From owner-l2tp@ipsec.org  Mon Apr  3 16:21:02 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24160
	for <l2tpext-archive@odin.ietf.org>; Mon, 3 Apr 2000 16:20:53 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id LAA04281; Mon, 3 Apr 2000 11:12:24 -0700 (PDT)
Received: from postal.redback.com (postal.redback.com [155.53.12.9]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA04277 for <l2tp@ipsec.org>; Mon, 3 Apr 2000 11:12:11 -0700 (PDT)
Received: from tradrat.redback.com (tradrat.redback.com [155.53.36.49])
	by postal.redback.com (Postfix) with ESMTP
	id 5F8242AA01; Mon,  3 Apr 2000 11:11:41 -0700 (PDT)
Received: (from tor@localhost) by tradrat.redback.com (8.8.8/8.6.9) id LAA02181; Mon, 3 Apr 2000 11:11:41 -0700 (PDT)
Date: Mon, 3 Apr 2000 11:11:41 -0700
From: Rene Tio <tor@redback.com>
To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Cc: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP with FR access network
Message-ID: <20000403111141.C1997@redback.com>
References: <882568B3.00730648.00@hqoutbound.ops.3com.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <882568B3.00730648.00@hqoutbound.ops.3com.com>; from Chris_Cormier@3Com.COM on Fri, Mar 31, 2000 at 12:56:43PM -0800
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Yes.  Should be back up on the server shortly.


On Fri, Mar 31, 2000 at 12:56:43PM -0800, Chris_Cormier@3Com.COM wrote:
> 
> 
> 
> 
> Hi,
> 
>   Is there any draft for L2TP with FR access network.
> 
> Thanks in advance.
> 
> Regards,
> Arul.
> 
> 
> 
> 


From owner-l2tp@ipsec.org  Mon Apr  3 21:27:52 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00339
	for <l2tpext-archive@odin.ietf.org>; Mon, 3 Apr 2000 21:27:51 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id RAA04757; Mon, 3 Apr 2000 17:20:37 -0700 (PDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA04753 for <l2tp@ipsec.org>; Mon, 3 Apr 2000 17:20:17 -0700 (PDT)
Received: from rapid5.com (colorado.rapid5.com [209.24.141.61])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id RAA05525
	for <l2tp@ipsec.org>; Mon, 3 Apr 2000 17:17:45 -0700 (PDT)
Received: from nile.rapid5.com (nile.rapid5.com [192.9.200.201])
	by rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id RAA21722
	for <l2tp@ipsec.org>; Mon, 3 Apr 2000 17:15:24 -0700 (PDT)
X-Recipient: <l2tp@ipsec.org>
Deliver-To: <l2tp@ipsec.org>
Received: from rapid5.com (dell_pc12 [192.9.200.224])
	by nile.rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id RAA21755
	for <l2tp@ipsec.org>; Mon, 3 Apr 2000 17:17:39 -0700 (PDT)
Message-ID: <38E88C86.BBE24C6A@rapid5.com>
Date: Mon, 03 Apr 2000 05:20:22 -0700
From: Srikrishnan <srikrish@rapid5.com>
Reply-To: srikrish@rapid5.com
Organization: Rapid5 Networks
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: MRU Renegotiation Problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello All,

   I've one question regarding implementing LAC.

   Following is the scenario I've my doubt,

Step 1) PPP user negotiates LCP with LAC ( say  ISP) and MRU negotiated
is 1500   ( let us assume, 1500 is maximum driver capability at the LAC
physical port to PPP)

Step 2)  LAC established tunnel/call to LNS and tunnels all layer 2
(PPP) data from now on to LNS

Step 3) PPP renegotiates LCP with LNS ( which is possible according to
RFC),
and at this time PPP negotiates 1524 MRU, which is accepted by LNS.

Step 4) After negotiation, LNS sends data packets to PPP User through
LAC( which  should ideal be transparent ).

My question is if the packet size is 1524 ( >1500) what will happen?

Issue here is,

* PPP in LAC side has updated its MRU as 1500 after initial negoitation
and not
change after renegotiation.
* Therez no way for LNS to update LAC about the changes in MRU.
   ( therez a mechanism to update change about ACCM not MRU)

What should be solution?

Is the packets dropped at LAC - PPP physical port?
Then therez no way for notification?

Has anyone have any solution to this?

I will appreciate any response. Thanks

Regards
Srikrishnan.



From owner-l2tp@ipsec.org  Mon Apr  3 22:32:01 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03392
	for <l2tpext-archive@odin.ietf.org>; Mon, 3 Apr 2000 22:32:00 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id SAA04871; Mon, 3 Apr 2000 18:25:03 -0700 (PDT)
Received: from blue.cosinecom.com (proxy4.cosinecom.com [208.248.148.132]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA04862 for <l2tp@ipsec.org>; Mon, 3 Apr 2000 18:24:35 -0700 (PDT)
Received: from cosinecom.com by blue.cosinecom.com (8.8.8+Sun/SMI-SVR4)
	id SAA23832; Mon, 3 Apr 2000 18:23:59 -0700 (PDT)
Message-ID: <38E9442E.699BF57D@cosinecom.com>
Date: Mon, 03 Apr 2000 18:23:59 -0700
From: Srinivasan Chakravarthy <cs@cosinecom.com>
Organization: CoSine Communications Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: srikrish@rapid5.com
CC: l2tp@ipsec.org
Subject: Re: MRU Renegotiation Problem
References: <38E88C86.BBE24C6A@rapid5.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

As long as the LAC has the capability (like driver buffer size and other
parameters) to transmit 1524 bytes of the PPP packets (which the user sends
after renegotiating with LNS), there should be no problem in the LAC. My view is
LAC should not remember (or even bother) the negotiated PPP parameters if the
remote user and LNS renegotiates. How the LAC to know if the link is
renegotiated between LNS and remote user is an implementation specific detail.

Is my view valid ? Any better solution ?

Thanks & Regards,

Srinivasan.

Srikrishnan wrote:

> Hello All,
>
>    I've one question regarding implementing LAC.
>
>    Following is the scenario I've my doubt,
>
> Step 1) PPP user negotiates LCP with LAC ( say  ISP) and MRU negotiated
> is 1500   ( let us assume, 1500 is maximum driver capability at the LAC
> physical port to PPP)
>
> Step 2)  LAC established tunnel/call to LNS and tunnels all layer 2
> (PPP) data from now on to LNS
>
> Step 3) PPP renegotiates LCP with LNS ( which is possible according to
> RFC),
> and at this time PPP negotiates 1524 MRU, which is accepted by LNS.
>
> Step 4) After negotiation, LNS sends data packets to PPP User through
> LAC( which  should ideal be transparent ).
>
> My question is if the packet size is 1524 ( >1500) what will happen?
>
> Issue here is,
>
> * PPP in LAC side has updated its MRU as 1500 after initial negoitation
> and not
> change after renegotiation.
> * Therez no way for LNS to update LAC about the changes in MRU.
>    ( therez a mechanism to update change about ACCM not MRU)
>
> What should be solution?
>
> Is the packets dropped at LAC - PPP physical port?
> Then therez no way for notification?
>
> Has anyone have any solution to this?
>
> I will appreciate any response. Thanks
>
> Regards
> Srikrishnan.



From owner-l2tp@ipsec.org  Tue Apr  4 01:52:09 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14160
	for <l2tpext-archive@odin.ietf.org>; Tue, 4 Apr 2000 01:52:09 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id VAA00418; Mon, 3 Apr 2000 21:48:09 -0700 (PDT)
Received: from fsnt.future.futusoft.com ([203.197.140.35]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id VAA00412 for <l2tp@ipsec.org>; Mon, 3 Apr 2000 21:46:14 -0700 (PDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000359080@fsnt.future.futusoft.com>;
 Tue, 04 Apr 2000 10:25:18 +0530
Received: from anandn (anandn.future.futsoft.com [10.0.4.57]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id KAA15258; Tue, 4 Apr 2000 10:04:40 +0530
Received: by localhost with Microsoft MAPI; Tue, 4 Apr 2000 10:13:52 +0530
Message-Id: <01BF9E1E.7A6C7940.anandn@future.futsoft.com>
From: Anand N <anandn@future.futsoft.com>
Reply-To: "anandn@future.futsoft.com" <anandn@future.futsoft.com>
To: "srikrish@rapid5.com" <srikrish@rapid5.com>
Cc: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: RE: MRU Renegotiation Problem
Date: Tue, 4 Apr 2000 10:13:51 +0530
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-l2tp@sailpix.com
Precedence: bulk


If somehow the MTU of LAC and the LNS PPP can be maintained and negotiated 
as the MRU of the L2TP transport medium (i.e. UDP in most cases) say, 1500 
bytes, then could this problem be solved?

- Anand.

-----Original Message-----
From:	Srinivasan Chakravarthy [SMTP:cs@cosinecom.com]
Sent:	Tuesday, April 04, 2000 6:54 AM
To:	srikrish@rapid5.com
Cc:	l2tp@ipsec.org
Subject:	Re: MRU Renegotiation Problem

As long as the LAC has the capability (like driver buffer size and other
parameters) to transmit 1524 bytes of the PPP packets (which the user sends
after renegotiating with LNS), there should be no problem in the LAC. My 
view is
LAC should not remember (or even bother) the negotiated PPP parameters if 
the
remote user and LNS renegotiates. How the LAC to know if the link is
renegotiated between LNS and remote user is an implementation specific 
detail.

Is my view valid ? Any better solution ?

Thanks & Regards,

Srinivasan.

Srikrishnan wrote:

> Hello All,
>
>    I've one question regarding implementing LAC.
>
>    Following is the scenario I've my doubt,
>
> Step 1) PPP user negotiates LCP with LAC ( say  ISP) and MRU negotiated
> is 1500   ( let us assume, 1500 is maximum driver capability at the LAC
> physical port to PPP)
>
> Step 2)  LAC established tunnel/call to LNS and tunnels all layer 2
> (PPP) data from now on to LNS
>
> Step 3) PPP renegotiates LCP with LNS ( which is possible according to
> RFC),
> and at this time PPP negotiates 1524 MRU, which is accepted by LNS.
>
> Step 4) After negotiation, LNS sends data packets to PPP User through
> LAC( which  should ideal be transparent ).
>
> My question is if the packet size is 1524 ( >1500) what will happen?
>
> Issue here is,
>
> * PPP in LAC side has updated its MRU as 1500 after initial negoitation
> and not
> change after renegotiation.
> * Therez no way for LNS to update LAC about the changes in MRU.
>    ( therez a mechanism to update change about ACCM not MRU)
>
> What should be solution?
>
> Is the packets dropped at LAC - PPP physical port?
> Then therez no way for notification?
>
> Has anyone have any solution to this?
>
> I will appreciate any response. Thanks
>
> Regards
> Srikrishnan.



From owner-l2tp@ipsec.org  Tue Apr  4 11:11:28 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05917
	for <l2tpext-archive@odin.ietf.org>; Tue, 4 Apr 2000 11:11:26 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id GAA02536; Tue, 4 Apr 2000 06:31:53 -0700 (PDT)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA02532 for <l2tp@ipsec.org>; Tue, 4 Apr 2000 06:31:21 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.49.31])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id GAA12606;
	Tue, 4 Apr 2000 06:31:43 -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 JAA09805; Tue, 4 Apr 2000 09:30:49 -0400 (EDT)
Message-ID: <38E9EE7A.97435815@cisco.com>
Date: Tue, 04 Apr 2000 09:30: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: Srinivasan Chakravarthy <cs@cosinecom.com>
CC: srikrish@rapid5.com, l2tp@ipsec.org
Subject: Re: MRU Renegotiation Problem
References: <38E88C86.BBE24C6A@rapid5.com> <38E9442E.699BF57D@cosinecom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srinivasan Chakravarthy wrote:
> 
> As long as the LAC has the capability (like driver buffer size and other
> parameters) to transmit 1524 bytes of the PPP packets (which the user sends
> after renegotiating with LNS), there should be no problem in the LAC. My view is
> LAC should not remember (or even bother) the negotiated PPP parameters if the
> remote user and LNS renegotiates. How the LAC to know if the link is
> renegotiated between LNS and remote user is an implementation specific detail.

The L2TP RFC states that the LAC MUST be able to tunnel PPP packets up
to the default MRU for PPP. This happens to be 1500 bytes (before the
IP/UDP/L2TP header). As long as the LNS does not allow an MRU larger
than this, the LAC should be OK. Incidently, it is probably never a good
idea to try and negotiate a larger MRU than 1500 anyway given the
likelihood of fragmentation on the intervening IP link. In fact, it is
better to ensure that the PPP MRU is some value lower than 1500 to
accomodate the additional headers. There is some discussion of this in
draft-ietf-l2tpext-l2tp-security-00.txt.

There have been proposals to communicate a negotiated MRU from the LNS
to the LAC, as well as suggest parameters from the LAC for the LNS to
negotiate. See draft-ietf-l2tpext-link-00.txt for more info. 

- Mark

> 
> Is my view valid ? Any better solution ?
> 
> Thanks & Regards,
> 
> Srinivasan.
> 
> Srikrishnan wrote:
> 
> > Hello All,
> >
> >    I've one question regarding implementing LAC.
> >
> >    Following is the scenario I've my doubt,
> >
> > Step 1) PPP user negotiates LCP with LAC ( say  ISP) and MRU negotiated
> > is 1500   ( let us assume, 1500 is maximum driver capability at the LAC
> > physical port to PPP)
> >
> > Step 2)  LAC established tunnel/call to LNS and tunnels all layer 2
> > (PPP) data from now on to LNS
> >
> > Step 3) PPP renegotiates LCP with LNS ( which is possible according to
> > RFC),
> > and at this time PPP negotiates 1524 MRU, which is accepted by LNS.
> >
> > Step 4) After negotiation, LNS sends data packets to PPP User through
> > LAC( which  should ideal be transparent ).
> >
> > My question is if the packet size is 1524 ( >1500) what will happen?
> >
> > Issue here is,
> >
> > * PPP in LAC side has updated its MRU as 1500 after initial negoitation
> > and not
> > change after renegotiation.
> > * Therez no way for LNS to update LAC about the changes in MRU.
> >    ( therez a mechanism to update change about ACCM not MRU)
> >
> > What should be solution?
> >
> > Is the packets dropped at LAC - PPP physical port?
> > Then therez no way for notification?
> >
> > Has anyone have any solution to this?
> >
> > I will appreciate any response. Thanks
> >
> > Regards
> > Srikrishnan.


From owner-l2tp@ipsec.org  Wed Apr  5 16:51:37 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16317
	for <l2tpext-archive@odin.ietf.org>; Wed, 5 Apr 2000 16:51:35 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id JAA05885; Wed, 5 Apr 2000 09:49:07 -0700 (PDT)
Received: from smtprich.nortel.com (smtprich.nortel.com [192.135.215.8]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA05878 for <l2tp@ipsec.org>; Wed, 5 Apr 2000 09:46:40 -0700 (PDT)
Received: from zrchb213.us.nortel.com (actually zrchb213) 
          by smtprich.nortel.com; Wed, 5 Apr 2000 11:16:22 -0500
Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2650.21) 
          id <2K0D5KT0>; Wed, 5 Apr 2000 11:12:10 -0500
Message-ID: <6DDA62170439D31185750000F80826AC0216E063@zmerd004.ca.nortel.com>
From: "David Allan" <dallan@nortelnetworks.com>
To: l2tp@ipsec.org
Subject: L2TPEXT Minutes
Date: Wed, 5 Apr 2000 11:11:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01BF9F19.B1D1A5EE"
X-Orig: <dallan@americasm01.nt.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

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

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

Any comments before I submit to ietf.org?

L2TPEXT Minutes for IETF 47

Chair:		Mark Townsley townsley@cisco.com
Minutes: 	Dave Allan, dallan@nortelnetworks.com


Draft-ietf-pppext-l2tp-atmext-01
Yves T'Jones/Alcatel
		Draft stable for quite some time. Yves provided a quick
review of the problem space. Extending incoming call procedures for ATM. 

		Q: What is the called number? Resolution is that use of
called number and service name needs to be more specific. 
		Q: What about adding VPI/VCI for where service name is not
available?
		Discussion focused around incoming call. Useful for
diagnostic reasons. To be added to the text.

		Changes: minor editorial changes, broadband bearer bits are
not a separate AVP. IANA type codes requested are in the IANA queue.
		Proposal do last call. Called number should be all zeros in
PVC case.

Draft ietf-pppext-l2tp-mpls-03
Pat Calhoun/Sun Microsystems

		Draft renamed for L2TPEXT

		Goal: How can two peers negotiate an LSPID.
		Document describes a new L2TP AVP 
		May be present in ICRQ, ICRP OCRQ and OCRP
		Because LSPs are unidirectional, can do both directions.
		Issue: There is discussion as whether the L2TP devices
should be inside or outside the MPLS network, If the latter, this may not be
useful.
		Suggestion: Put the LSPID in the result code.

		Consensus was group does not understand the utility or
appropriateness of this.
		George pointed out that DSCPs can be in the EXP bits, such
than a single LSPID was insufficient info to do diffserv.

Draft-ietf-pppext-l2tp-ds.02
		Provide an AVP to communicate DSCPs. All traffic for a
specific tunnel is bound to a specific DSCP. Permits per user class of
service differentiation in a tunnel. 

		Q: How does this work when there are user marked DSCPs? This
breaks the DS tunneling spec.

		What if it is PPP compressed or encrypted, is the LAC going
to pull everything apart to examine the DSCPs. Belief that there will be
tunnels across domain boundaries. 

		Resolution, add language to the draft, if compressed or
encrypted then use the session DSCP otherwise use the DSCP marking in the
session packets.

		Currently draft defines a vendor specific AVP. If people are
going to implement it, we'll get an IANA number.

		Q: Is this really a policy thing and DSCP is a bit too far
down.

		Q: Is this really a LAC/LNS thing or should there be a third
entity policy wise. In other words, is L2TP signaling not the right place
for this.

		It may be useful to allow something in the enterprise to do
a policy decision.

Draft-ietf-l2tpext-security-00
Bernard Aboba/UUNet

		Goal: Secure L2TP against threats to control channel and
data. Want to support floating source ports and IP addresses.

		Fragmentation issue: Addition of L2TP and IPSEC headers can
cause fragmentation. 
		Solution: Provide PPP with the MTU of ingress/egress
interface minus header overhead.
			- should occur after L2TP tunnel set up, before LCP
negotiation

		Teardown:
		IPSEC and PPP/L2TP teardown need to be coordinated.
		PPP: LCP term req/graceful else LCP keepalive for
non-graceful
		L2TP: StopCCN/graceful L2TP hello/non-graceful
		IKE/IPSEC SA: Once L2TP tunnel is deleted, then any phase 1
and phase 2 SA s should be deleted.
		Q: Why delete the phase 1 SA? Seems to be an arbitrary
linkage.
		A: OK, You may want to use it in the future. Not clear if an
LNS is aware of compulsory tunneling. Much discussion
		Suggested text to be posted to the list to resolve this
issue.

		Filter issues: 
		L2TP- implementations may use a dynamically assigned UDP
port.
		Address may change.
		Need IKE phase 1 and 2 to protect initial SCCRQ
		Then new IKE p1/2 to protect new SCCRQ on IP address
		New ike phase 2 for port number change.
		Filter Installation: L2TP needs to inject filters into the
IPSEC filter database.
		Certificate Handling: Cut to the chase. You are
authenticating a tunnel or PPP end point. How do you control the user base.
You can add PPP filters at the LNS.

		Q: A lot of effort put into running L2TP through a NAT. What
about IPSEC.
		Some things can be done if you turn off UDP checksum (which
you can configure with L2TP).

Draft-ietf-l2tpext-mib-00
Ross Wheeler/Wind River

	Has anyone implemented the recent draft....no!   anybody read it?

		Changes: detailed in the draft, mostly cosmetic
		Dave Thaler did the SNMP review.
		2 weeks to review then move to WG last call.
		Pat: Experience dictates that unless we put it directly to
WG last call, no comments will come.

		"It does compile by the way."

L2TP v2 draft discussion

		Proposed clarifications
		Recommend at least 16 octet tunnel auth challenge.
		When dropping out of order control packets, update Nr first.
		Zero should be send in the connect speed AVP if the speed is
indeterminable or no physical link.

		Pat: Call it something other than v2. Like "bis" or "son of
L2TP"

		More clarifications:
		Framing and bearer capabilities,
			Bearer for outgoing calls only.
			Do we need to be strict about framing capabilities
for incoming calls?
		SLI/ACCM race condition.
				Upon receipt of an SLI a LAC may apply a new
ACCM value before finishing tunneling LCP which if the client is strict on
ACCM, may lead to a non-converging race condition.
			Answer is SLI must traverse LAC-LNS-LAC before
applying it.
		Source IP address change
				Text is ambiguous as to whether this is
allowed. Some implementations currently change the source IP address of the
SCCRP based on local routing decisions.
		Current goals and milestones:
			Missed first two, may miss rest.
				Propose, may L2TP MIB, june L2TP security,
may L2TP over ATM and FR all to proposed standard. Dec 00, L2TP to draft
standard.

				Glen Zorn: we need 8 months? You have five
edits to do there. A: Want a bakeoff and implementation experience.;-)

		Current drafts:
				L2TP alternate data channel ADC, Securing
L2TP with IPSEC, SESINFO, ATM extensions, AAL5 and FUNI, Link Extensions,
header compression, diffserv, MPLS extension, MIB


Regards
Dave Allan

---------------------------------
Sr. Advisor Access Evolution
dallan@nortelnetworks.com



------_=_NextPart_001_01BF9F19.B1D1A5EE
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.2651.65">
<TITLE>L2TPEXT Minutes</TITLE>
</HEAD>
<BODY>

<P><FONT FACE=3D"Arial">Any comments before I submit to =
ietf.org?</FONT>
</P>

<P><FONT FACE=3D"Arial">L2TPEXT Minutes for IETF 47</FONT>
</P>

<P><FONT FACE=3D"Arial">Chair:&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mark Townsley =
townsley@cisco.com</FONT>
<BR><FONT FACE=3D"Arial">Minutes: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Dave Allan, dallan@nortelnetworks.com<U><B></B></U></FONT>
</P>
<BR>

<P><I><FONT FACE=3D"Arial">Draft-ietf-pppext-l2tp-atmext-01</FONT></I>
<BR><FONT FACE=3D"Arial">Yves T'Jones/Alcatel</FONT>
<UL><UL>
<P><FONT FACE=3D"Arial">Draft stable for quite some time. Yves provided =
a quick review of the problem space. Extending incoming call procedures =
for ATM. </FONT></P>

<P><FONT FACE=3D"Arial">Q: What is the called number? Resolution is =
that use of called number and service name needs to be more specific. =
</FONT>
<BR><FONT FACE=3D"Arial">Q: What about adding VPI/VCI for where service =
name is not available?</FONT>
<BR><FONT FACE=3D"Arial">Discussion focused around incoming call. =
Useful for diagnostic reasons. To be added to the text.</FONT>
</P>

<P><FONT FACE=3D"Arial">Changes: minor editorial changes, broadband =
bearer bits are not a separate AVP. IANA type codes requested are in =
the IANA queue.</FONT></P>

<P><FONT FACE=3D"Arial">Proposal do last call. Called number should be =
all zeros in PVC case.</FONT>
</P>
</UL></UL>
<P><I><FONT FACE=3D"Arial">Draft ietf-pppext-l2tp-mpls-03</FONT></I>
<BR><FONT FACE=3D"Arial">Pat Calhoun/Sun Microsystems</FONT>
</P>
<UL><UL>
<P><FONT FACE=3D"Arial">Draft renamed for L2TPEXT</FONT>
</P>

<P><FONT FACE=3D"Arial">Goal: How can two peers negotiate an =
LSPID.</FONT>
<BR><FONT FACE=3D"Arial">Document describes a new L2TP AVP </FONT>
<BR><FONT FACE=3D"Arial">May be present in ICRQ, ICRP OCRQ and =
OCRP</FONT>
<BR><FONT FACE=3D"Arial">Because LSPs are unidirectional, can do both =
directions.</FONT>
<BR><FONT FACE=3D"Arial">Issue: There is discussion as whether the L2TP =
devices should be inside or outside the MPLS network, If the latter, =
this may not be useful.</FONT></P>

<P><FONT FACE=3D"Arial">Suggestion: Put the LSPID in the result =
code.</FONT>
</P>

<P><FONT FACE=3D"Arial">Consensus was group does not understand the =
utility or appropriateness of this.</FONT>
<BR><FONT FACE=3D"Arial">George pointed out that DSCPs can be in the =
EXP bits, such than a single LSPID was insufficient info to do =
diffserv.</FONT>
</P>
</UL></UL>
<P><I><FONT FACE=3D"Arial">Draft-ietf-pppext-l2tp-ds.02</FONT></I>
<UL><UL>
<P><FONT FACE=3D"Arial">Provide an AVP to communicate DSCPs. All =
traffic for a specific tunnel is bound to a specific DSCP. Permits per =
user class of service differentiation in a tunnel. </FONT></P>

<P><FONT FACE=3D"Arial">Q: How does this work when there are user =
marked DSCPs? This breaks the DS tunneling spec.</FONT>
</P>

<P><FONT FACE=3D"Arial">What if it is PPP compressed or encrypted, is =
the LAC going to pull everything apart to examine the DSCPs. Belief =
that there will be tunnels across domain boundaries. </FONT></P>

<P><FONT FACE=3D"Arial">Resolution, add language to the draft, if =
compressed or encrypted then use the session DSCP otherwise use the =
DSCP marking in the session packets.</FONT></P>

<P><FONT FACE=3D"Arial">Currently draft defines a vendor specific AVP. =
If people are going to implement it, we'll get an IANA number.</FONT>
</P>

<P><FONT FACE=3D"Arial">Q: Is this really a policy thing and DSCP is a =
bit too far down.</FONT>
</P>

<P><FONT FACE=3D"Arial">Q: Is this really a LAC/LNS thing or should =
there be a third entity policy wise. In other words, is L2TP signaling =
not the right place for this.</FONT></P>

<P><FONT FACE=3D"Arial">It may be useful to allow something in the =
enterprise to do a policy decision.</FONT>
</P>
</UL></UL>
<P><I><FONT FACE=3D"Arial">Draft-ietf-l2tpext-security-00</FONT></I>
<BR><FONT FACE=3D"Arial">Bernard Aboba/UUNet</FONT>
</P>
<UL><UL>
<P><FONT FACE=3D"Arial">Goal: Secure L2TP against threats to control =
channel and data. Want to support floating source ports and IP =
addresses.</FONT>
</P>

<P><FONT FACE=3D"Arial">Fragmentation issue: Addition of L2TP and IPSEC =
headers can cause fragmentation. </FONT>
<BR><FONT FACE=3D"Arial">Solution: Provide PPP with the MTU of =
ingress/egress interface minus header overhead.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT FACE=3D"Arial">- =
should occur after L2TP tunnel set up, before LCP negotiation</FONT>
</P>

<P><FONT FACE=3D"Arial">Teardown:</FONT>
<BR><FONT FACE=3D"Arial">IPSEC and PPP/L2TP teardown need to be =
coordinated.</FONT>
<BR><FONT FACE=3D"Arial">PPP: LCP term req/graceful else LCP keepalive =
for non-graceful</FONT>
<BR><FONT FACE=3D"Arial">L2TP: StopCCN/graceful L2TP =
hello/non-graceful</FONT>
<BR><FONT FACE=3D"Arial">IKE/IPSEC SA: Once L2TP tunnel is deleted, =
then any phase 1 and phase 2 SA s should be deleted.</FONT>
<BR><FONT FACE=3D"Arial">Q: Why delete the phase 1 SA? Seems to be an =
arbitrary linkage.</FONT>
<BR><FONT FACE=3D"Arial">A: OK, You may want to use it in the future. =
Not clear if an LNS is aware of compulsory tunneling. Much =
discussion</FONT>
<BR><FONT FACE=3D"Arial">Suggested text to be posted to the list to =
resolve this issue.</FONT>
</P>

<P><FONT FACE=3D"Arial">Filter issues: </FONT>
<BR><FONT FACE=3D"Arial">L2TP- implementations may use a dynamically =
assigned UDP port.</FONT>
<BR><FONT FACE=3D"Arial">Address may change.</FONT>
<BR><FONT FACE=3D"Arial">Need IKE phase 1 and 2 to protect initial =
SCCRQ</FONT>
<BR><FONT FACE=3D"Arial">Then new IKE p1/2 to protect new SCCRQ on IP =
address</FONT>
<BR><FONT FACE=3D"Arial">New ike phase 2 for port number change.</FONT>
<BR><FONT FACE=3D"Arial">Filter Installation: L2TP needs to inject =
filters into the IPSEC filter database.</FONT>
<BR><FONT FACE=3D"Arial">Certificate Handling: Cut to the chase. You =
are authenticating a tunnel or PPP end point. How do you control the =
user base. You can add PPP filters at the LNS.</FONT></P>

<P><FONT FACE=3D"Arial">Q: A lot of effort put into running L2TP =
through a NAT. What about IPSEC.</FONT>
<BR><FONT FACE=3D"Arial">Some things can be done if you turn off UDP =
checksum (which you can configure with L2TP).</FONT>
</P>
</UL></UL>
<P><I><FONT FACE=3D"Arial">Draft-ietf-l2tpext-mib-00</FONT></I>
<BR><FONT FACE=3D"Arial">Ross Wheeler/Wind River</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT FACE=3D"Arial">Has =
anyone implemented the recent draft....no!&nbsp;&nbsp; anybody read =
it?</FONT>
</P>
<UL><UL>
<P><FONT FACE=3D"Arial">Changes: detailed in the draft, mostly =
cosmetic</FONT>
<BR><FONT FACE=3D"Arial">Dave Thaler did the SNMP review.</FONT>
<BR><FONT FACE=3D"Arial">2 weeks to review then move to WG last =
call.</FONT>
<BR><FONT FACE=3D"Arial">Pat: Experience dictates that unless we put it =
directly to WG last call, no comments will come.</FONT>
</P>

<P><FONT FACE=3D"Arial">"It does compile by the way."</FONT>
</P>
</UL></UL>
<P><I><FONT FACE=3D"Arial">L2TP v2 draft discussion</FONT></I>
</P>
<UL><UL>
<P><FONT FACE=3D"Arial">Proposed clarifications</FONT>
<BR><FONT FACE=3D"Arial">Recommend at least 16 octet tunnel auth =
challenge.</FONT>
<BR><FONT FACE=3D"Arial">When dropping out of order control packets, =
update Nr first.</FONT>
<BR><FONT FACE=3D"Arial">Zero should be send in the connect speed AVP =
if the speed is indeterminable or no physical link.</FONT>
</P>

<P><FONT FACE=3D"Arial">Pat: Call it something other than v2. Like =
"bis" or "son of L2TP"</FONT>
</P>

<P><FONT FACE=3D"Arial">More clarifications:</FONT>
<BR><FONT FACE=3D"Arial">Framing and bearer capabilities,</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
FACE=3D"Arial">Bearer for outgoing calls only.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT FACE=3D"Arial">Do =
we need to be strict about framing capabilities for incoming =
calls?</FONT>
<BR><FONT FACE=3D"Arial">SLI/ACCM race condition.</FONT>
<UL><UL>
<P><FONT FACE=3D"Arial">Upon receipt of an SLI a LAC may apply a new =
ACCM value before finishing tunneling LCP which if the client is strict =
on ACCM, may lead to a non-converging race condition.</FONT></P>
</UL></UL>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
FACE=3D"Arial">Answer is SLI must traverse LAC-LNS-LAC before applying =
it.</FONT>
<BR><FONT FACE=3D"Arial">Source IP address change</FONT>
<UL><UL>
<P><FONT FACE=3D"Arial">Text is ambiguous as to whether this is =
allowed. Some implementations currently change the source IP address of =
the SCCRP based on local routing decisions.</FONT></P>
</UL></UL>
<P><FONT FACE=3D"Arial">Current goals and milestones:</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
FACE=3D"Arial">Missed first two, may miss rest.</FONT>
<UL><UL>
<P><FONT FACE=3D"Arial">Propose, may L2TP MIB, june L2TP security, may =
L2TP over ATM and FR all to proposed standard. Dec 00, L2TP to draft =
standard.</FONT></P>

<P><FONT FACE=3D"Arial">Glen Zorn: we need 8 months? You have five =
edits to do there. A: Want a bakeoff and implementation =
experience.;-)</FONT>
</P>
</UL></UL>
<P><FONT FACE=3D"Arial">Current drafts:</FONT>
<UL><UL>
<P><FONT FACE=3D"Arial">L2TP alternate data channel ADC, Securing L2TP =
with IPSEC, SESINFO, ATM extensions, AAL5 and FUNI, Link Extensions, =
header compression, diffserv, MPLS extension, MIB</FONT></P>
<BR>
</UL></UL></UL></UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Dave Allan</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">---------------------------------</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">Sr. Advisor Access Evolution</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">dallan@nortelnetworks.com</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01BF9F19.B1D1A5EE--


From owner-l2tp@ipsec.org  Thu Apr  6 00:19:19 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22621
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Apr 2000 00:19:19 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id RAA06562; Wed, 5 Apr 2000 17:51:14 -0700 (PDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA06558 for <l2tp@ipsec.org>; Wed, 5 Apr 2000 17:51:03 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.49.31])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id RAA24444;
	Wed, 5 Apr 2000 17:49:44 -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 UAA10522; Wed, 5 Apr 2000 20:50:44 -0400 (EDT)
Message-ID: <38EBDF53.6D1C7666@cisco.com>
Date: Wed, 05 Apr 2000 20:50:27 -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: David Allan <dallan@nortelnetworks.com>
CC: l2tp@ipsec.org
Subject: Re: L2TPEXT Minutes
References: <6DDA62170439D31185750000F80826AC0216E063@zmerd004.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


David Allan wrote:
> 
> Any comments before I submit to ietf.org?

Please do not send to ietf.org, this is the only list you need to
publish this to.

- Mark


From owner-l2tp@ipsec.org  Thu Apr  6 00:45:52 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22963
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Apr 2000 00:45:51 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id SAA06621; Wed, 5 Apr 2000 18:36:06 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA06617 for <l2tp@ipsec.org>; Wed, 5 Apr 2000 18:35:05 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.49.31])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id SAA20824
	for <l2tp@ipsec.org>; Wed, 5 Apr 2000 18:34:37 -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 VAA10527 for <l2tp@ipsec.org>; Wed, 5 Apr 2000 21:34:47 -0400 (EDT)
Message-ID: <38EBE9A6.783B63F1@cisco.com>
Date: Wed, 05 Apr 2000 21:34:30 -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@ipsec.org
Subject: l2tpext minutes reformatted
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


Reformatted to be 72 column friendly. A couple of small editorial
corrections included as well (e.g. Bernard still works for Microsoft,
yes?).

Thanks,

- Mark

L2TPEXT Minutes for IETF 47

Chair:          Mark Townsley townsley@cisco.com
Minutes:        Dave Allan, dallan@nortelnetworks.com


Draft-ietf-pppext-l2tp-atmext-01
Yves T'Jones/Alcatel

Draft stable for quite some time. Yves provided a quick review of the
problem space. Extending incoming call procedures for ATM. 

Q: What is the called number? Resolution is that use of called number
and service name needs to be more specific. 

Q: What about adding VPI/VCI for where service name is not available?
Discussion focused around incoming call. Useful for diagnostic reasons.
To be added to the text.

Changes: minor editorial changes, broadband bearer bits are not a
separate AVP. IANA type codes requested are in the IANA queue. Proposal
do last call. Called number should be all zeros in PVC case.

Draft ietf-pppext-l2tp-mpls-03
Pat Calhoun/Sun Microsystems

Draft renamed for L2TPEXT

Goal: How can two peers negotiate an LSPID.
Document describes a new L2TP AVP May be present in ICRQ, ICRP OCRQ and
OCRPBecause LSPs are unidirectional, can do both directions.

Issue: There is discussion as whether the L2TP devices should be inside
or outside the MPLS network, If the latter, this may not be useful.

Suggestion: Put the LSPID in the result code.

Consensus was group does not understand the utility or appropriateness
of this.
George pointed out that DSCPs can be in the EXP bits, such than a single
LSPID was insufficient info to do diffserv.

Draft-ietf-pppext-l2tp-ds-02
Provide an AVP to communicate DSCPs. All traffic for a specific tunnel
is bound to a specific DSCP. Permits per user class of service
differentiation in a tunnel. 

Q: How does this work when there are user marked DSCPs? This breaks the
DS tunneling spec.

What if it is PPP compressed or encrypted, is the LAC going to pull
everything apart to examine the DSCPs. Belief that there will be tunnels
across domain boundaries. Resolution, add language to the draft, if
compressed or encrypted then use the session DSCP otherwise use the DSCP
marking in the session packets.

Currently draft defines a vendor specific AVP. If people are going to
implement it, we'll get an IANA number.

Q: Is this really a policy thing and DSCP is a bit too far down.

Q: Is this really a LAC/LNS thing or should there be a third entity
policy wise. In other words, is L2TP signaling not the right place for
this.

It may be useful to allow something in the enterprise to do a policy
decision.

Draft-ietf-l2tpext-security-00
Bernard Aboba/Microsoft

Goal: Secure L2TP against threats to control channel and data. Want to
support floating source ports and IP addresses.

Fragmentation issue: Addition of L2TP and IPSEC headers can cause
fragmentation. 

Solution: Provide PPP with the MTU of ingress/egress interface minus
header overhead. Should occur after L2TP tunnel set up, before LCP
negotiation.

Teardown: IPSEC and PPP/L2TP teardown need to be coordinated.
PPP: LCP term req/graceful else LCP keepalive for non-graceful
L2TP: StopCCN/graceful L2TP hello/non-graceful
IKE/IPSEC SA: Once L2TP tunnel is deleted, then any phase 1 and phase 2
SAs should be deleted.
Q: Why delete the phase 1 SA? Seems to be an arbitrary linkage.
A: OK, You may want to use it in the future. Not clear if an LNS is
aware of compulsory tunneling. Much discussion. Suggested text to be
posted to the list to resolve this issue.

Filter issues: 
L2TP implementations may use a dynamically assigned UDP port.
Address may change. Need IKE phase 1 and 2 to protect initial SCCRQ.
Then new IKE p1/2 to protect new SCCRQ on IP address. New ike phase 2
for port number change.

Filter Installation: L2TP needs to inject filters into the IPSEC filter
database.

Certificate Handling: Cut to the chase. You are authenticating a tunnel
or PPP end point. How do you control the user base. You can add PPP
filters at the LNS.

Q: A lot of effort put into running L2TP through a NAT. What about
IPSEC. Some things can be done if you turn off UDP checksum (which you
can configure with L2TP).

Draft-ietf-l2tpext-mib-00
Ross Wheeler/Wind River

Has anyone implemented the recent draft....no!   anybody read it?
Changes: detailed in the draft, mostly cosmetic
Dave Thaler will do the SNMP review.
2 weeks to review then move to WG last call.
Pat: Experience dictates that unless we put it directly to WG last call,
no comments will come.

"It does compile by the way."

L2TP v2 draft discussion

Proposed clarifications
Recommend at least 16 octet tunnel auth challenge.
When dropping out of order control packets, update Nr first.
Zero should be send in the connect speed AVP if the speed is
indeterminable or no physical link.

Pat: Call it something other than v2. Like "bis" or "son of L2TP"

More clarifications:
Framing and bearer capabilities,
Bearer for outgoing calls only.
Do we need to be strict about framing capabilities for incoming calls?

SLI/ACCM race condition.

Upon receipt of an SLI a LAC may apply a new ACCM value before finishing
tunneling LCP which if the client is strict on ACCM, may lead to a
non-converging race condition.

Answer is SLI must traverse LAC-LNS-LAC before applying it.

Source IP address change

Text is ambiguous as to whether this is allowed. Some implementations
currently change the source IP address of the SCCRP based on local
routing decisions.

Current goals and milestones:

Missed first two, may miss rest. Propose, May L2TP MIB, June L2TP
security, May L2TP over ATM and FR all to proposed standard. Dec 00,
L2TP to draft standard.

Glen Zorn: we need 8 months (for L2TP)? You have five edits to do there.
A: Want a bakeoff and implementation experience.

Current drafts:

L2TP alternate data channel ADC, Securing L2TP with IPSEC, SESINFO, ATM
extensions, AAL5 and FUNI, Link Extensions, header compression,
diffserv, MPLS extension, MIB

Regards
Dave Allan

---------------------------------
Sr. Advisor Access Evolution
dallan@nortelnetworks.com


From owner-l2tp@ipsec.org  Thu Apr  6 05:29:32 2000
Received: from ns3.sailpix.com (ns3.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05878
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Apr 2000 05:29:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id WAA07251; Wed, 5 Apr 2000 22:48:58 -0700 (PDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA07247 for <l2tp@ipsec.org>; Wed, 5 Apr 2000 22:48:44 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.49.31])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id WAA03565;
	Wed, 5 Apr 2000 22:47:24 -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 BAA10558; Thu, 6 Apr 2000 01:48:26 -0400 (EDT)
Message-ID: <38EC2519.3739E0BA@cisco.com>
Date: Thu, 06 Apr 2000 01:48:09 -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: David Allan <dallan@nortelnetworks.com>, l2tp@ipsec.org
Subject: Re: L2TPEXT Minutes
References: <6DDA62170439D31185750000F80826AC0216E063@zmerd004.ca.nortel.com> <38EBDF53.6D1C7666@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


David,

You probably meant minutes@ietf.org, I misinterpreted this as
ietf@ietf.org (which of course would be silly). I will forward them on
to minutes@ietf.org if there are no objections.

Thanks,

- Mark

"W. Mark Townsley" wrote:
> 
> David Allan wrote:
> >
> > Any comments before I submit to ietf.org?
> 
> Please do not send to ietf.org, this is the only list you need to
> publish this to.
> 
> - Mark


From owner-l2tp@ipsec.org  Thu Apr  6 19:11:01 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16751
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Apr 2000 19:11:00 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA09371; Thu, 6 Apr 2000 13:15:27 -0700 (PDT)
Received: from sin.core-sdi.com (host-SDI-R01.metrored.net.ar [200.47.48.28] (may be forged)) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA09367 for <l2tp@ipsec.org>; Thu, 6 Apr 2000 13:14:36 -0700 (PDT)
Received: from amadeus.servers.core-sdi.com (amadeus.servers.core-sdi.com [192.168.13.3])
	by sin.core-sdi.com (Postfix) with ESMTP id BC7D51E01
	for <l2tp@ipsec.org>; Thu,  6 Apr 2000 17:16:39 -0300 (ART)
Received: from core-sdi.com (random.exorcist.core-sdi.com [192.168.88.17])
	by amadeus.servers.core-sdi.com id RAA10369
	for <l2tp@ipsec.org>; Thu, 6 Apr 2000 17:12:55 -0300
Message-ID: <38ECEE36.47D29C2E@core-sdi.com>
Date: Thu, 06 Apr 2000 17:06:14 -0300
From: Sebastian Wain <swain@core-sdi.com>
Organization: Core SDI
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: [Fwd: Lucent WaveAccess 3200]
Content-Type: multipart/mixed;
 boundary="------------75492A8828792B5D920000F1"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

This is a multi-part message in MIME format.
--------------75492A8828792B5D920000F1
Content-Type: multipart/alternative;
 boundary="------------9884DA0CA219CC328D0B7F73"


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

I forward the same mail I sent to the babylon list.
I think the equipment model is the 3500, but the isp gave me 3200.
The equipment homepage is
(http://www.lucent.com/wirelessnet/waveaccess/)

Thank You
Sebastian Wain

--
Sebastian Wain - Security Consultant
swain@core-sdi.com
Core SDI S.A.
http://www.core-sdi.com



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I forward the same mail I sent to the babylon list.
<br>I think the equipment model is the 3500, but the isp gave me 3200.
<br>The equipment homepage is (<A HREF="http://www.lucent.com/wirelessnet/waveaccess/">http://www.lucent.com/wirelessnet/waveaccess/</A>)
<p>Thank You
<br>Sebastian Wain
<pre>--
Sebastian Wain - Security Consultant
swain@core-sdi.com
Core SDI S.A.
<A HREF="http://www.core-sdi.com">http://www.core-sdi.com</A></pre>
&nbsp;</html>

--------------9884DA0CA219CC328D0B7F73--

--------------75492A8828792B5D920000F1
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

X-Mozilla-Status2: 00000000
Message-ID: <38E266D5.237524AE@core-sdi.com>
Date: Wed, 29 Mar 2000 17:25:58 -0300
From: Sebastian Wain <swain@core-sdi.com>
Organization: Core SDI
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.5-15 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: babylon@spellcast.com, babylon-beta@spellcast.com
Subject: Lucent WaveAccess 3200
Content-Type: multipart/alternative;
 boundary="------------B6FE088EB5071547031CD499"


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

I write this message to know if somebody is using this type of equipment
(Lucent WaveAccess 3200) with some type of Unix (Linux, FreeBSD, OpenBSD
or others) or have some extra information (I didn't find enough
information in Internet) I think will
be useful to do a driver.

Here, In Argentina, began to operate a wireless isp called velocom. This
enteprise only has drivers in windows, and I search in Internet without
results.
I contracted the service and sniffed the network in my home, so I
observed l2tp over ethernet using the protocol types 0x8866 and
0x8867 (in pppoe the types are 0x8863 and 0x8864),  the windows first
logged to a vpn server on an Intranet (>172.16.x.x).
If somebody knows of some driver... I will be very grateful, otherwise
the right way is to do the driver with some friends in the same
situation.


Thank You
Sebastian Wain


--
Sebastian Wain - Security Consultant
swain@core-sdi.com
Core SDI S.A.
http://www.core-sdi.com



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I write this message to know if somebody is using this type of equipment
(Lucent WaveAccess 3200) with some type of Unix (Linux, FreeBSD, OpenBSD
or others) or have some extra information (I didn't find enough information
in Internet) I think will
<br>be useful to do a driver.
<p>Here, In Argentina, began to operate a wireless isp called velocom.
This enteprise only has drivers in windows, and I search in Internet without
results.
<br>I contracted the service and sniffed the network in my home, so I observed
l2tp over ethernet using the protocol types 0x8866 and
<br>0x8867 (in pppoe the types are 0x8863 and 0x8864),&nbsp; the windows
first logged to a vpn server on an Intranet (>172.16.x.x).
<br>If somebody knows of some driver... I will be very grateful, otherwise
the right way is to do the driver with some friends in the same
<br>situation.
<br>&nbsp;
<p>Thank You
<br>Sebastian Wain
<br>&nbsp;
<pre>--
Sebastian Wain - Security Consultant
swain@core-sdi.com
Core SDI S.A.
<A HREF="http://www.core-sdi.com">http://www.core-sdi.com</A></pre>
&nbsp;</html>

--------------B6FE088EB5071547031CD499--


--------------75492A8828792B5D920000F1--



From owner-l2tp@ipsec.org  Sat Apr  8 01:38:13 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00325
	for <l2tpext-archive@odin.ietf.org>; Sat, 8 Apr 2000 01:38:11 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id UAA12857; Fri, 7 Apr 2000 20:45:44 -0700 (PDT)
Received: from firewall.chttl.com.tw (gate.chttl.com.tw [202.39.157.254]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id UAA12850 for <l2tp@ipsec.org>; Fri, 7 Apr 2000 20:44:56 -0700 (PDT)
Received: from ms.chttl.com.tw (ms.tl.gov.tw. [10.144.2.104])
	by firewall.chttl.com.tw (8.9.3/8.9.3) with ESMTP id LAA02023
	for <l2tp@ipsec.org>; Sat, 8 Apr 2000 11:44:35 +0800 (CST)
Received: from ms.chttl.com.tw ([10.144.169.37])
	by ms.chttl.com.tw (8.9.3/8.9.3) with ESMTP id LAA16570
	for <l2tp@ipsec.org>; Sat, 8 Apr 2000 11:45:34 +0800 (CST)
Message-ID: <38EEAB7F.C4FCF382@ms.chttl.com.tw>
Date: Sat, 08 Apr 2000 11:46:07 +0800
From: =?iso-8859-1?Q?=DFN=B7=AC?= <yhf@ms.chttl.com.tw>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: new draft about "Securing L2TP using IPSEC" ?
Content-Type: multipart/mixed;
 boundary="------------AEA592F6DB246C2828A78756"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

This is a multi-part message in MIME format.
--------------AEA592F6DB246C2828A78756
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,
Is there any new draft or standard comes out to obsoletes
the expired draft, "Securing L2TP using IPSEC" ?

Hsiao-Feng

--------------AEA592F6DB246C2828A78756
Content-Type: text/x-vcard; charset=us-ascii;
 name="yhf.vcf"
Content-Description: Card for ßN·¬
Content-Disposition: attachment;
 filename="yhf.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Yeh;Hsiao-Feng
tel;work:+886-3-4245064
x-mozilla-html:FALSE
fn;quoted-printable:=B8=AD=DFN=B7=AC
org:Chunghwa Telecom Co. TL.
adr:;;;;;;
version:2.1
email;internet:yhf@chttl.com.tw
end:vcard

--------------AEA592F6DB246C2828A78756--



From owner-l2tp@ipsec.org  Sat Apr  8 04:38:15 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08725
	for <l2tpext-archive@odin.ietf.org>; Sat, 8 Apr 2000 04:38:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id AAA13129; Sat, 8 Apr 2000 00:13:50 -0700 (PDT)
Received: from firewall.chttl.com.tw (gate.chttl.com.tw [202.39.157.254]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id AAA13124 for <l2tp@ipsec.org>; Sat, 8 Apr 2000 00:13:31 -0700 (PDT)
Received: from ms.chttl.com.tw (ms.tl.gov.tw. [10.144.2.104])
	by firewall.chttl.com.tw (8.9.3/8.9.3) with ESMTP id PAA00793
	for <l2tp@ipsec.org>; Sat, 8 Apr 2000 15:13:16 +0800 (CST)
Received: from ms.chttl.com.tw ([10.144.169.37])
	by ms.chttl.com.tw (8.9.3/8.9.3) with ESMTP id PAA16206
	for <l2tp@ipsec.org>; Sat, 8 Apr 2000 15:14:14 +0800 (CST)
Message-ID: <38EEDC67.5DB15485@ms.chttl.com.tw>
Date: Sat, 08 Apr 2000 15:14:48 +0800
From: =?iso-8859-1?Q?=DFN=B7=AC?= <yhf@ms.chttl.com.tw>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: how to test the interoperability?
Content-Type: multipart/mixed;
 boundary="------------E9BB009C17D0F806A5E18874"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

This is a multi-part message in MIME format.
--------------E9BB009C17D0F806A5E18874
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Is there any place or organization in which we can test the
interoperability of L2TP device?

Hsiao-Feng

--------------E9BB009C17D0F806A5E18874
Content-Type: text/x-vcard; charset=us-ascii;
 name="yhf.vcf"
Content-Description: Card for ßN·¬
Content-Disposition: attachment;
 filename="yhf.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Yeh;Hsiao-Feng
tel;work:+886-3-4245064
x-mozilla-html:FALSE
fn;quoted-printable:=B8=AD=DFN=B7=AC
org:Chunghwa Telecom Co. TL.
adr:;;;;;;
version:2.1
email;internet:yhf@chttl.com.tw
end:vcard

--------------E9BB009C17D0F806A5E18874--



From owner-l2tp@ipsec.org  Mon Apr 10 19:21:42 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06539
	for <l2tpext-archive@odin.ietf.org>; Mon, 10 Apr 2000 19:21:41 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id OAA00218; Mon, 10 Apr 2000 14:59:47 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.2.33]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA00214 for <l2tp@ipsec.org>; Mon, 10 Apr 2000 14:59:38 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id RAA21896 for <l2tp@ipsec.org>; Mon, 10 Apr 2000 17:59:02 -0400 (EDT)
Message-ID: <38F24E98.2E2A5892@cisco.com>
Date: Mon, 10 Apr 2000 17:58:48 -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@ipsec.org
Subject: presentations
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


If you presented in Australia, please send me your presentations.

Thanks,

- Mark


From owner-l2tp@ipsec.org  Mon Apr 10 19:22:11 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06567
	for <l2tpext-archive@odin.ietf.org>; Mon, 10 Apr 2000 19:22:10 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id PAA00369; Mon, 10 Apr 2000 15:14:57 -0700 (PDT)
Received: from amberex01.ambernetworks.com (outgate01.ambernetworks.com [207.20.187.199]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA00362 for <l2tp@ipsec.org>; Mon, 10 Apr 2000 15:14:44 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2448.0)
	id <2D2YAAFS>; Mon, 10 Apr 2000 14:26:31 -0700
Message-ID: <405CAE450410D311B26C0050047326DC6B7473@amberex01.ambernetworks.com>
From: Andy Koscinski <ANDYK@ambernetworks.com>
To: l2tp@ipsec.org
Subject: RE: question about the content of the subaddress in L2TP
Date: Mon, 10 Apr 2000 14:26:30 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

rfc2661, page 32:

"Sub-Address AVP (...)

The Sub-Address is an ASCII string. Contact between the administrator
of the LAC and the LNS may be necessary to coordinate interpretation
of the value in this AVP."


1. why has the subaddress to be ASCII if it's meaning is opaque to l2tp
and the network? could subaddress be any binary value, which is 
transparently transported LAC <-> LNS? 

2. what is the best way to exchange a non ASCII subaddress between
LAC and LNS?

andy koscinski: andyk@ambernetworks.com


 


From owner-l2tp@ipsec.org  Tue Apr 11 01:37:29 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17622
	for <l2tpext-archive@odin.ietf.org>; Tue, 11 Apr 2000 01:37:29 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id VAA01464; Mon, 10 Apr 2000 21:31:46 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id VAA01435 for <l2tp@ipsec.org>; Mon, 10 Apr 2000 21:30:16 -0700 (PDT)
Received: by ans2-pub.dttus.com id XAA04052
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Mon, 10 Apr 2000 23:30:03 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Mon, 10 Apr 2000 23:30:03 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Mon, 10 Apr 2000 23:30:03 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E656289CB0@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dttus.com>
To: Ly Loi <LLL@shastanets.com>
Cc: l2tp@ipsec.org
Subject: RE: l2tp questions
Date: Mon, 10 Apr 2000 23:27:56 -0500
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFA36E.46CA42B6"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

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

------_=_NextPart_001_01BFA36E.46CA42B6
Content-Type: text/plain;
	charset="iso-8859-1"

Aha classic case of defensive programming. Technically you should not
cleanup the session until you receive an ack for your CDN.  Also, you should
keep the session active for atleast 3 times the RTT between the LAC and the
LNS. A good idea is to mark the session table entry as "READY_TO_DELETE". If
you do not recevie anything till 3 RTT do a cleanup.
If you receive a CDN from the remote side then cleanup any ways. In fact the
condition u described below can very easily lead to random disconnects.
Think about a case where you reallocated the session table entry for another
incoming call, there is a chance that your CDN from the previous call may
disrupt this. A good implementation should recycle table entries in a ring
buffer order also, make sure the tunnel and sequence number validity before
processing a CDN or any other control message.

Hope this helps.

Regards

Rohit Verma
Consultant
Deloitte Consulting
180, N. Stetson Avenue
Chicago, IL 60601
312-374-2475

-----Original Message-----
From: Ly Loi [mailto:LLL@shastanets.com]
Sent: Monday, April 10, 2000 8:35 PM
To: 'Rohit Verma'
Cc: Ly Loi
Subject: l2tp questions


Hi Rohit, how are you? I've got the following l2tp question and wonder
whether there's a solution to it.

1. LAC and LNS at the same time bring down the L2TP session
2. Both LAC and LNS send to each other a CDN.
3. LAC deletes its L2TP session, THEN receives the CDN generated by the LNS.
Since the LAC has freed its L2TP session, it doesn't recognize the L2TP
session id in the CDN, thus drops the pkt.
4. LNS retransmits the CDN n times.
5. Each time, the LAC drops the CDN.
6. LNS eventually times out and brings down the tunnel.

What can I do to avoid having the LNS bring down the tunnel? The LAC didn't
ack the CDN because it has already gotten rid of the L2TP session data
structures.
Even if I have the LAC send a keep alive to the LNS, the LNS will continue
retransmitting the CDN since it is at the head of its transmit Q. What to
do?

Thanks much,

- Ly

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

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

<P><FONT SIZE=3D2>Aha classic case of defensive programming. =
Technically you should not cleanup the session until you receive an ack =
for your CDN.&nbsp; Also, you should keep the session active for =
atleast 3 times the RTT between the LAC and the LNS. A good idea is to =
mark the session table entry as &quot;READY_TO_DELETE&quot;. If you do =
not recevie anything till 3 RTT do a cleanup.</FONT></P>

<P><FONT SIZE=3D2>If you receive a CDN from the remote side then =
cleanup any ways. In fact the condition u described below can very =
easily lead to random disconnects. Think about a case where you =
reallocated the session table entry for another incoming call, there is =
a chance that your CDN from the previous call may disrupt this. A good =
implementation should recycle table entries in a ring buffer order =
also, make sure the tunnel and sequence number validity before =
processing a CDN or any other control message.</FONT></P>

<P><FONT SIZE=3D2>Hope this helps.</FONT>
</P>

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

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Ly Loi [<A =
HREF=3D"mailto:LLL@shastanets.com">mailto:LLL@shastanets.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Monday, April 10, 2000 8:35 PM</FONT>
<BR><FONT SIZE=3D2>To: 'Rohit Verma'</FONT>
<BR><FONT SIZE=3D2>Cc: Ly Loi</FONT>
<BR><FONT SIZE=3D2>Subject: l2tp questions</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi Rohit, how are you? I've got the following l2tp =
question and wonder</FONT>
<BR><FONT SIZE=3D2>whether there's a solution to it.</FONT>
</P>

<P><FONT SIZE=3D2>1. LAC and LNS at the same time bring down the L2TP =
session</FONT>
<BR><FONT SIZE=3D2>2. Both LAC and LNS send to each other a CDN.</FONT>
<BR><FONT SIZE=3D2>3. LAC deletes its L2TP session, THEN receives the =
CDN generated by the LNS.</FONT>
<BR><FONT SIZE=3D2>Since the LAC has freed its L2TP session, it doesn't =
recognize the L2TP</FONT>
<BR><FONT SIZE=3D2>session id in the CDN, thus drops the pkt.</FONT>
<BR><FONT SIZE=3D2>4. LNS retransmits the CDN n times.</FONT>
<BR><FONT SIZE=3D2>5. Each time, the LAC drops the CDN.</FONT>
<BR><FONT SIZE=3D2>6. LNS eventually times out and brings down the =
tunnel.</FONT>
</P>

<P><FONT SIZE=3D2>What can I do to avoid having the LNS bring down the =
tunnel? The LAC didn't</FONT>
<BR><FONT SIZE=3D2>ack the CDN because it has already gotten rid of the =
L2TP session data</FONT>
<BR><FONT SIZE=3D2>structures.</FONT>
<BR><FONT SIZE=3D2>Even if I have the LAC send a keep alive to the LNS, =
the LNS will continue</FONT>
<BR><FONT SIZE=3D2>retransmitting the CDN since it is at the head of =
its transmit Q. What to</FONT>
<BR><FONT SIZE=3D2>do?</FONT>
</P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01BFA36E.46CA42B6--


From owner-l2tp@ipsec.org  Tue Apr 11 13:46:45 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14710
	for <l2tpext-archive@odin.ietf.org>; Tue, 11 Apr 2000 13:46:44 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id JAA03369; Tue, 11 Apr 2000 09:35:39 -0700 (PDT)
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA03365 for <l2tp@ipsec.org>; Tue, 11 Apr 2000 09:34:43 -0700 (PDT)
Received: from acc.com (unk105122.acc.com [129.192.105.122])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id JAA13461;
	Tue, 11 Apr 2000 09:36:50 -0700 (PDT)
Message-ID: <38F354BB.417D5B9D@acc.com>
Date: Tue, 11 Apr 2000 09:37:15 -0700
From: Evan Caves <evan@acc.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Verma, Rohit (US - Chicago)" <rverma@dttus.com>
CC: Ly Loi <LLL@shastanets.com>, l2tp@ipsec.org
Subject: Re: l2tp questions
References: <2F4A3F6B7BF5D3119E2500508B94E656289CB0@uscntnt405a.us.deloitte.com>
Content-Type: multipart/alternative;
 boundary="------------97F7C12BC0BBCD225EA76280"
Sender: owner-l2tp@sailpix.com
Precedence: bulk


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

Since the LAC received the CDN it should update its Nr. What the LAC
does after this
(in most cases) does not affect Nr. The LAC should then send back a zlb
ack with new
Nr or piggy back Nr in the next message.

evan
-


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

>
>
> Aha classic case of defensive programming. Technically you should not
> cleanup the session until you receive an ack for your CDN.  Also, you
> should keep the session active for atleast 3 times the RTT between the
> LAC and the LNS. A good idea is to mark the session table entry as
> "READY_TO_DELETE". If you do not recevie anything till 3 RTT do a
> cleanup.
>
> If you receive a CDN from the remote side then cleanup any ways. In
> fact the condition u described below can very easily lead to random
> disconnects. Think about a case where you reallocated the session
> table entry for another incoming call, there is a chance that your CDN
> from the previous call may disrupt this. A good implementation should
> recycle table entries in a ring buffer order also, make sure the
> tunnel and sequence number validity before processing a CDN or any
> other control message.
>
> Hope this helps.
>
> Regards
>
> Rohit Verma
> Consultant
> Deloitte Consulting
> 180, N. Stetson Avenue
> Chicago, IL 60601
> 312-374-2475
>
> -----Original Message-----
> From: Ly Loi [mailto:LLL@shastanets.com]
> Sent: Monday, April 10, 2000 8:35 PM
> To: 'Rohit Verma'
> Cc: Ly Loi
> Subject: l2tp questions
>
> Hi Rohit, how are you? I've got the following l2tp question and wonder
>
> whether there's a solution to it.
>
> 1. LAC and LNS at the same time bring down the L2TP session
> 2. Both LAC and LNS send to each other a CDN.
> 3. LAC deletes its L2TP session, THEN receives the CDN generated by
> the LNS.
> Since the LAC has freed its L2TP session, it doesn't recognize the
> L2TP
> session id in the CDN, thus drops the pkt.
> 4. LNS retransmits the CDN n times.
> 5. Each time, the LAC drops the CDN.
> 6. LNS eventually times out and brings down the tunnel.
>
> What can I do to avoid having the LNS bring down the tunnel? The LAC
> didn't
> ack the CDN because it has already gotten rid of the L2TP session data
>
> structures.
> Even if I have the LAC send a keep alive to the LNS, the LNS will
> continue
> retransmitting the CDN since it is at the head of its transmit Q. What
> to
> do?
>
> Thanks much,
>
> - Ly

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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Since the LAC received the CDN it should update its Nr. What the LAC does
after this
<br>(in most cases) does not affect Nr. The LAC should then send back a
zlb ack with new
<br>Nr or piggy back Nr in the next message.
<p>evan
<br>-
<br>&nbsp;
<p>"Verma, Rohit (US - Chicago)" wrote:
<blockquote TYPE=CITE>&nbsp;
<p><font size=-1>Aha classic case of defensive programming. Technically
you should not cleanup the session until you receive an ack for your CDN.&nbsp;
Also, you should keep the session active for atleast 3 times the RTT between
the LAC and the LNS. A good idea is to mark the session table entry as
"READY_TO_DELETE". If you do not recevie anything till 3 RTT do a cleanup.</font>
<p><font size=-1>If you receive a CDN from the remote side then cleanup
any ways. In fact the condition u described below can very easily lead
to random disconnects. Think about a case where you reallocated the session
table entry for another incoming call, there is a chance that your CDN
from the previous call may disrupt this. A good implementation should recycle
table entries in a ring buffer order also, make sure the tunnel and sequence
number validity before processing a CDN or any other control message.</font>
<p><font size=-1>Hope this helps.</font>
<p><font size=-1>Regards</font>
<p><font size=-1>Rohit Verma</font>
<br><font size=-1>Consultant</font>
<br><font size=-1>Deloitte Consulting</font>
<br><font size=-1>180, N. Stetson Avenue</font>
<br><font size=-1>Chicago, IL 60601</font>
<br><font size=-1>312-374-2475</font>
<p><font size=-1>-----Original Message-----</font>
<br><font size=-1>From: Ly Loi [<a href="mailto:LLL@shastanets.com">mailto:LLL@shastanets.com</a>]</font>
<br><font size=-1>Sent: Monday, April 10, 2000 8:35 PM</font>
<br><font size=-1>To: 'Rohit Verma'</font>
<br><font size=-1>Cc: Ly Loi</font>
<br><font size=-1>Subject: l2tp questions</font>
<p><font size=-1>Hi Rohit, how are you? I've got the following l2tp question
and wonder</font>
<br><font size=-1>whether there's a solution to it.</font>
<p><font size=-1>1. LAC and LNS at the same time bring down the L2TP session</font>
<br><font size=-1>2. Both LAC and LNS send to each other a CDN.</font>
<br><font size=-1>3. LAC deletes its L2TP session, THEN receives the CDN
generated by the LNS.</font>
<br><font size=-1>Since the LAC has freed its L2TP session, it doesn't
recognize the L2TP</font>
<br><font size=-1>session id in the CDN, thus drops the pkt.</font>
<br><font size=-1>4. LNS retransmits the CDN n times.</font>
<br><font size=-1>5. Each time, the LAC drops the CDN.</font>
<br><font size=-1>6. LNS eventually times out and brings down the tunnel.</font>
<p><font size=-1>What can I do to avoid having the LNS bring down the tunnel?
The LAC didn't</font>
<br><font size=-1>ack the CDN because it has already gotten rid of the
L2TP session data</font>
<br><font size=-1>structures.</font>
<br><font size=-1>Even if I have the LAC send a keep alive to the LNS,
the LNS will continue</font>
<br><font size=-1>retransmitting the CDN since it is at the head of its
transmit Q. What to</font>
<br><font size=-1>do?</font>
<p><font size=-1>Thanks much,</font>
<p><font size=-1>- Ly</font></blockquote>
</html>

--------------97F7C12BC0BBCD225EA76280--



From owner-l2tp@ipsec.org  Thu Apr 13 15:14:15 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11636
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 15:14:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA08888; Thu, 13 Apr 2000 10:52:32 -0700 (PDT)
Received: from poseidon.broadpac.com (adsl-63-199-87-6.dsl.snfc21.pacbell.net [63.199.87.6]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA08884 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 10:52:15 -0700 (PDT)
Received: 
	by poseidon.broadpac.com (8.9.1/8.9.1) with SMTP id KAA07684
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 10:53:22 -0700 (PDT)
Message-ID: <02ea01bfa571$0302b5e0$7164a8c0@ruchirnt>
From: "Ruchir" <ruchir@broadpac.com>
To: <l2tp@ipsec.org>
Subject: latest ipsec , isakmp and ike MIB drafts
Date: Thu, 13 Apr 2000 10:52:09 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02DD_01BFA536.51292050"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@sailpix.com
Precedence: bulk

This is a multi-part message in MIME format.

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

Hi
    Which are the latest drafts on IPSEC, ISAKMP AND IKE MIBs ?

Ruchir

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; Which are the latest =
drafts=20
on&nbsp;IPSEC, ISAKMP AND IKE MIBs ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ruchir</FONT></DIV></BODY></HTML>

------=_NextPart_000_02DD_01BFA536.51292050--



From owner-l2tp@ipsec.org  Thu Apr 13 16:54:25 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13770
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 16:54:24 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id MAA09183; Thu, 13 Apr 2000 12:53:00 -0700 (PDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA09176 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:52:42 -0700 (PDT)
Received: from rapid5.com (colorado.rapid5.com [209.24.141.61])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id MAA01618
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:50:04 -0700 (PDT)
Received: from nile.rapid5.com (nile.rapid5.com [192.9.200.201])
	by rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id MAA02850
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:47:37 -0700 (PDT)
X-Recipient: <l2tp@ipsec.org>
Deliver-To: <l2tp@ipsec.org>
Received: from rapid5.com (dell_pc12 [192.9.200.224])
	by nile.rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id MAA07473
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:49:59 -0700 (PDT)
Message-ID: <38F57CCC.8B2C4284@rapid5.com>
Date: Thu, 13 Apr 2000 00:52:44 -0700
From: Srikrishnan <srikrish@rapid5.com>
Reply-To: srikrish@rapid5.com
Organization: Rapid5 Networks
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

   L2TP RFC 2661 section 5.4 (give below)
"Unlike the L2TP control channel, the L2TP data channel does not use
   sequence numbers to retransmit lost data messages. Rather, data
   messages may use sequence numbers to detect lost packets and/or
   restore the original sequence of packets that may have been reordered

   during transport.  The LAC may request that sequence numbers be"

   proposes that Sequence Numbers in Payload can be used for
   reordering of data packets and/or detect packets lost.

   But how can a packet be detected if we cant resynchronize the
   Sequence number after the first packet loss.

    For ex:  If sequence 1,2,3 sent by LAC to LNS and 2 is lost. By
    what mechanism   will LNS detect the packet loss?

     Previous L2TP drafts ( earlier versions) detailed about RESET
Packet
     which can be used for resync. But RFC doesnt talk about that too.

     Can anyone please explain how this can be done.
     Am I missing something?

Regards
Srikrishnan.





From owner-l2tp@ipsec.org  Thu Apr 13 16:57:22 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13825
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 16:57:22 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id NAA09209; Thu, 13 Apr 2000 13:04:26 -0700 (PDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA09205 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 13:04:11 -0700 (PDT)
Received: from rapid5.com (colorado.rapid5.com [209.24.141.61])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id NAA14029
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 13:02:16 -0700 (PDT)
Received: from nile.rapid5.com (nile.rapid5.com [192.9.200.201])
	by rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id MAA02922
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:59:49 -0700 (PDT)
X-Recipient: <l2tp@ipsec.org>
Deliver-To: <l2tp@ipsec.org>
Received: from rapid5.com (dell_pc12 [192.9.200.224])
	by nile.rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id NAA07536
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 13:02:10 -0700 (PDT)
Message-ID: <38F57FA8.E61F7D70@rapid5.com>
Date: Thu, 13 Apr 2000 01:04:56 -0700
From: Srikrishnan <srikrish@rapid5.com>
Reply-To: srikrish@rapid5.com
Organization: Rapid5 Networks
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: Question on ISP's L2TP implementation
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

    I've following question regarding typical ISP implementation,

     Eventhough RFC suggests we can have any number of tunnels
     between LAC-LNS pair,

     Will ISP typically allow more than one Tunnel from a NODE?

      I would appreciate an answer from people who did
interoperatability with
      ISP's LNS.

Thanks in Advance,
Srikrishnan.







From owner-l2tp@ipsec.org  Thu Apr 13 16:57:30 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13836
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 16:57:29 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA09231; Thu, 13 Apr 2000 13:07:31 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA09227 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 13:07:20 -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 NAA29674;
	Thu, 13 Apr 2000 13:06:50 -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 QAA02792; Thu, 13 Apr 2000 16:06:48 -0400 (EDT)
Message-ID: <38F628C1.7A0F159A@cisco.com>
Date: Thu, 13 Apr 2000 16:06:25 -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: srikrish@rapid5.com
CC: l2tp@ipsec.org
Subject: Re: How to get a Vendor ID?
References: <38F57D2E.7BBA1FD9@rapid5.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srikrishnan wrote:
> 
> Hi,
> 
>    Can anyone please tell how to get Vendor ID?
>    I know its from IANA but how?

Check the references section in the RFC.

> 
> Thanks in Advance,
> Srikrishnan


From owner-l2tp@ipsec.org  Thu Apr 13 16:57:53 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13847
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 16:57:53 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id NAA09245; Thu, 13 Apr 2000 13:09:30 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA09241 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 13:09:10 -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 NAA00639;
	Thu, 13 Apr 2000 13:08: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 QAA02796; Thu, 13 Apr 2000 16:08:39 -0400 (EDT)
Message-ID: <38F62930.32465FE7@cisco.com>
Date: Thu, 13 Apr 2000 16:08:16 -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: srikrish@rapid5.com
CC: l2tp@ipsec.org
Subject: Re: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
References: <38F57CCC.8B2C4284@rapid5.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srikrishnan wrote:
> 
> Hi,
> 
>    L2TP RFC 2661 section 5.4 (give below)
> "Unlike the L2TP control channel, the L2TP data channel does not use
>    sequence numbers to retransmit lost data messages. Rather, data
>    messages may use sequence numbers to detect lost packets and/or
>    restore the original sequence of packets that may have been reordered
> 
>    during transport.  The LAC may request that sequence numbers be"
> 
>    proposes that Sequence Numbers in Payload can be used for
>    reordering of data packets and/or detect packets lost.
> 
>    But how can a packet be detected if we cant resynchronize the
>    Sequence number after the first packet loss.
> 
>     For ex:  If sequence 1,2,3 sent by LAC to LNS and 2 is lost. By
>     what mechanism   will LNS detect the packet loss?

If 2 is lost, the LNS would not see it. The LNS would only see 1 and 3. 

> 
>      Previous L2TP drafts ( earlier versions) detailed about RESET
> Packet
>      which can be used for resync. But RFC doesnt talk about that too.

The Rbit was used for flow control (e.g. to allow communication of
packet loss back to the sending peer - in your example, the LAC). Flow
control was removed from the RFC.

> 
>      Can anyone please explain how this can be done.
>      Am I missing something?
> 
> Regards
> Srikrishnan.


From owner-l2tp@ipsec.org  Thu Apr 13 16:59:17 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13892
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 16:59:17 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id MAA09171; Thu, 13 Apr 2000 12:52:20 -0700 (PDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA09167 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:52:09 -0700 (PDT)
Received: from rapid5.com (colorado.rapid5.com [209.24.141.61])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id MAA10893
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:51:41 -0700 (PDT)
Received: from nile.rapid5.com (nile.rapid5.com [192.9.200.201])
	by rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id MAA02858
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:49:15 -0700 (PDT)
X-Recipient: <l2tp@ipsec.org>
Deliver-To: <l2tp@ipsec.org>
Received: from rapid5.com (dell_pc12 [192.9.200.224])
	by nile.rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id MAA07486
	for <l2tp@ipsec.org>; Thu, 13 Apr 2000 12:51:36 -0700 (PDT)
Message-ID: <38F57D2E.7BBA1FD9@rapid5.com>
Date: Thu, 13 Apr 2000 00:54:22 -0700
From: Srikrishnan <srikrish@rapid5.com>
Reply-To: srikrish@rapid5.com
Organization: Rapid5 Networks
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: How to get a Vendor ID?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

   Can anyone please tell how to get Vendor ID?
   I know its from IANA but how?

Thanks in Advance,
Srikrishnan



From owner-l2tp@ipsec.org  Thu Apr 13 17:06:38 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14075
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 17:06:38 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id NAA09366; Thu, 13 Apr 2000 13:21:37 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA09362 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 13:21:22 -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 NAA07866;
	Thu, 13 Apr 2000 13:20:54 -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 QAA02804; Thu, 13 Apr 2000 16:20:51 -0400 (EDT)
Message-ID: <38F62C0C.F9E79F15@cisco.com>
Date: Thu, 13 Apr 2000 16:20:28 -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: srikrish@rapid5.com
CC: l2tp@ipsec.org
Subject: Re: Question on ISP's L2TP implementation
References: <38F57FA8.E61F7D70@rapid5.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srikrishnan wrote:
> 
> Hi,
> 
>     I've following question regarding typical ISP implementation,
> 
>      Eventhough RFC suggests we can have any number of tunnels
>      between LAC-LNS pair,
> 
>      Will ISP typically allow more than one Tunnel from a NODE?

In some cases, yes. It is up to the implementation.

> 
>       I would appreciate an answer from people who did
> interoperatability with
>       ISP's LNS.
> 
> Thanks in Advance,
> Srikrishnan.


From owner-l2tp@ipsec.org  Thu Apr 13 18:29:08 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15127
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 18:29:07 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id OAA09598; Thu, 13 Apr 2000 14:13:11 -0700 (PDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA09594 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 14:12:50 -0700 (PDT)
Received: from rapid5.com (colorado.rapid5.com [209.24.141.61])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id OAA07785;
	Thu, 13 Apr 2000 14:10:17 -0700 (PDT)
Received: from nile.rapid5.com (nile.rapid5.com [192.9.200.201])
	by rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id OAA03334;
	Thu, 13 Apr 2000 14:07:50 -0700 (PDT)
Received: from rapid5.com (dell_pc12 [192.9.200.224])
	by nile.rapid5.com (8.9.1b+Sun/8.8.8) with ESMTP id OAA07916;
	Thu, 13 Apr 2000 14:10:12 -0700 (PDT)
Message-ID: <38F58F99.8A61A65E@rapid5.com>
Date: Thu, 13 Apr 2000 02:12:57 -0700
From: Srikrishnan <srikrish@rapid5.com>
Reply-To: srikrish@rapid5.com
Organization: Rapid5 Networks
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
CC: l2tp@ipsec.org
Subject: Re: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
References: <38F57CCC.8B2C4284@rapid5.com> <38F62930.32465FE7@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



"W. Mark Townsley" wrote:

> Srikrishnan wrote:
> >
> > Hi,
> >
> >    L2TP RFC 2661 section 5.4 (give below)
> > "Unlike the L2TP control channel, the L2TP data channel does not use
> >    sequence numbers to retransmit lost data messages. Rather, data
> >    messages may use sequence numbers to detect lost packets and/or
> >    restore the original sequence of packets that may have been reordered
> >
> >    during transport.  The LAC may request that sequence numbers be"
> >
> >    proposes that Sequence Numbers in Payload can be used for
> >    reordering of data packets and/or detect packets lost.
> >
> >    But how can a packet be detected if we cant resynchronize the
> >    Sequence number after the first packet loss.
> >
> >     For ex:  If sequence 1,2,3 sent by LAC to LNS and 2 is lost. By
> >     what mechanism   will LNS detect the packet loss?
>
> If 2 is lost, the LNS would not see it. The LNS would only see 1 and 3.
>

My Point is exactly that, at the time of getting 3, how could LNS conclude
whether the packet 2 is lost or delayed in the network?
As its not serial link, there is lot of chances that the packet 2 may be
delayed.

If you see the section mentioned about, it says LNS can reorder the packet
or detect packet loss. I could'nt see any way to do that. ( may be some
timer!!)

Your response will be appreicated.

Thanks in Advance,
Srikrishnan.



From owner-l2tp@ipsec.org  Thu Apr 13 19:50:15 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16087
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 19:50:14 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id QAA09951; Thu, 13 Apr 2000 16:02:19 -0700 (PDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA09947 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 16:02:06 -0700 (PDT)
Received: from gwz (ssh.cisco.com [171.69.10.34]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id QAA27983; Thu, 13 Apr 2000 16:01:34 -0700 (PDT)
From: "Glen Zorn" <gwz@cisco.com>
To: <srikrish@rapid5.com>, <l2tp@ipsec.org>
Subject: RE: How to get a Vendor ID?
Date: Thu, 13 Apr 2000 16:01:21 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPIEDKCCAA.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: <38F57D2E.7BBA1FD9@rapid5.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

>
> Hi,
>
>    Can anyone please tell how to get Vendor ID?

If your company already has an SMI Network Management Private Enterprise
Code, it should be listed here:
http://www.isi.edu/in-notes/iana/assignments/enterprise-numbers ;
if not, the on-line application is here:
http://www.isi.edu/cgi-bin/iana/enterprise.pl .

>    I know its from IANA but how?
>
> Thanks in Advance,
> Srikrishnan
>
>
>



From owner-l2tp@ipsec.org  Thu Apr 13 20:45:59 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16533
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 20:45:59 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id QAA10095; Thu, 13 Apr 2000 16:52:08 -0700 (PDT)
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA10089 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 16:51:44 -0700 (PDT)
Received: from acc.com (unk105122.acc.com [129.192.105.122])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id QAA05904;
	Thu, 13 Apr 2000 16:54:20 -0700 (PDT)
Message-ID: <38F65E47.2F9AD7B7@acc.com>
Date: Thu, 13 Apr 2000 16:54:47 -0700
From: Evan Caves <evan@acc.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: srikrish@rapid5.com
CC: "W. Mark Townsley" <townsley@cisco.com>, l2tp@ipsec.org
Subject: Re: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
References: <38F57CCC.8B2C4284@rapid5.com> <38F62930.32465FE7@cisco.com> <38F58F99.8A61A65E@rapid5.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srikrishnan wrote:

> "W. Mark Townsley" wrote:
>
> > Srikrishnan wrote:
> > >
> > > Hi,
> > >
> > >    L2TP RFC 2661 section 5.4 (give below)
> > > "Unlike the L2TP control channel, the L2TP data channel does not use
> > >    sequence numbers to retransmit lost data messages. Rather, data
> > >    messages may use sequence numbers to detect lost packets and/or
> > >    restore the original sequence of packets that may have been reordered
> > >
> > >    during transport.  The LAC may request that sequence numbers be"
> > >
> > >    proposes that Sequence Numbers in Payload can be used for
> > >    reordering of data packets and/or detect packets lost.
> > >
> > >    But how can a packet be detected if we cant resynchronize the
> > >    Sequence number after the first packet loss.
> > >
> > >     For ex:  If sequence 1,2,3 sent by LAC to LNS and 2 is lost. By
> > >     what mechanism   will LNS detect the packet loss?
> >
> > If 2 is lost, the LNS would not see it. The LNS would only see 1 and 3.
> >
>
> My Point is exactly that, at the time of getting 3, how could LNS conclude
> whether the packet 2 is lost or delayed in the network?
> As its not serial link, there is lot of chances that the packet 2 may be
> delayed.
>
> If you see the section mentioned about, it says LNS can reorder the packet
> or detect packet loss. I could'nt see any way to do that. ( may be some
> timer!!)

Yes you would need to use some kind of timer mechanism and possibly force
flush based on queue depth.

evan
-

>
>
> Your response will be appreicated.
>
> Thanks in Advance,
> Srikrishnan.



From owner-l2tp@ipsec.org  Thu Apr 13 20:59:43 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16691
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 20:59:43 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id QAA10116; Thu, 13 Apr 2000 16:59:27 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA10112 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 16:58:58 -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 QAA07559;
	Thu, 13 Apr 2000 16:58: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 TAA02876; Thu, 13 Apr 2000 19:58:27 -0400 (EDT)
Message-ID: <38F65F0C.E24EBBBE@cisco.com>
Date: Thu, 13 Apr 2000 19:58:04 -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: Evan Caves <evan@acc.com>
CC: srikrish@rapid5.com, l2tp@ipsec.org
Subject: Re: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
References: <38F57CCC.8B2C4284@rapid5.com> <38F62930.32465FE7@cisco.com> <38F58F99.8A61A65E@rapid5.com> <38F65E47.2F9AD7B7@acc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Evan Caves wrote:
> 
> Srikrishnan wrote:
> 
> > "W. Mark Townsley" wrote:
> >
> > > Srikrishnan wrote:
> > > >
> > > > Hi,
> > > >
> > > >    L2TP RFC 2661 section 5.4 (give below)
> > > > "Unlike the L2TP control channel, the L2TP data channel does not use
> > > >    sequence numbers to retransmit lost data messages. Rather, data
> > > >    messages may use sequence numbers to detect lost packets and/or
> > > >    restore the original sequence of packets that may have been reordered
> > > >
> > > >    during transport.  The LAC may request that sequence numbers be"
> > > >
> > > >    proposes that Sequence Numbers in Payload can be used for
> > > >    reordering of data packets and/or detect packets lost.
> > > >
> > > >    But how can a packet be detected if we cant resynchronize the
> > > >    Sequence number after the first packet loss.
> > > >
> > > >     For ex:  If sequence 1,2,3 sent by LAC to LNS and 2 is lost. By
> > > >     what mechanism   will LNS detect the packet loss?
> > >
> > > If 2 is lost, the LNS would not see it. The LNS would only see 1 and 3.
> > >
> >
> > My Point is exactly that, at the time of getting 3, how could LNS conclude
> > whether the packet 2 is lost or delayed in the network?
> > As its not serial link, there is lot of chances that the packet 2 may be
> > delayed.
> >
> > If you see the section mentioned about, it says LNS can reorder the packet
> > or detect packet loss. I could'nt see any way to do that. ( may be some
> > timer!!)
> 
> Yes you would need to use some kind of timer mechanism and possibly force
> flush based on queue depth.

Yes. But don't wait around too long as you don't want to cause the
higher layer (e.g. TCP) RTT calculations to get skewed heavily. If you
must reorder, I would recommend a very short queue with depth flush as
Evan mentioned, and perhaps a short timer as well if you can afford it
(this all depends on your scalability requirements). 

For L2 tunneled IP data packets (without stateful compression or
encryption of course), I have seen little reason in practice not to go
ahead and pass data as it is received - in order or not.

> 
> evan
> -
> 
> >
> >
> > Your response will be appreicated.
> >
> > Thanks in Advance,
> > Srikrishnan.


From owner-l2tp@ipsec.org  Thu Apr 13 21:18:59 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16879
	for <l2tpext-archive@odin.ietf.org>; Thu, 13 Apr 2000 21:18:59 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id RAA10159; Thu, 13 Apr 2000 17:19:43 -0700 (PDT)
Received: from shasta-exch.shastanets.com (mailserver.shastanets.com [199.242.48.25] (may be forged)) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA10155 for <l2tp@ipsec.org>; Thu, 13 Apr 2000 17:19:33 -0700 (PDT)
Received: by shasta-exch.shastanets.com with Internet Mail Service (5.5.2650.21)
	id <2LGCDKAY>; Thu, 13 Apr 2000 17:19:02 -0700
Message-ID: <4DEC824F6F1FD3119BEF0000E86CEA010287E390@shasta-exch.shastanets.com>
From: Vipin Jain <vipin@shastanets.com>
To: "'srikrish@rapid5.com'" <srikrish@rapid5.com>,
        "W. Mark Townsley"
	 <townsley@cisco.com>
Cc: l2tp@ipsec.org
Subject: RE: How to Reorder/Detect packet loss  in case of Payload L2TP pa
	ckets?
Date: Thu, 13 Apr 2000 17:19:00 -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@sailpix.com
Precedence: bulk

> If you see the section mentioned about, it says LNS can reorder the packet
> or detect packet loss. I could'nt see any way to do that. ( may be some
> timer!!)
How to detect packet loss is implementation specific, I think.
Only information LNS has to conclude something from, is sequence numbers.
Using timers is one way; Other implementation could assume
that packet is lost if its queues are full.

- Vipin


From owner-l2tp@ipsec.org  Fri Apr 14 05:34:10 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04811
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 05:34:09 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id BAA10933; Fri, 14 Apr 2000 01:09:28 -0700 (PDT)
Received: from p-biset.issy.cnet.fr (p-biset.issy.cnet.fr [139.100.0.33]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id BAA10929 for <l2tp@ipsec.org>; Fri, 14 Apr 2000 01:09:11 -0700 (PDT)
Received: by p-biset.issy.cnet.fr with Internet Mail Service (5.5.2448.0)
	id <2K2JK4CN>; Fri, 14 Apr 2000 10:09:03 +0200
Message-ID: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr>
From: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>
To: "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: ZLB Ack.
Date: Fri, 14 Apr 2000 10:08:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

What is the condition to send a ZLB Ack (see the example below), is this a
timer or something else ? The rfc says only that "the ZLB Ack is sent if
there are no futher messages waiting in the queue".

LAC						LNS

SCCRQ ---->
					<----SCCRP
SCCCN ---->
					<----ZLB ACK

But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
the ZLB ACK.
Thank you for your help.


From owner-l2tp@ipsec.org  Fri Apr 14 06:41:56 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05319
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 06:41:55 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id CAA10982; Fri, 14 Apr 2000 02:16:06 -0700 (PDT)
Received: from shasta-exch.shastanets.com (mailserver.shastanets.com [199.242.48.25] (may be forged)) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id CAA10978 for <l2tp@ipsec.org>; Fri, 14 Apr 2000 02:15:50 -0700 (PDT)
Received: by shasta-exch.shastanets.com with Internet Mail Service (5.5.2650.21)
	id <2LGCDKZ6>; Fri, 14 Apr 2000 02:15:19 -0700
Message-ID: <4DEC824F6F1FD3119BEF0000E86CEA010287E396@shasta-exch.shastanets.com>
From: Vipin Jain <vipin@shastanets.com>
To: "'HOULLIER Francis FTRD/DMI/CAE'" <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: RE: ZLB Ack.
Date: Fri, 14 Apr 2000 02:15:17 -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@sailpix.com
Precedence: bulk


As per specs, it should be when there are
"no further messages waiting in the queue",
which means ZLB ACK could be sent _as soon as_
it processes SCCCN and discovers there are
no messages waiting to be sent.

- Vipin

-----Original Message-----
From: HOULLIER Francis FTRD/DMI/CAE
[mailto:francis.houllier@rd.francetelecom.fr]
Sent: Friday, April 14, 2000 1:08 AM
To: 'Mailing liste L2TP'
Subject: ZLB Ack.


What is the condition to send a ZLB Ack (see the example below), is this a
timer or something else ? The rfc says only that "the ZLB Ack is sent if
there are no futher messages waiting in the queue".

LAC						LNS

SCCRQ ---->
					<----SCCRP
SCCCN ---->
					<----ZLB ACK

But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
the ZLB ACK.
Thank you for your help.


From owner-l2tp@ipsec.org  Fri Apr 14 11:12:34 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08796
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 11:12:34 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id GAA12464; Fri, 14 Apr 2000 06:57:35 -0700 (PDT)
Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id GAA12460 for <l2tp@sailpix.com>; Fri, 14 Apr 2000 06:57:17 -0700 (PDT)
From: Barney Wolff <barney@databus.com>
To: l2tp@sailpix.com
Date: Fri, 14 Apr 2000 09:51 EDT
Subject: Re: ZLB Ack.
Content-Type: text/plain
Message-ID: <38f723b90.2b7b@databus.databus.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

The queue is the output queue.  From the LNS's point of view when it
gets the SCCCN, it has nothing to send and must ack the SCCCN, so it
sends the ZLB.  It would be a (imho) needless sophistication for the
LNS to implement delayed acks and hope that the LAC will send another
packet quickly.  The cost of L2TP is the header applied to each PPP
frame, not the very few packets exchanged to setup/teardown tunnels
and sessions.

Regards,
Barney Wolff

> From: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>
> Date: Fri, 14 Apr 2000 10:08:16 +0200
> 
> What is the condition to send a ZLB Ack (see the example below), is this a
> timer or something else ? The rfc says only that "the ZLB Ack is sent if
> there are no futher messages waiting in the queue".
> 
> LAC						LNS
> 
> SCCRQ ---->
> 					<----SCCRP
> SCCCN ---->
> 					<----ZLB ACK
> 
> But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> the ZLB ACK.
> Thank you for your help.
> 


From owner-l2tp@ipsec.org  Fri Apr 14 11:17:01 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08852
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 11:17:00 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id HAA12499; Fri, 14 Apr 2000 07:15:50 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id HAA12495 for <l2tp@ipsec.org>; Fri, 14 Apr 2000 07:14:58 -0700 (PDT)
Received: by ans2-pub.dttus.com id JAA24927
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Fri, 14 Apr 2000 09:14:47 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Fri, 14 Apr 2000 09:14:47 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Fri, 14 Apr 2000 09:14:47 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E656329358@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        l2tp@ipsec.org
Subject: RE: ZLB Ack.
Date: Fri, 14 Apr 2000 10:02:43 -0400
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFA61A.0E8A446A"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

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

------_=_NextPart_001_01BFA61A.0E8A446A
Content-Type: text/plain;
	charset="iso-8859-1"

Most of the time, you would like to conserve bandwidth, so you waould want
to piggyback your ack on information packets. (Such as ack for the SCCRQ can
be sent in the SCCRP msg)
The ZLB ack procides you a mechanism to accoplish, sending acks without the
information. Hence when you do not have any information to piggyback the ack
on, you should send a ZLB ack.

Hope this helps

Regards

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


-----Original Message-----
From: HOULLIER Francis FTRD/DMI/CAE
[mailto:francis.houllier@rd.francetelecom.fr]
Sent: Friday, April 14, 2000 3:08 AM
To: 'Mailing liste L2TP'
Subject: ZLB Ack.


What is the condition to send a ZLB Ack (see the example below), is this a
timer or something else ? The rfc says only that "the ZLB Ack is sent if
there are no futher messages waiting in the queue".

LAC						LNS

SCCRQ ---->
					<----SCCRP
SCCCN ---->
					<----ZLB ACK

But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
the ZLB ACK.
Thank you for your help.

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

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

<P><FONT SIZE=3D2>Most of the time, you would like to conserve =
bandwidth, so you waould want to piggyback your ack on information =
packets. (Such as ack for the SCCRQ can be sent in the SCCRP =
msg)</FONT></P>

<P><FONT SIZE=3D2>The ZLB ack procides you a mechanism to accoplish, =
sending acks without the information. Hence when you do not have any =
information to piggyback the ack on, you should send a ZLB =
ack.</FONT></P>

<P><FONT SIZE=3D2>Hope this helps</FONT>
</P>

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

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: HOULLIER Francis FTRD/DMI/CAE</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:francis.houllier@rd.francetelecom.fr">mailto:francis.houl=
lier@rd.francetelecom.fr</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, April 14, 2000 3:08 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Mailing liste L2TP'</FONT>
<BR><FONT SIZE=3D2>Subject: ZLB Ack.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>What is the condition to send a ZLB Ack (see the =
example below), is this a</FONT>
<BR><FONT SIZE=3D2>timer or something else ? The rfc says only that =
&quot;the ZLB Ack is sent if</FONT>
<BR><FONT SIZE=3D2>there are no futher messages waiting in the =
queue&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>LAC&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</FONT>
</P>

<P><FONT SIZE=3D2>SCCRQ ----&gt;</FONT>
<BR>&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; <FONT =
SIZE=3D2>&lt;----SCCRP</FONT>
<BR><FONT SIZE=3D2>SCCCN ----&gt;</FONT>
<BR>&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; <FONT SIZE=3D2>&lt;----ZLB =
ACK</FONT>
</P>

<P><FONT SIZE=3D2>But generally after the SCCCN, the LAC sends an ICRQ =
and the LNS can't send</FONT>
<BR><FONT SIZE=3D2>the ZLB ACK.</FONT>
<BR><FONT SIZE=3D2>Thank you for your help.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFA61A.0E8A446A--


From owner-l2tp@ipsec.org  Fri Apr 14 20:19:41 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16141
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 20:19:40 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id QAA13199; Fri, 14 Apr 2000 16:17:05 -0700 (PDT)
Received: from poseidon.broadpac.com (adsl-63-199-87-6.dsl.snfc21.pacbell.net [63.199.87.6]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA13195 for <l2tp@ipsec.org>; Fri, 14 Apr 2000 16:16:22 -0700 (PDT)
Received: 
	by poseidon.broadpac.com (8.9.1/8.9.1) with SMTP id QAA14200;
	Fri, 14 Apr 2000 16:17:08 -0700 (PDT)
Message-ID: <010a01bfa667$602cbc10$7164a8c0@ruchirnt>
From: "Ruchir" <ruchir@broadpac.com>
To: <ipsec@lists.tislabs.com>, <l2tp@ipsec.org>
Subject: IPsecMIB
Date: Fri, 14 Apr 2000 16:15:51 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0105_01BFA62C.B396F590"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@sailpix.com
Precedence: bulk

This is a multi-part message in MIME format.

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

Hi
    The IPsecMIB module is defined in the draft =
draft-ietf-ipsec-flow-monitoring-mib-00.txt

-------------------------------------------------------------------------=
-----------------
IPsecMIB MODULE-IDENTITY
       LAST-UPDATED "9911040000Z"
       ORGANIZATION "Tivoli Systems and Cisco Systems"
       CONTACT-INFO
          "Tivoli Systems
           Research Triangle Park, NC

           Cisco Systems
           San Jose, CA"
       DESCRIPTION
          "This is the MIB Module for objects to
           manage the IP Security Protocol."
       ::=3D { enterprises ibm(2) ibmProd(6) tivoliNma(168)
                                           IPsecMgmt(1)
                                           IPsecMgmtT1(1) 1 }

-------------------------------------------------------------------------=
-----------

Why is this MIB under the "enterprises" node ? Its not a proprietary =
MIB, right ? where i.e. under which node, is IETF planning to put it ?

Ruchir Malhotra

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; The IPsecMIB module =
is defined=20
in the draft draft-ietf-ipsec-flow-monitoring-mib-00.txt</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
--------------------------</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>IPsecMIB=20
MODULE-IDENTITY<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LAST-UPDATED=20
"9911040000Z"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ORGANIZATION =
"Tivoli=20
Systems and Cisco Systems"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
CONTACT-INFO<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"Tivoli=20
Systems<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Research=20
Triangle Park, NC</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Cisco=20
Systems<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
San=20
Jose, CA"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
DESCRIPTION<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"This is=20
the MIB Module for objects=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
manage the IP=20
Security Protocol."<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { =
enterprises=20
ibm(2) ibmProd(6)=20
tivoliNma(168)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
IPsecMgmt(1)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
IPsecMgmtT1(1) 1 }</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
--------------------</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Why is this&nbsp;MIB under the =
"enterprises" node ?=20
Its not a proprietary MIB, right ? where i.e. under which node, is IETF =
planning=20
to put it ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ruchir =
Malhotra</FONT></DIV></BODY></HTML>

------=_NextPart_000_0105_01BFA62C.B396F590--



From owner-l2tp@ipsec.org  Fri Apr 14 20:46:06 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16320
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 20:46:05 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id QAA13232; Fri, 14 Apr 2000 16:37:11 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id QAA13227 for <l2tp@ipsec.org>; Fri, 14 Apr 2000 16:36:35 -0700 (PDT)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 14 Apr 2000 15:09:58 -0700 (Pacific Daylight Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <2YH3B2RG>; Fri, 14 Apr 2000 15:09:58 -0700
Message-ID: <6A05D00595BE644E9F435BE5947423F2FFC35B@fifi.platinum.corp.microsoft.com>
From: William Dixon <wdixon@Exchange.Microsoft.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>, Evan Caves <evan@acc.com>
Cc: srikrish@rapid5.com, l2tp@ipsec.org
Subject: RE: How to Reorder/Detect packet loss  in case of Payload L2TP pa
	ckets?
Date: Fri, 14 Apr 2000 15:13:09 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Don't forget that IPSec mandates sequence numbers as well for both AH & ESP
and anti-replay protection on the receiving SA, which uses either a 32 or 64
packet window (sufficient to detect packet loss, since receiver must discard
outside of this window).  So if you want one general mechanism for both
IPSec tunnels & L2TP/IPSec tunnels to detect packets loss, I'd put it in
IPSec and have L2TP report it.  I realize this doesn't apply to L2TP clear
packets, but I'd hate to see interop requirements develop to include L2TP
sequence numbers just to detect packet loss.

-----Original Message-----
From: W. Mark Townsley [mailto:townsley@cisco.com]
Sent: Thursday, April 13, 2000 4:58 PM
To: Evan Caves
Cc: srikrish@rapid5.com; l2tp@ipsec.org
Subject: Re: How to Reorder/Detect packet loss in case of Payload L2TP
packets?




Evan Caves wrote:
> 
> Srikrishnan wrote:
> 
> > "W. Mark Townsley" wrote:
> >
> > > Srikrishnan wrote:
> > > >
> > > > Hi,
> > > >
> > > >    L2TP RFC 2661 section 5.4 (give below)
> > > > "Unlike the L2TP control channel, the L2TP data channel does not use
> > > >    sequence numbers to retransmit lost data messages. Rather, data
> > > >    messages may use sequence numbers to detect lost packets and/or
> > > >    restore the original sequence of packets that may have been
reordered
> > > >
> > > >    during transport.  The LAC may request that sequence numbers be"
> > > >
> > > >    proposes that Sequence Numbers in Payload can be used for
> > > >    reordering of data packets and/or detect packets lost.
> > > >
> > > >    But how can a packet be detected if we cant resynchronize the
> > > >    Sequence number after the first packet loss.
> > > >
> > > >     For ex:  If sequence 1,2,3 sent by LAC to LNS and 2 is lost. By
> > > >     what mechanism   will LNS detect the packet loss?
> > >
> > > If 2 is lost, the LNS would not see it. The LNS would only see 1 and
3.
> > >
> >
> > My Point is exactly that, at the time of getting 3, how could LNS
conclude
> > whether the packet 2 is lost or delayed in the network?
> > As its not serial link, there is lot of chances that the packet 2 may be
> > delayed.
> >
> > If you see the section mentioned about, it says LNS can reorder the
packet
> > or detect packet loss. I could'nt see any way to do that. ( may be some
> > timer!!)
> 
> Yes you would need to use some kind of timer mechanism and possibly force
> flush based on queue depth.

Yes. But don't wait around too long as you don't want to cause the
higher layer (e.g. TCP) RTT calculations to get skewed heavily. If you
must reorder, I would recommend a very short queue with depth flush as
Evan mentioned, and perhaps a short timer as well if you can afford it
(this all depends on your scalability requirements). 

For L2 tunneled IP data packets (without stateful compression or
encryption of course), I have seen little reason in practice not to go
ahead and pass data as it is received - in order or not.

> 
> evan
> -
> 
> >
> >
> > Your response will be appreicated.
> >
> > Thanks in Advance,
> > Srikrishnan.


From owner-l2tp@ipsec.org  Fri Apr 14 22:51:04 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18988
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Apr 2000 22:51:04 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id SAA13408; Fri, 14 Apr 2000 18:47:15 -0700 (PDT)
Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id SAA13404 for <l2tp@sailpix.com>; Fri, 14 Apr 2000 18:47:02 -0700 (PDT)
From: Barney Wolff <barney@databus.com>
To: l2tp@sailpix.com
Date: Fri, 14 Apr 2000 21:41 EDT
Subject: RE: How to Reorder/Detect packet loss  in case of Payload L2TP pa ckets?
Content-Type: text/plain
Message-ID: <38f7ca130.351d@databus.databus.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

But the requirement is already there, that either side can insist on
sequence numbers in the data channel.  How is interoperability aided
by allowing some systems to evade requirements that other systems
count on?  I don't consider myself a layering purist, but imho
introducing an l2tp-lite that works only over ipsec would be a mistake.

Barney Wolff

> From: William Dixon <wdixon@Exchange.Microsoft.com>
> Date: Fri, 14 Apr 2000 15:13:09 -0700
> 
> Don't forget that IPSec mandates sequence numbers as well for both AH & ESP
> and anti-replay protection on the receiving SA, which uses either a 32 or 64
> packet window (sufficient to detect packet loss, since receiver must discard
> outside of this window).  So if you want one general mechanism for both
> IPSec tunnels & L2TP/IPSec tunnels to detect packets loss, I'd put it in
> IPSec and have L2TP report it.  I realize this doesn't apply to L2TP clear
> packets, but I'd hate to see interop requirements develop to include L2TP
> sequence numbers just to detect packet loss.


From owner-l2tp@ipsec.org  Sat Apr 15 00:34:58 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20044
	for <l2tpext-archive@odin.ietf.org>; Sat, 15 Apr 2000 00:34:57 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id UAA13691; Fri, 14 Apr 2000 20:49:03 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id UAA13687 for <l2tp@sailpix.com>; Fri, 14 Apr 2000 20:48:42 -0700 (PDT)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 14 Apr 2000 20:43:18 -0700 (Pacific Daylight Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <2YH3BPTB>; Fri, 14 Apr 2000 20:43:18 -0700
Message-ID: <6A05D00595BE644E9F435BE5947423F2FFC363@fifi.platinum.corp.microsoft.com>
From: William Dixon <wdixon@Exchange.Microsoft.com>
To: "'Barney Wolff'" <barney@databus.com>, l2tp@sailpix.com
Subject: RE: How to Reorder/Detect packet loss  in case of Payload L2TP pa
	 ckets?
Date: Fri, 14 Apr 2000 20:46:19 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Barney, I mistakenly thought we could agree on a convention, after rereading
the spec..., I now see that if requested they must be present, so for
interop I must support sequence numbers.  The other reason I had for packet
loss calculated in the IPSec module was to still get packet loss
measurements when implementing header compression.

From the L2TPHC draft:
The S bit MUST be set to 0, indicating no Nr/Ns fields.  Control
   packets are not passed via L2TPHC.  If sequencing of data packets is
   required, L2TPHC MUST NOT be used for those data packets.  

Clearly in this case, if you negotiated L2TPHC, then there are no L2TP
sequence numbers, yet packet loss figures could still be tracked for the
L2TP/IPSec sessions.

-----Original Message-----
From: Barney Wolff [mailto:barney@databus.com]
Sent: Friday, April 14, 2000 6:41 PM
To: l2tp@sailpix.com
Subject: RE: How to Reorder/Detect packet loss in case of Payload L2TP
pa ckets?


But the requirement is already there, that either side can insist on
sequence numbers in the data channel.  How is interoperability aided
by allowing some systems to evade requirements that other systems
count on?  I don't consider myself a layering purist, but imho
introducing an l2tp-lite that works only over ipsec would be a mistake.

Barney Wolff

> From: William Dixon <wdixon@Exchange.Microsoft.com>
> Date: Fri, 14 Apr 2000 15:13:09 -0700
> 
> Don't forget that IPSec mandates sequence numbers as well for both AH &
ESP
> and anti-replay protection on the receiving SA, which uses either a 32 or
64
> packet window (sufficient to detect packet loss, since receiver must
discard
> outside of this window).  So if you want one general mechanism for both
> IPSec tunnels & L2TP/IPSec tunnels to detect packets loss, I'd put it in
> IPSec and have L2TP report it.  I realize this doesn't apply to L2TP clear
> packets, but I'd hate to see interop requirements develop to include L2TP
> sequence numbers just to detect packet loss.


From owner-l2tp@ipsec.org  Sun Apr 16 17:50:48 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10650
	for <l2tpext-archive@odin.ietf.org>; Sun, 16 Apr 2000 17:50:48 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA18332; Sun, 16 Apr 2000 13:51:16 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA18328 for <l2tp@ipsec.org>; Sun, 16 Apr 2000 13:51:00 -0700 (PDT)
From: kyork@cisco.com
Received: from deep-freeze.cisco.com (deep-freeze.cisco.com [171.71.68.21])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id NAA08157;
	Sun, 16 Apr 2000 13:50:32 -0700 (PDT)
Received: from cisco.com ([10.19.200.101]) by deep-freeze.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id NAA27174; Sun, 16 Apr 2000 13:50:29 -0700 (PDT)
Message-ID: <38FA26E4.5918AC80@cisco.com>
Date: Sun, 16 Apr 2000 13:47:32 -0700
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>
CC: "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,

HOULLIER Francis FTRD/DMI/CAE wrote:
> 
> What is the condition to send a ZLB Ack (see the example below), is this a
> timer or something else ? The rfc says only that "the ZLB Ack is sent if
> there are no futher messages waiting in the queue".
> 
> LAC                                             LNS
> 
> SCCRQ ---->
>                                         <----SCCRP
> SCCCN ---->
>                                         <----ZLB ACK
> 
> But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> the ZLB ACK.
> Thank you for your help.

For what it's worth, my implementation would generally send a ZLB after
the SCCRQ as there was an authentication delay. More generally, anytime
the input path was complete, if no other messages have been queued for
output, send a ZLB.

-- 
Kyle A. York
Subordinate Grunt
CLOB


From owner-l2tp@ipsec.org  Mon Apr 17 10:12:49 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03173
	for <l2tpext-archive@odin.ietf.org>; Mon, 17 Apr 2000 10:12:48 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id FAA20569; Mon, 17 Apr 2000 05:55:37 -0700 (PDT)
Received: from cat01s2.catenanet.com (CAT01FW.Catenanet.com [209.135.116.34]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA20565 for <l2tp@ipsec.org>; Mon, 17 Apr 2000 05:54:17 -0700 (PDT)
Received: by CAT01S2 with Internet Mail Service (5.5.2448.0)
	id <2NJZ84J6>; Mon, 17 Apr 2000 08:54:21 -0400
Message-ID: <310508EDF557D31188FA0050DA0A37522CC14E@CAT01S2>
From: Tim Jenkins <TJenkins@CatenaNet.com>
To: "'Ruchir'" <ruchir@broadpac.com>, ipsec@lists.tislabs.com, l2tp@ipsec.org
Subject: RE: IPsecMIB
Date: Mon, 17 Apr 2000 08:54:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFA86C.0CB107E0"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

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

------_=_NextPart_001_01BFA86C.0CB107E0
Content-Type: text/plain;
	charset="iso-8859-1"

The MIB asked about is not the version that is currently being advanced
under standards track. Technically, it's an application specific MIB that
includes everything else. The standards track MIBs for IPsec are the
following:
 
Textual Conventions: <
http://search.ietf.org/internet-drafts/draft-ietf-ipsec-doi-tc-mib-02.txt
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-doi-tc-mib-02.txt>
>
IPsec Monitoring: <
http://search.ietf.org/internet-drafts/draft-ietf-ipsec-monitor-mib-02.txt
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-monitor-mib-02.txt>
>
ISAKMP DOI-ind. Monitoring: <
http://search.ietf.org/internet-drafts/draft-ietf-ipsec-isakmp-di-mon-mib-01
.txt
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-isakmp-di-mon-mib-0
1.txt> >
IKE Monitoring: <
http://search.ietf.org/internet-drafts/draft-ietf-ipsec-ike-monitor-mib-00.t
xt
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-ike-monitor-mib-00.
txt> >
 
New versions of all should be available within a couple of months at the
latest (hopefully).
 
The authors of the MIB referred to below were asked if they were interested
in modifying it to use the base MIBs listed above; I don't recall there
being any response to that.

-----Original Message-----
From: Ruchir [mailto:ruchir@broadpac.com]
Sent: Friday, April 14, 2000 7:16 PM
To: ipsec@lists.tislabs.com; l2tp@ipsec.org
Subject: IPsecMIB


Hi
    The IPsecMIB module is defined in the draft
draft-ietf-ipsec-flow-monitoring-mib-00.txt
 
----------------------------------------------------------------------------
--------------
IPsecMIB MODULE-IDENTITY
       LAST-UPDATED "9911040000Z"
       ORGANIZATION "Tivoli Systems and Cisco Systems"
       CONTACT-INFO
          "Tivoli Systems
           Research Triangle Park, NC
 
           Cisco Systems
           San Jose, CA"
       DESCRIPTION
          "This is the MIB Module for objects to
           manage the IP Security Protocol."
       ::= { enterprises ibm(2) ibmProd(6) tivoliNma(168)
                                           IPsecMgmt(1)
                                           IPsecMgmtT1(1) 1 }
 
----------------------------------------------------------------------------
--------
 
Why is this MIB under the "enterprises" node ? Its not a proprietary MIB,
right ? where i.e. under which node, is IETF planning to put it ?
 
Ruchir Malhotra


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D670264812-17042000>The=20
MIB asked about is not the version that is currently being advanced =
under=20
standards track. Technically, it's an application specific MIB that =
includes=20
everything else. The standards track MIBs for IPsec are the=20
following:</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D670264812-17042000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff><SPAN class=3D670264812-17042000>
<DIV><FONT color=3D#0000ff><SPAN class=3D572244220-13042000><SPAN=20
class=3D670264812-17042000></SPAN><FONT face=3DArial size=3D2>T<SPAN=20
class=3D670264812-17042000>extual Conventions: </SPAN>&lt;<A=20
href=3D"http://search.ietf.org/internet-drafts/draft-ietf-ipsec-doi-tc-m=
ib-02.txt">http://search.ietf.org/internet-drafts/draft-ietf-ipsec-doi-t=
c-mib-02.txt</A>&gt;</FONT></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff><SPAN class=3D572244220-13042000><SPAN=20
class=3D670264812-17042000></SPAN><FONT face=3DArial size=3D2>I<SPAN=20
class=3D670264812-17042000>Psec Monito</SPAN><SPAN =
class=3D670264812-17042000>ring:=20
</SPAN>&lt;<A=20
href=3D"http://search.ietf.org/internet-drafts/draft-ietf-ipsec-monitor-=
mib-02.txt">http://search.ietf.org/internet-drafts/draft-ietf-ipsec-moni=
tor-mib-02.txt</A>&gt;</FONT></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff><SPAN class=3D572244220-13042000><SPAN=20
class=3D670264812-17042000></SPAN><FONT face=3DArial size=3D2>I<SPAN=20
class=3D670264812-17042000>SAK</SPAN><SPAN =
class=3D670264812-17042000>MP=20
DOI</SPAN><SPAN class=3D670264812-17042000>-ind. Monitoring: =
</SPAN>&lt;<A=20
href=3D"http://search.ietf.org/internet-drafts/draft-ietf-ipsec-isakmp-d=
i-mon-mib-01.txt">http://search.ietf.org/internet-drafts/draft-ietf-ipse=
c-isakmp-di-mon-mib-01.txt</A>&gt;</FONT></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff><SPAN class=3D572244220-13042000><SPAN=20
class=3D670264812-17042000></SPAN><FONT face=3DArial size=3D2>I<SPAN=20
class=3D670264812-17042000>KE Monitoring</SPAN><SPAN =
class=3D670264812-17042000>:=20
</SPAN>&lt;<A=20
href=3D"http://search.ietf.org/internet-drafts/draft-ietf-ipsec-ike-moni=
tor-mib-00.txt">http://search.ietf.org/internet-drafts/draft-ietf-ipsec-=
ike-monitor-mib-00.txt</A>&gt;</FONT></SPAN></FONT></DIV>
<DIV><SPAN class=3D572244220-13042000></SPAN><FONT face=3DArial=20
size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D572244220-13042000>New =
versions of all=20
should be available within a couple of months at the latest=20
(hopefully).</SPAN></FONT></DIV>
<DIV><SPAN class=3D572244220-13042000></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D572244220-13042000><SPAN =

class=3D670264812-17042000>The authors of the MIB referred to below =
were asked if=20
they were interested in modifying it to use the base MIBs listed above; =
I don't=20
recall there being any response to=20
that.</SPAN></SPAN></FONT></DIV></SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Ruchir=20
  [mailto:ruchir@broadpac.com]<BR><B>Sent:</B> Friday, April 14, 2000 =
7:16=20
  PM<BR><B>To:</B> ipsec@lists.tislabs.com; =
l2tp@ipsec.org<BR><B>Subject:</B>=20
  IPsecMIB<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; The IPsecMIB =
module is defined=20
  in the draft draft-ietf-ipsec-flow-monitoring-mib-00.txt</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>---------------------------------------------------------------=
---------------------------</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>IPsecMIB=20
  MODULE-IDENTITY<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LAST-UPDATED=20
  "9911040000Z"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ORGANIZATION =
"Tivoli=20
  Systems and Cisco Systems"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
CONTACT-INFO<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"Tivoli=20
  =
Systems<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  Research Triangle Park, NC</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Cisco=20
  =
Systems<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
San=20
  Jose, CA"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  DESCRIPTION<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"This is=20
  the MIB Module for objects=20
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
manage the=20
  IP Security Protocol."<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D =
{=20
  enterprises ibm(2) ibmProd(6)=20
  =
tivoliNma(168)<BR>&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;=20
  =
IPsecMgmt(1)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  IPsecMgmtT1(1) 1 }</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>---------------------------------------------------------------=
---------------------</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Why is this&nbsp;MIB under the =
"enterprises" node=20
  ? Its not a proprietary MIB, right ? where i.e. under which node, is =
IETF=20
  planning to put it ?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Ruchir=20
Malhotra</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFA86C.0CB107E0--


From owner-l2tp@ipsec.org  Mon Apr 17 17:01:03 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09788
	for <l2tpext-archive@odin.ietf.org>; Mon, 17 Apr 2000 17:01:02 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id NAA21188; Mon, 17 Apr 2000 13:01:54 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA21184 for <l2tp@ipsec.org>; Mon, 17 Apr 2000 13:01:36 -0700 (PDT)
Received: from miranda-ultra.cisco.com (miranda-ultra.cisco.com [171.69.85.104])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id NAA12870;
	Mon, 17 Apr 2000 13:00:01 -0700 (PDT)
Received: from vnatupc (rks-pc.cisco.com [171.69.85.105]) by miranda-ultra.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with SMTP id MAA29096; Mon, 17 Apr 2000 12:59:59 -0700 (PDT)
Message-ID: <004201bfa8a7$80cb5fc0$695545ab@cisco.com>
From: "S Ramakrishnan" <rks@cisco.com>
To: <l2tp@ipsec.org>, <ipsec@lists.tislabs.com>,
        "Tim Jenkins" <TJenkins@CatenaNet.com>,
        "Leo Temoshenko" <leot@tivoli.com>
References: <310508EDF557D31188FA0050DA0A37522CC14E@CAT01S2>
Subject: Re: IPsecMIB
Date: Mon, 17 Apr 2000 12:59:55 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

     From: Tim Jenkins
     Sent: Monday, April 17, 2000 5:54 AM

    >Textual Conventions:
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-doi-tc-mib-02.txt>
   >IPsec Monitoring:
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-monitor-mib-02.txt>
   >ISAKMP DOI-ind. Monitoring:
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-isakmp-di-mon-mib-0
1.txt>
   >IKE Monitoring:
<http://search.ietf.org/internet-drafts/draft-ietf-ipsec-ike-monitor-mib-00.
txt>

   >The authors of the MIB referred to below were asked if they
   >were interested in modifying it to use the base MIBs listed above;
   >I don't recall there being any response to that.

I do not recall a discussion to this effect in this list.
Perhaps I missed it. What specific changes would
you suggest?

We have included the TCs proposed in
draft-ietf-ipsec-doi-tc-mib-02.txt.

Thanks,

Rk







From owner-l2tp@ipsec.org  Tue Apr 18 01:27:49 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19658
	for <l2tpext-archive@odin.ietf.org>; Tue, 18 Apr 2000 01:27:48 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id VAA21876; Mon, 17 Apr 2000 21:25:06 -0700 (PDT)
Received: from noya.bupt.edu.cn (noya.bupt.edu.cn [202.112.96.2]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id VAA21872 for <l2tp@ipsec.org>; Mon, 17 Apr 2000 21:24:36 -0700 (PDT)
Received: from chj ([202.112.111.45])
	by noya.bupt.edu.cn (8.9.3/8.9.3) with SMTP id MAA25855
	for <l2tp@ipsec.org>; Tue, 18 Apr 2000 12:10:36 +0800 (CST)
Message-Id: <200004180410.MAA25855@noya.bupt.edu.cn>
Date: Tue, 18 Apr 2000 12:10:41 +0800
From: chj <hjchai@263.net>
Reply-To: hjchai@263.net
To: L2TP discussion group <l2tp@ipsec.org>
Subject: about the framing capacity AVP.
Organization: ATM R&D CENTER
X-mailer: FoxMail 2.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi,all,

	how does L2tp discriminate between synchronous HDLC framing and Octet-synchronous 
HDLC framing? It seems that this AVP can only tell between sync and async HDLC framings.

reguards,

hjchai

   



From owner-l2tp@ipsec.org  Wed Apr 19 08:02:16 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04333
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 08:02:14 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id DAA27255; Wed, 19 Apr 2000 03:44:47 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA27251 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 03:44:12 -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 GAA02844;
	Wed, 19 Apr 2000 06:44:00 -0400 (EDT)
Message-Id: <200004191044.GAA02844@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: l2tp@ipsec.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l2tpext-l2tphc-01.txt
Date: Wed, 19 Apr 2000 06:44:00 -0400
Sender: owner-l2tp@ipsec.org
Precedence: bulk

--NextPart

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

	Title		: L2TP Header Compression ('L2TPHC')
	Author(s)	: A. Valencia
	Filename	: draft-ietf-l2tpext-l2tphc-01.txt
	Pages		: 7
	Date		: 18-Apr-00
	
The Layer 2 Tunneling Protocol ('L2TP') [RFC2661] defines a mecha-
nism for tunneling PPP sessions over arbitrary media.  There exists a
class of specific media and applications for which protocol overhead
may be optimized, and where such reduction results in improved opera-
tion.  This document describes the solution space addressed, its
underlying motivations, and the protocol modifications required.  The
enhancement to the L2TP protocol is called L2TP Header Compression,
or 'L2TPHC'.

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Wed Apr 19 14:16:06 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11124
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:16:05 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id KAA27938; Wed, 19 Apr 2000 10:05:18 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA27925 for <l2tp@sailpix.com>; Wed, 19 Apr 2000 10:04:30 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA19101; Wed, 19 Apr 2000 10:03:46 -0700 (PDT)
Message-ID: <38FDDC4C.601EE2FC@cisco.com>
Date: Wed, 19 Apr 2000 12:18:20 -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: William Dixon <wdixon@Exchange.Microsoft.com>
CC: "'Barney Wolff'" <barney@databus.com>, l2tp@sailpix.com
Subject: Re: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
References: <6A05D00595BE644E9F435BE5947423F2FFC363@fifi.platinum.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


We could certainly *suggest* leaving sequence numbers off on the l2tp
data channel with ipsec, citing the reasons you have stated. This of
course would not be license to leave out support.

William Dixon wrote:
> 
> Barney, I mistakenly thought we could agree on a convention, after rereading
> the spec..., I now see that if requested they must be present, so for
> interop I must support sequence numbers.  The other reason I had for packet
> loss calculated in the IPSec module was to still get packet loss
> measurements when implementing header compression.
> 
> >From the L2TPHC draft:
> The S bit MUST be set to 0, indicating no Nr/Ns fields.  Control
>    packets are not passed via L2TPHC.  If sequencing of data packets is
>    required, L2TPHC MUST NOT be used for those data packets.
> 
> Clearly in this case, if you negotiated L2TPHC, then there are no L2TP
> sequence numbers, yet packet loss figures could still be tracked for the
> L2TP/IPSec sessions.
> 
> -----Original Message-----
> From: Barney Wolff [mailto:barney@databus.com]
> Sent: Friday, April 14, 2000 6:41 PM
> To: l2tp@sailpix.com
> Subject: RE: How to Reorder/Detect packet loss in case of Payload L2TP
> pa ckets?
> 
> But the requirement is already there, that either side can insist on
> sequence numbers in the data channel.  How is interoperability aided
> by allowing some systems to evade requirements that other systems
> count on?  I don't consider myself a layering purist, but imho
> introducing an l2tp-lite that works only over ipsec would be a mistake.
> 
> Barney Wolff
> 
> > From: William Dixon <wdixon@Exchange.Microsoft.com>
> > Date: Fri, 14 Apr 2000 15:13:09 -0700
> >
> > Don't forget that IPSec mandates sequence numbers as well for both AH &
> ESP
> > and anti-replay protection on the receiving SA, which uses either a 32 or
> 64
> > packet window (sufficient to detect packet loss, since receiver must
> discard
> > outside of this window).  So if you want one general mechanism for both
> > IPSec tunnels & L2TP/IPSec tunnels to detect packets loss, I'd put it in
> > IPSec and have L2TP report it.  I realize this doesn't apply to L2TP clear
> > packets, but I'd hate to see interop requirements develop to include L2TP
> > sequence numbers just to detect packet loss.




From owner-l2tp@ipsec.org  Wed Apr 19 14:18:00 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11193
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:18:00 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id JAA27842; Wed, 19 Apr 2000 09:41:28 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA27838 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 09:41:11 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id JAA17389; Wed, 19 Apr 2000 09:40:35 -0700 (PDT)
Message-ID: <38FDDC42.568CBE90@cisco.com>
Date: Wed, 19 Apr 2000 12:18:10 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.
> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.
> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB




From owner-l2tp@ipsec.org  Wed Apr 19 14:18:19 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11206
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:18:19 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id KAA27929; Wed, 19 Apr 2000 10:04:42 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA27920 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:04:04 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA19094; Wed, 19 Apr 2000 10:03:30 -0700 (PDT)
Message-ID: <38FDDC46.A41AB57F@cisco.com>
Date: Wed, 19 Apr 2000 12:18:14 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.

This certainly does not prohibit the LNS from sending a ZLB ack, as I
think has already been answered.

> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.

Also FWIW, the cisco IOS implementation will always send a ZLB ACK after
receipt of an SCCCN, and never after receipt of an SCCRQ.

- Mark

> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB




From owner-l2tp@ipsec.org  Wed Apr 19 14:34:53 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11524
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:34:52 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA27924; Wed, 19 Apr 2000 10:04:15 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA27915 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:03:51 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA19090; Wed, 19 Apr 2000 10:03:16 -0700 (PDT)
Message-ID: <38FDDC42.568CBE90@cisco.com>
Date: Wed, 19 Apr 2000 12:18:10 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.
> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.
> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB




From owner-l2tp@ipsec.org  Wed Apr 19 14:48:48 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11709
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:48:47 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28110; Wed, 19 Apr 2000 10:52:26 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28096 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:51:23 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24716; Wed, 19 Apr 2000 10:50:37 -0700 (PDT)
Message-ID: <38FDF1EA.396EFD51@cisco.com>
Date: Wed, 19 Apr 2000 13:50: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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.

This certainly does not prohibit the LNS from sending a ZLB ack, as I
think has already been answered.

> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.

Also FWIW, the cisco IOS implementation will always send a ZLB ACK after
receipt of an SCCCN, and never after receipt of an SCCRQ.

- Mark

> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB


From owner-l2tp@ipsec.org  Wed Apr 19 14:50:41 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11737
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:50:40 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28028; Wed, 19 Apr 2000 10:41:19 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28020 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:40:50 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24586; Wed, 19 Apr 2000 10:40:17 -0700 (PDT)
Message-ID: <38FDDC42.568CBE90@cisco.com>
Date: Wed, 19 Apr 2000 12:18:10 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.
> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.
> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB




From owner-l2tp@ipsec.org  Wed Apr 19 14:59:48 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11838
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 14:59:48 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28122; Wed, 19 Apr 2000 10:52:48 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28100 for <l2tp@sailpix.com>; Wed, 19 Apr 2000 10:51:30 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24722; Wed, 19 Apr 2000 10:50:55 -0700 (PDT)
Message-ID: <38FDF1FF.2547AAA8@cisco.com>
Date: Wed, 19 Apr 2000 13:50:55 -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: William Dixon <wdixon@Exchange.Microsoft.com>
CC: "'Barney Wolff'" <barney@databus.com>, l2tp@sailpix.com
Subject: Re: How to Reorder/Detect packet loss  in case of Payload L2TP packets?
References: <6A05D00595BE644E9F435BE5947423F2FFC363@fifi.platinum.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


We could certainly *suggest* leaving sequence numbers off on the l2tp
data channel with ipsec, citing the reasons you have stated. This of
course would not be license to leave out support.

William Dixon wrote:
> 
> Barney, I mistakenly thought we could agree on a convention, after rereading
> the spec..., I now see that if requested they must be present, so for
> interop I must support sequence numbers.  The other reason I had for packet
> loss calculated in the IPSec module was to still get packet loss
> measurements when implementing header compression.
> 
> >From the L2TPHC draft:
> The S bit MUST be set to 0, indicating no Nr/Ns fields.  Control
>    packets are not passed via L2TPHC.  If sequencing of data packets is
>    required, L2TPHC MUST NOT be used for those data packets.
> 
> Clearly in this case, if you negotiated L2TPHC, then there are no L2TP
> sequence numbers, yet packet loss figures could still be tracked for the
> L2TP/IPSec sessions.
> 
> -----Original Message-----
> From: Barney Wolff [mailto:barney@databus.com]
> Sent: Friday, April 14, 2000 6:41 PM
> To: l2tp@sailpix.com
> Subject: RE: How to Reorder/Detect packet loss in case of Payload L2TP
> pa ckets?
> 
> But the requirement is already there, that either side can insist on
> sequence numbers in the data channel.  How is interoperability aided
> by allowing some systems to evade requirements that other systems
> count on?  I don't consider myself a layering purist, but imho
> introducing an l2tp-lite that works only over ipsec would be a mistake.
> 
> Barney Wolff
> 
> > From: William Dixon <wdixon@Exchange.Microsoft.com>
> > Date: Fri, 14 Apr 2000 15:13:09 -0700
> >
> > Don't forget that IPSec mandates sequence numbers as well for both AH &
> ESP
> > and anti-replay protection on the receiving SA, which uses either a 32 or
> 64
> > packet window (sufficient to detect packet loss, since receiver must
> discard
> > outside of this window).  So if you want one general mechanism for both
> > IPSec tunnels & L2TP/IPSec tunnels to detect packets loss, I'd put it in
> > IPSec and have L2TP report it.  I realize this doesn't apply to L2TP clear
> > packets, but I'd hate to see interop requirements develop to include L2TP
> > sequence numbers just to detect packet loss.


From owner-l2tp@ipsec.org  Wed Apr 19 15:04:35 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11964
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:04:34 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28132; Wed, 19 Apr 2000 10:55:49 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28128 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:55:37 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24820 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:55:05 -0700 (PDT)
Message-ID: <38FDF2F9.919365FA@cisco.com>
Date: Wed, 19 Apr 2000 13:55: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: l2tp@ipsec.org
Subject: For the record
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The bug was in Netscape Communicator 4.7

Sorry for the spam

- Mark


From owner-l2tp@ipsec.org  Wed Apr 19 15:06:55 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12010
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:06:55 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28104; Wed, 19 Apr 2000 10:52:04 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28092 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:51:20 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24719; Wed, 19 Apr 2000 10:50:47 -0700 (PDT)
Message-ID: <38FDF1F6.1E7D4748@cisco.com>
Date: Wed, 19 Apr 2000 13:50:46 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.
> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.
> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB


From owner-l2tp@ipsec.org  Wed Apr 19 15:11:01 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12096
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:11:00 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28076; Wed, 19 Apr 2000 10:48:22 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28066 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:47:57 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24608; Wed, 19 Apr 2000 10:47:24 -0700 (PDT)
Message-ID: <38FDDC42.568CBE90@cisco.com>
Date: Wed, 19 Apr 2000 12:18:10 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.
> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.
> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB




From owner-l2tp@ipsec.org  Wed Apr 19 15:11:10 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12111
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:11:09 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA28029; Wed, 19 Apr 2000 10:41:26 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28024 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 10:40:58 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA24589; Wed, 19 Apr 2000 10:40:24 -0700 (PDT)
Message-ID: <38FDDC42.568CBE90@cisco.com>
Date: Wed, 19 Apr 2000 12:18:10 -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: kyork@cisco.com
CC: HOULLIER Francis FTRD/DMI/CAE <francis.houllier@rd.francetelecom.fr>,
        "'Mailing liste L2TP'" <l2tp@ipsec.org>
Subject: Re: ZLB Ack.
References: <91A311FF6A85D3118DDF0060080C3D820E3102@lat3721.lannion.cnet.fr> <38FA26E4.5918AC80@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



kyork@cisco.com wrote:
> 
> Greetings,
> 
> HOULLIER Francis FTRD/DMI/CAE wrote:
> >
> > What is the condition to send a ZLB Ack (see the example below), is this a
> > timer or something else ? The rfc says only that "the ZLB Ack is sent if
> > there are no futher messages waiting in the queue".
> >
> > LAC                                             LNS
> >
> > SCCRQ ---->
> >                                         <----SCCRP
> > SCCCN ---->
> >                                         <----ZLB ACK
> >
> > But generally after the SCCCN, the LAC sends an ICRQ and the LNS can't send
> > the ZLB ACK.
> > Thank you for your help.
> 
> For what it's worth, my implementation would generally send a ZLB after
> the SCCRQ as there was an authentication delay. More generally, anytime
> the input path was complete, if no other messages have been queued for
> output, send a ZLB.
> 
> --
> Kyle A. York
> Subordinate Grunt
> CLOB




From owner-l2tp@ipsec.org  Wed Apr 19 15:35:14 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12619
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:35:13 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id LAA28275; Wed, 19 Apr 2000 11:27:26 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA28271 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 11:27:00 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id LAA27904; Wed, 19 Apr 2000 11:26:28 -0700 (PDT)
Message-ID: <38FDFA53.CBBB4221@cisco.com>
Date: Wed, 19 Apr 2000 14:26:27 -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: Craig Fox <fox@cisco.com>
CC: l2tp@ipsec.org
Subject: Re: For the record
References: <38FDF2F9.919365FA@cisco.com> <38FDF529.89304A2E@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Craig Fox wrote:
> 
> "W. Mark Townsley" wrote:
> >
> > The bug was in Netscape Communicator 4.7
> 
> What was the bug?  I have used 4.7 for six months now.

OK, several people have asked, so here it is.

Netscape Messenger got into some state where it thought my disk was full
(I actually had over 2 GB free) when writing to the Sent Mail folder.
When trying to write it would fail, with an error message stating that
my disk was full, my mail was NOT sent, and that the Send operation
would need to be retried after the problem was corrected. Further, the
mail remained in my Unsent Mail folder. Given that there was some
catastrophic file system failure, I suppose I can understand not moving
my messages out of the Unsent folder, but the error message was clearly
inaccurate. 

I went through Windows reboots and Netscape restarts in various
combinations. Each time (on netscape exit and startup), I was asked if I
wished to send the messages, each time it failed saying that the
messages were not sent. Finally, I got the right combination of reboots
and restarts, the messages went out the door OK and were copied to the
Sent Mail folder without error.

It was not until after that I realized each time I answered yes to the
retry, a copy of all messages in my Unsent Folder had been sent. I had a
feeling that this might be happening, but put too much faith and trust
in the error message was reported.

Hope you only get one copy of this.

- Mark

> 
> Craig
> 
> >
> > Sorry for the spam
> >
> > - Mark


From owner-l2tp@ipsec.org  Wed Apr 19 15:44:22 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12907
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:44:22 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id LAA28285; Wed, 19 Apr 2000 11:28:37 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA28281 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 11:28:20 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id LAA27913; Wed, 19 Apr 2000 11:27:47 -0700 (PDT)
Message-ID: <38FDFAA3.2A68E8A5@cisco.com>
Date: Wed, 19 Apr 2000 14:27: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: Ignacio Goyret <igoyret@lucent.com>
CC: l2tp@ipsec.org
Subject: Re: RFC 2661 small typo
References: <3.0.5.32.20000419111626.00a71100@scamp.eng.ascend.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Thanks!

Ignacio Goyret wrote:
> 
> Small typo in section 10.3.1, third sentence.
> It reads:
>   "For the StopCCN message, values 0-7 are defined in Section
>    4.4.2; for the StopCCN message, values 0-11 are defined in
>    the same section."
> 
> The second "StopCCN" should have been a "CDN" :-)
> 
> -Ignacio
> 
> >From a Sun Microsystems bug report (#4102680):
>   "Workaround: don't pound on the mouse like a wild monkey."


From owner-l2tp@ipsec.org  Wed Apr 19 15:47:39 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13002
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:47:38 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id LAA28406; Wed, 19 Apr 2000 11:42:04 -0700 (PDT)
Received: from mw.3com.com (intergate.usr.com [149.112.20.3]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA28402 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 11:41:44 -0700 (PDT)
Received: from mwgate02.mw.3com.com by mw.3com.com (8.8.5/3.1.090690-3Com Corporation)
	id NAA21898; Wed, 19 Apr 2000 13:41:40 -0500 (CDT)
Received: by mwgate02.mw.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 862568C6.0066DEB2 ; Wed, 19 Apr 2000 13:43:36 -0500
X-Lotus-FromDomain: 3COM@3COM-MWGATE
From: "Madhvi Verma" <Madhvi_Verma@mw.3com.com>
To: l2tp@ipsec.org
Message-ID: <862568C6.0066DCE2.00@mwgate02.mw.3com.com>
Date: Wed, 19 Apr 2000 13:44:58 -0500
Subject: Tunnel-Medium-Type value for FR and ATM
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk



Hi,
What do you use as the tunnel-medium-type (RADIUS attribute :65) value for the
following media?
FR:
AAL5:

The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following address
values :
       1      IPv4 (IP version 4)
       2      IPv6 (IP version 6)
       3      NSAP
       4      HDLC (8-bit multidrop)
       5      BBN 1822
       6      802 (includes all 802 media plus Ethernet "canonical format")
       7      E.163 (POTS)
       8      E.164 (SMDS, Frame Relay, ATM)
       9      F.69 (Telex)
       10     X.121 (X.25, Frame Relay)
       11     IPX
       12     Appletalk
       13     Decnet IV
       14     Banyan Vines
       15     E.164 with NSAP format subaddress


Does this mean that the value is addressing dependent, and not media dependent !
Inputs appreciated?

Madhvi




From owner-l2tp@ipsec.org  Wed Apr 19 15:49:36 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13114
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 15:49:35 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id LAA28212; Wed, 19 Apr 2000 11:17:09 -0700 (PDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA28203 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 11:16:16 -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 LAA14261
	for <l2tp@ipsec.org>; Wed, 19 Apr 2000 11:09: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; 19 Apr 2000 18:16:12 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 LAA21289;
	Wed, 19 Apr 2000 11:16:09 -0700 (PDT)
Received: from scamp.eng.ascend.com (scamp.eng.ascend.com [172.20.8.27])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id LAA10774;
	Wed, 19 Apr 2000 11:16:10 -0700 (PDT)
Received: from igoyret-pc.eng.ascend.com by scamp.eng.ascend.com (8.8.8+Sun/SMI-SVR4)
	id LAA14876; Wed, 19 Apr 2000 11:16:09 -0700 (PDT)
Message-Id: <3.0.5.32.20000419111626.00a71100@scamp.eng.ascend.com>
X-Sender: igoyret@scamp.eng.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 19 Apr 2000 11:16:26 -0700
To: l2tp@ipsec.org
From: Ignacio Goyret <igoyret@lucent.com>
Subject: RFC 2661 small typo
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Small typo in section 10.3.1, third sentence.
It reads:
  "For the StopCCN message, values 0-7 are defined in Section
   4.4.2; for the StopCCN message, values 0-11 are defined in
   the same section."

The second "StopCCN" should have been a "CDN" :-)

-Ignacio

>From a Sun Microsystems bug report (#4102680):
  "Workaround: don't pound on the mouse like a wild monkey."



From owner-l2tp@ipsec.org  Wed Apr 19 17:19:10 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14595
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Apr 2000 17:19:09 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id MAA28691; Wed, 19 Apr 2000 12:57:54 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id MAA28677 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 12:56:45 -0700 (PDT)
Received: by ans2-pub.dttus.com id OAA02654
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Wed, 19 Apr 2000 14:56:33 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Wed, 19 Apr 2000 14:56:33 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Wed, 19 Apr 2000 14:56:33 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E65645A138@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: Madhvi Verma <Madhvi_Verma@mw.3com.com>, l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM
Date: Wed, 19 Apr 2000 15:54:19 -0400
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFAA39.0363DDBC"
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_01BFAA39.0363DDBC
Content-Type: text/plain;
	charset="iso-8859-1"

The mediuam-type field is a guideline to the Tunnel Initiator what to expect
in the Tunnel Endpoint Address field. 
I do agree with you that it does not clearly capture the medium (For
Example: E.164 is the addressing standard and it does not specify (SMDS, FR
or ATM).

May be we need to add a more specific value to the set of AVPs retrieved
from RADIUS.

Regards

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


-----Original Message-----
From: Madhvi Verma [mailto:Madhvi_Verma@mw.3com.com]
Sent: Wednesday, April 19, 2000 1:45 PM
To: l2tp@ipsec.org
Subject: Tunnel-Medium-Type value for FR and ATM




Hi,
What do you use as the tunnel-medium-type (RADIUS attribute :65) value for
the
following media?
FR:
AAL5:

The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following
address
values :
       1      IPv4 (IP version 4)
       2      IPv6 (IP version 6)
       3      NSAP
       4      HDLC (8-bit multidrop)
       5      BBN 1822
       6      802 (includes all 802 media plus Ethernet "canonical format")
       7      E.163 (POTS)
       8      E.164 (SMDS, Frame Relay, ATM)
       9      F.69 (Telex)
       10     X.121 (X.25, Frame Relay)
       11     IPX
       12     Appletalk
       13     Decnet IV
       14     Banyan Vines
       15     E.164 with NSAP format subaddress


Does this mean that the value is addressing dependent, and not media
dependent !
Inputs appreciated?

Madhvi


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Tunnel-Medium-Type value for FR and ATM</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>The mediuam-type field is a guideline to the Tunnel =
Initiator what to expect in the Tunnel Endpoint Address field. </FONT>
<BR><FONT SIZE=3D2>I do agree with you that it does not clearly capture =
the medium (For Example: E.164 is the addressing standard and it does =
not specify (SMDS, FR or ATM).</FONT></P>

<P><FONT SIZE=3D2>May be we need to add a more specific value to the =
set of AVPs retrieved from RADIUS.</FONT>
</P>

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

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Madhvi Verma [<A =
HREF=3D"mailto:Madhvi_Verma@mw.3com.com">mailto:Madhvi_Verma@mw.3com.com=
</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 19, 2000 1:45 PM</FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: Tunnel-Medium-Type value for FR and =
ATM</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
<BR><FONT SIZE=3D2>What do you use as the tunnel-medium-type (RADIUS =
attribute :65) value for the</FONT>
<BR><FONT SIZE=3D2>following media?</FONT>
<BR><FONT SIZE=3D2>FR:</FONT>
<BR><FONT SIZE=3D2>AAL5:</FONT>
</P>

<P><FONT SIZE=3D2>The draft =
&quot;draft-ietf-radius-tunnel-auth-09.txt&quot; mentions the following =
address</FONT>
<BR><FONT SIZE=3D2>values :</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv4 (IP version 4)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 (IP version 6)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NSAP</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HDLC (8-bit multidrop)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BBN 1822</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 802 (includes all 802 media plus =
Ethernet &quot;canonical format&quot;)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E.163 (POTS)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E.164 (SMDS, Frame Relay, ATM)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F.69 (Telex)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
10&nbsp;&nbsp;&nbsp;&nbsp; X.121 (X.25, Frame Relay)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
11&nbsp;&nbsp;&nbsp;&nbsp; IPX</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
12&nbsp;&nbsp;&nbsp;&nbsp; Appletalk</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
13&nbsp;&nbsp;&nbsp;&nbsp; Decnet IV</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
14&nbsp;&nbsp;&nbsp;&nbsp; Banyan Vines</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
15&nbsp;&nbsp;&nbsp;&nbsp; E.164 with NSAP format subaddress</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Does this mean that the value is addressing =
dependent, and not media dependent !</FONT>
<BR><FONT SIZE=3D2>Inputs appreciated?</FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01BFAA39.0363DDBC--


From owner-l2tp@ipsec.org  Thu Apr 20 00:12:47 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20920
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 00:12:46 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id SAA29233; Wed, 19 Apr 2000 18:32:26 -0700 (PDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA29229 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 18:31:19 -0700 (PDT)
Received: from gwz (sj-dial-1-213.cisco.com [171.68.179.214]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id SAA12496; Wed, 19 Apr 2000 18:30:09 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "Verma, Rohit (US - Chicago)" <rverma@dc.com>,
        "Madhvi Verma" <Madhvi_Verma@mw.3com.com>, <l2tp@ipsec.org>
Subject: RE: Tunnel-Medium-Type value for FR and ATM
Date: Wed, 19 Apr 2000 18:29:55 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPGEKGCCAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01BFAA2D.42892E40"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <2F4A3F6B7BF5D3119E2500508B94E65645A138@uscntnt405a.us.deloitte.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@ipsec.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01BFAA2D.42892E40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

RE: Tunnel-Medium-Type value for FR and ATMThe mediuam-type field is a
guideline to the Tunnel Initiator what to expect in the Tunnel Endpoint
Address field.
  I do agree with you that it does not clearly capture the medium (For
Example: E.164 is the addressing standard and it does not specify (SMDS, FR
or ATM).

  Is it really necessary to do so, though?  If so, why?

  May be we need to add a more specific value to the set of AVPs retrieved
from RADIUS.

  Regards

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



  -----Original Message-----
  From: Madhvi Verma [mailto:Madhvi_Verma@mw.3com.com]
  Sent: Wednesday, April 19, 2000 1:45 PM
  To: l2tp@ipsec.org
  Subject: Tunnel-Medium-Type value for FR and ATM





  Hi,
  What do you use as the tunnel-medium-type (RADIUS attribute :65) value for
the
  following media?
  FR:
  AAL5:

  The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following
address
  values :
         1      IPv4 (IP version 4)
         2      IPv6 (IP version 6)
         3      NSAP
         4      HDLC (8-bit multidrop)
         5      BBN 1822
         6      802 (includes all 802 media plus Ethernet "canonical
format")
         7      E.163 (POTS)
         8      E.164 (SMDS, Frame Relay, ATM)
         9      F.69 (Telex)
         10     X.121 (X.25, Frame Relay)
         11     IPX
         12     Appletalk
         13     Decnet IV
         14     Banyan Vines
         15     E.164 with NSAP format subaddress



  Does this mean that the value is addressing dependent, and not media
dependent !
  Inputs appreciated?

  Madhvi


------=_NextPart_000_0006_01BFAA2D.42892E40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: Tunnel-Medium-Type value for FR and ATM</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR></HEAD>
<BODY>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT=20
  face=3DTahoma></DIV></FONT>
  <P><FONT size=3D2>The mediuam-type field is a guideline to the Tunnel =
Initiator=20
  what to expect in the Tunnel Endpoint Address field. <BR>I do agree =
with you=20
  that it does not clearly capture the medium (For Example: E.164 is the =

  addressing standard and it does not specify (SMDS, FR or ATM).<FONT=20
  color=3D#0000ff face=3DArial><SPAN=20
  class=3D640052901-20042000>&nbsp;</SPAN></FONT></FONT></P>
  <P><FONT size=3D2><FONT color=3D#0000ff face=3DArial><SPAN=20
  class=3D640052901-20042000>Is it really necessary to do so, =
though?&nbsp; If so,=20
  why?&nbsp;</SPAN></FONT></FONT></P>
  <P><FONT size=3D2>May be we need to add a more specific value to the =
set of AVPs=20
  retrieved from RADIUS.</FONT> </P>
  <P><FONT size=3D2>Regards</FONT> </P>
  <P><FONT size=3D2>Rohit Verma</FONT> <BR><FONT size=3D2>Deloitte =
Consulting</FONT>=20
  <BR><FONT size=3D2>180, N. Stetson Avenue</FONT> <BR><FONT =
size=3D2>Chicago,=20
  Illinois 60601</FONT> <BR><FONT size=3D2>Phone:312-374-2475</FONT> =
</P><BR>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
  Madhvi Verma [<A=20
  =
href=3D"mailto:Madhvi_Verma@mw.3com.com">mailto:Madhvi_Verma@mw.3com.com<=
/A>]</FONT>=20
  <BR><FONT size=3D2>Sent: Wednesday, April 19, 2000 1:45 PM</FONT> =
<BR><FONT=20
  size=3D2>To: l2tp@ipsec.org</FONT> <BR><FONT size=3D2>Subject: =
Tunnel-Medium-Type=20
  value for FR and ATM</FONT> </P><BR><BR><BR>
  <P><FONT size=3D2>Hi,</FONT> <BR><FONT size=3D2>What do you use as the =

  tunnel-medium-type (RADIUS attribute :65) value for the</FONT> =
<BR><FONT=20
  size=3D2>following media?</FONT> <BR><FONT size=3D2>FR:</FONT> =
<BR><FONT=20
  size=3D2>AAL5:</FONT> </P>
  <P><FONT size=3D2>The draft "draft-ietf-radius-tunnel-auth-09.txt" =
mentions the=20
  following address</FONT> <BR><FONT size=3D2>values :</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  IPv4 (IP version 4)</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  IPv6 (IP version 6)</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  NSAP</FONT> <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HDLC (8-bit multidrop)</FONT> =
<BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  BBN 1822</FONT> <BR><FONT =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 802 (includes all 802 media plus =
Ethernet=20
  "canonical format")</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  E.163 (POTS)</FONT> <BR><FONT =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E.164 (SMDS, Frame Relay, ATM)</FONT>=20
  <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F.69 (Telex)</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
10&nbsp;&nbsp;&nbsp;&nbsp; X.121=20
  (X.25, Frame Relay)</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
11&nbsp;&nbsp;&nbsp;&nbsp;=20
  IPX</FONT> <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  12&nbsp;&nbsp;&nbsp;&nbsp; Appletalk</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
13&nbsp;&nbsp;&nbsp;&nbsp; Decnet=20
  IV</FONT> <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  14&nbsp;&nbsp;&nbsp;&nbsp; Banyan Vines</FONT> <BR><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
15&nbsp;&nbsp;&nbsp;&nbsp; E.164=20
  with NSAP format subaddress</FONT> </P><BR>
  <P><FONT size=3D2>Does this mean that the value is addressing =
dependent, and not=20
  media dependent !</FONT> <BR><FONT size=3D2>Inputs appreciated?</FONT> =
</P>
  <P><FONT size=3D2>Madhvi</FONT> </P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0006_01BFAA2D.42892E40--



From owner-l2tp@ipsec.org  Thu Apr 20 01:06:40 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21573
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 01:06:39 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id VAA29584; Wed, 19 Apr 2000 21:07:51 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id VAA29576 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 21:07:23 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id VAA02628 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 21:06:52 -0700 (PDT)
Message-ID: <38FE825B.565DBCF2@cisco.com>
Date: Thu, 20 Apr 2000 00:06:51 -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@ipsec.org
Subject: IANA Considerations
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I initiated discussion with our ADs recently regarding the IANA
considerations in RFC 2661.

There are two decisions we face, and have not reached clear agreement.
I'd like to get a feel of the WGs opinion here.

Issue #1

Currently, a new IETF AVP value may only be requested for RFCs. That is,
after last call and approval by the IESG. In DC we discussed (and agreed
upon) the value in obtaining numbers from IANA here at an earlier stage
so as to reduce the risk of ultimately maintaining two values (the IANA
number and whatever vendor-specific number that was originally
documented). 

We have three choices.

A. Stay where we are, and request IANA numbers only after the RFC
publication is imminent.
B. Write a short RFC modifying the policy.
C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
until it is published before it can be followed.

The new policy might be that a person (such as the WG chair) is
appointed to determine when the WG has sufficient consensus to request a
value. This would typically be at or near the point of last call,
depending on implementation demand and clarity of consensus.

Issue #2

This is simply where to begin handing out new values for AVPs. The
highest value now is 39. We have two choices.

A. Begin at 40
B. Begin at some other value slightly higher, say, 50, so that *if* we
end up adding an AVP or two to the base spec as it advances, we can
remain contiguous in the base spec.

Opinions appreciated. Thanks,

- Mark


From owner-l2tp@ipsec.org  Thu Apr 20 02:12:49 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03167
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 02:12:48 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id VAA29574; Wed, 19 Apr 2000 21:06:54 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id VAA29570 for <l2tp@ipsec.org>; Wed, 19 Apr 2000 21:05:31 -0700 (PDT)
Received: by ans2-pub.dttus.com id XAA04503
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Wed, 19 Apr 2000 23:05:30 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Wed, 19 Apr 2000 23:05:30 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Wed, 19 Apr 2000 23:05:30 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E6564DF53B@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: gwz@cisco.com, Madhvi Verma <Madhvi_Verma@mw.3com.com>, l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM
Date: Wed, 19 Apr 2000 23:01:13 -0500
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFAA7D.10292D92"
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_01BFAA7D.10292D92
Content-Type: text/plain;
	charset="iso-8859-1"

Please see comments below.
 
Regards

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

-----Original Message-----
From: Glen Zorn [mailto:gwz@cisco.com]
Sent: Wednesday, April 19, 2000 8:30 PM
To: Verma, Rohit (US - Chicago); Madhvi Verma; l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM





The mediuam-type field is a guideline to the Tunnel Initiator what to expect
in the Tunnel Endpoint Address field. 
I do agree with you that it does not clearly capture the medium (For
Example: E.164 is the addressing standard and it does not specify (SMDS, FR
or ATM). 

Is it really necessary to do so, though?  If so, why? 
[Rohit Verma] 

Yes, it is important for tunnel initiators (TI) that support both ATM and FR
type interfaces. When a TI receives a RADIUS accept with tunne type set to
L2TP and the medium type to an E.164 address, it needs to figure out what
interface (FR or ATM) to use for the tunnel. 

Pardon my ignorance but I am not sure if E.164 address on its own can be
used to do that distinction. Can anybody confirm that ?

May be we need to add a more specific value to the set of AVPs retrieved
from RADIUS. 

Regards 

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


-----Original Message----- 
From: Madhvi Verma [ mailto:Madhvi_Verma@mw.3com.com
<mailto:Madhvi_Verma@mw.3com.com> ] 
Sent: Wednesday, April 19, 2000 1:45 PM 
To: l2tp@ipsec.org 
Subject: Tunnel-Medium-Type value for FR and ATM 




Hi, 
What do you use as the tunnel-medium-type (RADIUS attribute :65) value for
the 
following media? 
FR: 
AAL5: 

The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following
address 
values : 
       1      IPv4 (IP version 4) 
       2      IPv6 (IP version 6) 
       3      NSAP 
       4      HDLC (8-bit multidrop) 
       5      BBN 1822 
       6      802 (includes all 802 media plus Ethernet "canonical format") 
       7      E.163 (POTS) 
       8      E.164 (SMDS, Frame Relay, ATM) 
       9      F.69 (Telex) 
       10     X.121 (X.25, Frame Relay) 
       11     IPX 
       12     Appletalk 
       13     Decnet IV 
       14     Banyan Vines 
       15     E.164 with NSAP format subaddress 


Does this mean that the value is addressing dependent, and not media
dependent ! 
Inputs appreciated? 

Madhvi 


------_=_NextPart_001_01BFAA7D.10292D92
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: Tunnel-Medium-Type value for FR and ATM</TITLE>

<META content="MSHTML 5.00.2614.3500" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=960075803-20042000>Please 
see comments below.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=960075803-20042000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=960075803-20042000>Regards</SPAN></FONT></DIV>
<P><B><I><FONT size=2><FONT color=#000080><FONT face=Arial><SPAN 
class=960075803-20042000></SPAN>Rohit Verma</FONT></FONT></FONT></I></B> 
<BR><B><I><FONT color=#000080 face=Arial size=2>Deloitte 
Consulting</FONT></I></B> <BR><B><I><FONT color=#000080 face=Arial size=2>180, 
N. Stetson Avenue</FONT></I></B> <BR><B><I><FONT color=#000080 face=Arial 
size=2>Chicago, Illinois 60601</FONT></I></B> <BR><B><I><FONT color=#000080 
face=Arial size=2>Phone:312-374-2475</FONT></I></B><I></I> </P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Glen Zorn 
  [mailto:gwz@cisco.com]<BR><B>Sent:</B> Wednesday, April 19, 2000 8:30 
  PM<BR><B>To:</B> Verma, Rohit (US - Chicago); Madhvi Verma; 
  l2tp@ipsec.org<BR><B>Subject:</B> RE: Tunnel-Medium-Type value for FR and 
  ATM<BR><BR></DIV></FONT>
  <BLOCKQUOTE 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV align=left class=OutlookMessageHeader dir=ltr><FONT 
    face=Tahoma></DIV></FONT>
    <P><FONT size=2>The mediuam-type field is a guideline to the Tunnel 
    Initiator what to expect in the Tunnel Endpoint Address field. <BR>I do 
    agree with you that it does not clearly capture the medium (For Example: 
    E.164 is the addressing standard and it does not specify (SMDS, FR or 
    ATM).<FONT color=#0000ff face=Arial><SPAN 
    class=640052901-20042000>&nbsp;</SPAN></FONT></FONT></P>
    <P><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=640052901-20042000>Is it really necessary to do so, though?&nbsp; If 
    so, why?&nbsp;<BR><SPAN class=960075803-20042000>[Rohit 
    Verma]&nbsp;</SPAN></SPAN></FONT></FONT></FONT><FONT size=2><FONT 
    color=#0000ff><FONT face=Arial><SPAN class=640052901-20042000><SPAN 
    class=960075803-20042000></SPAN></SPAN></FONT></FONT></FONT></P>
    <P><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=640052901-20042000><SPAN class=960075803-20042000>Yes, it is important 
    for tunnel initiators (TI)  that support both ATM and FR type interfaces. 
    When a&nbsp;TI receives a RADIUS accept with tunne type set to L2TP and the 
    medium type to an E.164 address, it needs to figure out what interface (FR 
    or ATM) to use for the tunnel. </SPAN></SPAN></FONT></FONT></FONT></P>
    <P><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=640052901-20042000><SPAN class=960075803-20042000>Pardon my ignorance 
    but I am not sure if E.164 address on its own can be used to do that 
    distinction. Can anybody confirm that 
    ?</SPAN></SPAN></FONT></FONT></FONT></P>
    <P><FONT size=2>May be we need to add a more specific value to the set of 
    AVPs retrieved from RADIUS.</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: 
    Madhvi Verma [<A 
    href="mailto:Madhvi_Verma@mw.3com.com">mailto:Madhvi_Verma@mw.3com.com</A>]</FONT> 
    <BR><FONT size=2>Sent: Wednesday, April 19, 2000 1:45 PM</FONT> <BR><FONT 
    size=2>To: l2tp@ipsec.org</FONT> <BR><FONT size=2>Subject: 
    Tunnel-Medium-Type value for FR and ATM</FONT> </P><BR><BR><BR>
    <P><FONT size=2>Hi,</FONT> <BR><FONT size=2>What do you use as the 
    tunnel-medium-type (RADIUS attribute :65) value for the</FONT> <BR><FONT 
    size=2>following media?</FONT> <BR><FONT size=2>FR:</FONT> <BR><FONT 
    size=2>AAL5:</FONT> </P>
    <P><FONT size=2>The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions 
    the following address</FONT> <BR><FONT size=2>values :</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    IPv4 (IP version 4)</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    IPv6 (IP version 6)</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    NSAP</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HDLC (8-bit multidrop)</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    BBN 1822</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 802 (includes all 802 media plus Ethernet 
    "canonical format")</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    E.163 (POTS)</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E.164 (SMDS, Frame Relay, ATM)</FONT> 
    <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F.69 (Telex)</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp; X.121 
    (X.25, Frame Relay)</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 11&nbsp;&nbsp;&nbsp;&nbsp; 
    IPX</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    12&nbsp;&nbsp;&nbsp;&nbsp; Appletalk</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 13&nbsp;&nbsp;&nbsp;&nbsp; 
    Decnet IV</FONT> <BR><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    14&nbsp;&nbsp;&nbsp;&nbsp; Banyan Vines</FONT> <BR><FONT 
    size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15&nbsp;&nbsp;&nbsp;&nbsp; E.164 
    with NSAP format subaddress</FONT> </P><BR>
    <P><FONT size=2>Does this mean that the value is addressing dependent, and 
    not media dependent !</FONT> <BR><FONT size=2>Inputs appreciated?</FONT> 
</P>
    <P><FONT size=2>Madhvi</FONT> </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFAA7D.10292D92--


From owner-l2tp@ipsec.org  Thu Apr 20 05:54:04 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04827
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 05:54:04 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id AAA29835; Thu, 20 Apr 2000 00:52:57 -0700 (PDT)
Received: from relay1.marconi.it (relay1.marconi.it [192.106.52.1]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id AAA29831 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 00:52:41 -0700 (PDT)
Received: by relay1.marconi.it (8.9.1a/8.9.1) id JAA24363
	for l2tp@ipsec.org; Thu, 20 Apr 2000 09:48:28 +0200 (MET DST)
Received: from marconicomms.com (gedgwy01.marconi.it [172.16.123.237])
	by relay1.marconi.it (8.9.1a/8.9.1) with SMTP id JAA24342
	for <l2tp@ipsec.org>; Thu, 20 Apr 2000 09:48:16 +0200 (MET DST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id C12568C7.002B22A2 ; Thu, 20 Apr 2000 09:51:09 +0200
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Luigi Campora" <Luigi.Campora@Marconicomms.com>
To: l2tp@ipsec.org
Message-ID: <C12568C7.002B2182.00@marconicomms.com>
Date: Thu, 20 Apr 2000 09:51:25 +0200
Subject: PID value for L2TPoA
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk




Dear subscribers,
I have a doubt concerning the AAL5 packet format to be used when transporting
L2TP over ATM.

draft-ietf-l2tpext-l2tp-atm-00 states that when using LLC encapsulation, the
IANA
OUI shall be used, while the PID is to be determined by IANA.
Can soneone address me the document where this number is defined?


Thank you.

Luigi

------------------------------------------------------------------------------------------------
Luigi Campora
Marconi Communications Group - Access Networks Division
Genova - Italy




From owner-l2tp@ipsec.org  Thu Apr 20 12:12:19 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14460
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 12:12:18 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id IAA01630; Thu, 20 Apr 2000 08:06:46 -0700 (PDT)
Received: from mw.3com.com (intergate.usr.com [149.112.20.3]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA01626 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 08:06:21 -0700 (PDT)
Received: from mwgate02.mw.3com.com by mw.3com.com (8.8.5/3.1.090690-3Com Corporation)
	id KAA23186; Thu, 20 Apr 2000 10:01:29 -0500 (CDT)
Received: by mwgate02.mw.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 862568C7.0052B6B1 ; Thu, 20 Apr 2000 10:03:27 -0500
X-Lotus-FromDomain: 3COM@3COM-MWGATE
From: "Janakiraman Senthilnathan" <Janakiraman_Senthilnathan@mw.3com.com>
To: "Luigi Campora" <Luigi.Campora@Marconicomms.com>
cc: l2tp@ipsec.org
Message-ID: <862568C7.0052B509.00@mwgate02.mw.3com.com>
Date: Thu, 20 Apr 2000 10:03:32 -0500
Subject: Re: PID value for L2TPoA
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk




Luigi,

Please use 0x0007 for L2TP and 00-00-5E for IANA's OUI.
0x0007 was assigned for L2TP over FR and we can use the
same for L2TP over AAL5.

Regards,

senthil.





"Luigi Campora" <Luigi.Campora@Marconicomms.com> on 04/20/2000 02:51:25 AM

Sent by:  "Luigi Campora" <Luigi.Campora@Marconicomms.com>


To:   l2tp@ipsec.org
cc:    (Janakiraman Senthilnathan/MW/US/3Com)
Subject:  PID value for L2TPoA






Dear subscribers,
I have a doubt concerning the AAL5 packet format to be used when transporting
L2TP over ATM.

draft-ietf-l2tpext-l2tp-atm-00 states that when using LLC encapsulation, the
IANA
OUI shall be used, while the PID is to be determined by IANA.
Can soneone address me the document where this number is defined?


Thank you.

Luigi

------------------------------------------------------------------------------------------------

Luigi Campora
Marconi Communications Group - Access Networks Division
Genova - Italy








From owner-l2tp@ipsec.org  Thu Apr 20 14:00:11 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17343
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 14:00:11 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA01864; Thu, 20 Apr 2000 10:00:42 -0700 (PDT)
Received: from zev.net (zev.net [206.111.135.146]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA01860 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 10:00:16 -0700 (PDT)
Received: from zev.net (localhost.zev.net [127.0.0.1] (may be forged))
	by zev.net (8.9.3/8.9.3) with ESMTP id JAA08041;
	Thu, 20 Apr 2000 09:59:46 -0700 (PDT)
Message-Id: <200004201659.JAA08041@zev.net>
To: Evan Caves <evan.caves@ericsson.com>
cc: "W. Mark Townsley" <townsley@cisco.com>, l2tp@ipsec.org
Subject: Re: IANA Considerations 
In-reply-to: Your message of "Thu, 20 Apr 2000 09:59:34 PDT."
             <38FF3776.F5A858CA@ericsson.com> 
Date: Thu, 20 Apr 2000 09:59:46 -0700
From: Bill Palter <palter@zev.net>
Sender: owner-l2tp@ipsec.org
Precedence: bulk

> Would it make it any easier if we defined an 'experimental' vendor ID
> which IANA can allocate AVP types/values out of. The number space could
> mirror the IETF number space (may be hard to manage) so that if adopted
> the type/values remain the same, just the vendor ID changes.
> 
> just a thought,


  I like it......Wonder what we need to do to get a vendor id allocated..
> 
> evan
> -
> 
> "W. Mark Townsley" wrote:
> > 
> > I initiated discussion with our ADs recently regarding the IANA
> > considerations in RFC 2661.
> > 
> > There are two decisions we face, and have not reached clear agreement.
> > I'd like to get a feel of the WGs opinion here.
> > 
> > Issue #1
> > 
> > Currently, a new IETF AVP value may only be requested for RFCs. That is,
> > after last call and approval by the IESG. In DC we discussed (and agreed
> > upon) the value in obtaining numbers from IANA here at an earlier stage
> > so as to reduce the risk of ultimately maintaining two values (the IANA
> > number and whatever vendor-specific number that was originally
> > documented).
> > 
> > We have three choices.
> > 
> > A. Stay where we are, and request IANA numbers only after the RFC
> > publication is imminent.
> > B. Write a short RFC modifying the policy.
> > C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
> > until it is published before it can be followed.
> > 
> > The new policy might be that a person (such as the WG chair) is
> > appointed to determine when the WG has sufficient consensus to request a
> > value. This would typically be at or near the point of last call,
> > depending on implementation demand and clarity of consensus.
> > 
> > Issue #2
> > 
> > This is simply where to begin handing out new values for AVPs. The
> > highest value now is 39. We have two choices.
> > 
> > A. Begin at 40
> > B. Begin at some other value slightly higher, say, 50, so that *if* we
> > end up adding an AVP or two to the base spec as it advances, we can
> > remain contiguous in the base spec.
> > 
> > Opinions appreciated. Thanks,
> > 
> > - Mark
--
Bill Palter (Palter@zev.net)


From owner-l2tp@ipsec.org  Thu Apr 20 14:00:59 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17389
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 14:00:59 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id JAA01837; Thu, 20 Apr 2000 09:57:02 -0700 (PDT)
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA01828 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 09:56:26 -0700 (PDT)
Received: from ericsson.com (unk105122.acc.com [129.192.105.122])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id JAA14496;
	Thu, 20 Apr 2000 09:59:09 -0700 (PDT)
Message-ID: <38FF3776.F5A858CA@ericsson.com>
Date: Thu, 20 Apr 2000 09:59:34 -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: "W. Mark Townsley" <townsley@cisco.com>
CC: l2tp@ipsec.org
Subject: Re: IANA Considerations
References: <38FE825B.565DBCF2@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Would it make it any easier if we defined an 'experimental' vendor ID
which IANA can allocate AVP types/values out of. The number space could
mirror the IETF number space (may be hard to manage) so that if adopted
the type/values remain the same, just the vendor ID changes.

just a thought,

evan
-

"W. Mark Townsley" wrote:
> 
> I initiated discussion with our ADs recently regarding the IANA
> considerations in RFC 2661.
> 
> There are two decisions we face, and have not reached clear agreement.
> I'd like to get a feel of the WGs opinion here.
> 
> Issue #1
> 
> Currently, a new IETF AVP value may only be requested for RFCs. That is,
> after last call and approval by the IESG. In DC we discussed (and agreed
> upon) the value in obtaining numbers from IANA here at an earlier stage
> so as to reduce the risk of ultimately maintaining two values (the IANA
> number and whatever vendor-specific number that was originally
> documented).
> 
> We have three choices.
> 
> A. Stay where we are, and request IANA numbers only after the RFC
> publication is imminent.
> B. Write a short RFC modifying the policy.
> C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
> until it is published before it can be followed.
> 
> The new policy might be that a person (such as the WG chair) is
> appointed to determine when the WG has sufficient consensus to request a
> value. This would typically be at or near the point of last call,
> depending on implementation demand and clarity of consensus.
> 
> Issue #2
> 
> This is simply where to begin handing out new values for AVPs. The
> highest value now is 39. We have two choices.
> 
> A. Begin at 40
> B. Begin at some other value slightly higher, say, 50, so that *if* we
> end up adding an AVP or two to the base spec as it advances, we can
> remain contiguous in the base spec.
> 
> Opinions appreciated. Thanks,
> 
> - Mark


From owner-l2tp@ipsec.org  Thu Apr 20 14:19:03 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17904
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 14:19:03 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id KAA01922; Thu, 20 Apr 2000 10:25:15 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA01918 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 10:24:45 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA26089;
	Thu, 20 Apr 2000 11:24:38 -0600 (MDT)
Received: from ha1mpk-mail.eng.sun.com (phys-ha1mpka.Eng.Sun.COM [129.146.51.34])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id KAA21324;
	Thu, 20 Apr 2000 10:24:37 -0700 (PDT)
Received: from mordor by ha1mpk-mail.eng.sun.com (SMI-8.6/SMI-SVR4)
	id KAA13038; Thu, 20 Apr 2000 10:24:32 -0700
Date: Thu, 20 Apr 2000 10:24:32 -0700 (PDT)
From: "pcalhoun@eng.sun.com" <pcalhoun@ha1mpk-mail.Eng.Sun.COM>
Reply-To: "pcalhoun@eng.sun.com" <pcalhoun@ha1mpk-mail.Eng.Sun.COM>
Subject: Re: IANA Considerations 
To: Bill Palter <palter@zev.net>
Cc: Evan Caves <evan.caves@ericsson.com>,
        "W. Mark Townsley" <townsley@cisco.com>, l2tp@ipsec.org
In-Reply-To: "Your message with ID" <200004201659.JAA08041@zev.net>
Message-ID: <Roam.SIMC.2.0.6.956251472.4832.pcalhoun@ha1mpk-mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk

hmmm... I'm not sure that this is really the direction that we want. I would
actually ask that we update RFC2661, and state that the numbers are assigned
from a Designated Expert, which is frequently done.

The con: We have to reset the clock before moving to draft standard.

The pro: Number allocation actually works

PatC



From owner-l2tp@ipsec.org  Thu Apr 20 14:45:02 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18464
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 14:45:01 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA01977; Thu, 20 Apr 2000 10:50:06 -0700 (PDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA01970 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 10:49:40 -0700 (PDT)
Received: from gwz (sj-dial-1-235.cisco.com [171.68.179.236]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id KAA20499; Thu, 20 Apr 2000 10:49:07 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "W. Mark Townsley" <townsley@cisco.com>, <l2tp@ipsec.org>
Subject: RE: IANA Considerations
Date: Thu, 20 Apr 2000 10:48:54 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPCELICCAA.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.2314.1300
In-Reply-To: <38FE825B.565DBCF2@cisco.com>
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>
>
> I initiated discussion with our ADs recently regarding the IANA
> considerations in RFC 2661.
>
> There are two decisions we face, and have not reached clear agreement.
> I'd like to get a feel of the WGs opinion here.
>
> Issue #1
>
> Currently, a new IETF AVP value may only be requested for RFCs. That is,
> after last call and approval by the IESG. In DC we discussed (and agreed
> upon) the value in obtaining numbers from IANA here at an earlier stage
> so as to reduce the risk of ultimately maintaining two values (the IANA
> number and whatever vendor-specific number that was originally
> documented).
>
> We have three choices.
>
> A. Stay where we are, and request IANA numbers only after the RFC
> publication is imminent.
> B. Write a short RFC modifying the policy.

Good idea.

> C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
> until it is published before it can be followed.
>
> The new policy might be that a person (such as the WG chair) is
> appointed to determine when the WG has sufficient consensus to request a
> value. This would typically be at or near the point of last call,
> depending on implementation demand and clarity of consensus.
>
> Issue #2
>
> This is simply where to begin handing out new values for AVPs. The
> highest value now is 39. We have two choices.
>
> A. Begin at 40
> B. Begin at some other value slightly higher, say, 50, so that *if* we
> end up adding an AVP or two to the base spec as it advances, we can
> remain contiguous in the base spec.

Semi-contiguous, unless all 10 numbers are used.  If none are used, then
there will be a hole; how big a hole is acceptable seems to be highly
implementation-dependent, to the point of being a matter of taste.

>
> Opinions appreciated. Thanks,
>
> - Mark
>
>



From owner-l2tp@ipsec.org  Thu Apr 20 15:31:52 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19739
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 15:31:51 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id LAA02083; Thu, 20 Apr 2000 11:33:02 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id LAA02079 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 11:31:48 -0700 (PDT)
Received: by ans2-pub.dttus.com id NAA16853
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Thu, 20 Apr 2000 13:31:45 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Thu, 20 Apr 2000 13:31:45 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Thu, 20 Apr 2000 13:31:45 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E6564DFAFD@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: "W. Mark Townsley" <townsley@cisco.com>, l2tp@ipsec.org
Subject: RE: IANA Considerations
Date: Thu, 20 Apr 2000 14:29:15 -0400
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFAAF6.558C19E8"
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_01BFAAF6.558C19E8
Content-Type: text/plain;
	charset="iso-8859-1"

For Issue #2:-
We have 2 bytes available for the Attribute Type. Why don't we hand new
AVP's with the precondition that the MSBit for the new AVPs must be 1.

New AVPs 0x80, 0x81 ....0xff
Base Spec AVPs 0x01....0x7f

This precondition it will ensure continuity for the base spec to a large
Attribute Type space.
Also it will be easier for implementations to differentiate between base
spec AVPs and new ones.


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


-----Original Message-----
From: W. Mark Townsley [mailto:townsley@cisco.com]
Sent: Wednesday, April 19, 2000 11:07 PM
To: l2tp@ipsec.org
Subject: IANA Considerations



I initiated discussion with our ADs recently regarding the IANA
considerations in RFC 2661.

There are two decisions we face, and have not reached clear agreement.
I'd like to get a feel of the WGs opinion here.

Issue #1

Currently, a new IETF AVP value may only be requested for RFCs. That is,
after last call and approval by the IESG. In DC we discussed (and agreed
upon) the value in obtaining numbers from IANA here at an earlier stage
so as to reduce the risk of ultimately maintaining two values (the IANA
number and whatever vendor-specific number that was originally
documented). 

We have three choices.

A. Stay where we are, and request IANA numbers only after the RFC
publication is imminent.
B. Write a short RFC modifying the policy.
C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
until it is published before it can be followed.

The new policy might be that a person (such as the WG chair) is
appointed to determine when the WG has sufficient consensus to request a
value. This would typically be at or near the point of last call,
depending on implementation demand and clarity of consensus.

Issue #2

This is simply where to begin handing out new values for AVPs. The
highest value now is 39. We have two choices.

A. Begin at 40
B. Begin at some other value slightly higher, say, 50, so that *if* we
end up adding an AVP or two to the base spec as it advances, we can
remain contiguous in the base spec.

Opinions appreciated. Thanks,

- Mark

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

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

<P><FONT SIZE=3D2>For Issue #2:-</FONT>
<BR><FONT SIZE=3D2>We have 2 bytes available for the Attribute Type. =
Why don't we hand new AVP's with the precondition that the MSBit for =
the new AVPs must be 1.</FONT></P>

<P><FONT SIZE=3D2>New AVPs 0x80, 0x81 ....0xff</FONT>
<BR><FONT SIZE=3D2>Base Spec AVPs 0x01....0x7f</FONT>
</P>

<P><FONT SIZE=3D2>This precondition it will ensure continuity for the =
base spec to a large Attribute Type space.</FONT>
<BR><FONT SIZE=3D2>Also it will be easier for implementations to =
differentiate between base spec AVPs and new ones.</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: W. Mark Townsley [<A =
HREF=3D"mailto:townsley@cisco.com">mailto:townsley@cisco.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, April 19, 2000 11:07 PM</FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: IANA Considerations</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>I initiated discussion with our ADs recently =
regarding the IANA</FONT>
<BR><FONT SIZE=3D2>considerations in RFC 2661.</FONT>
</P>

<P><FONT SIZE=3D2>There are two decisions we face, and have not reached =
clear agreement.</FONT>
<BR><FONT SIZE=3D2>I'd like to get a feel of the WGs opinion =
here.</FONT>
</P>

<P><FONT SIZE=3D2>Issue #1</FONT>
</P>

<P><FONT SIZE=3D2>Currently, a new IETF AVP value may only be requested =
for RFCs. That is,</FONT>
<BR><FONT SIZE=3D2>after last call and approval by the IESG. In DC we =
discussed (and agreed</FONT>
<BR><FONT SIZE=3D2>upon) the value in obtaining numbers from IANA here =
at an earlier stage</FONT>
<BR><FONT SIZE=3D2>so as to reduce the risk of ultimately maintaining =
two values (the IANA</FONT>
<BR><FONT SIZE=3D2>number and whatever vendor-specific number that was =
originally</FONT>
<BR><FONT SIZE=3D2>documented). </FONT>
</P>

<P><FONT SIZE=3D2>We have three choices.</FONT>
</P>

<P><FONT SIZE=3D2>A. Stay where we are, and request IANA numbers only =
after the RFC</FONT>
<BR><FONT SIZE=3D2>publication is imminent.</FONT>
<BR><FONT SIZE=3D2>B. Write a short RFC modifying the policy.</FONT>
<BR><FONT SIZE=3D2>C. Modify RFC 2661 in the next rev to reflect a new =
policy, and wait</FONT>
<BR><FONT SIZE=3D2>until it is published before it can be =
followed.</FONT>
</P>

<P><FONT SIZE=3D2>The new policy might be that a person (such as the WG =
chair) is</FONT>
<BR><FONT SIZE=3D2>appointed to determine when the WG has sufficient =
consensus to request a</FONT>
<BR><FONT SIZE=3D2>value. This would typically be at or near the point =
of last call,</FONT>
<BR><FONT SIZE=3D2>depending on implementation demand and clarity of =
consensus.</FONT>
</P>

<P><FONT SIZE=3D2>Issue #2</FONT>
</P>

<P><FONT SIZE=3D2>This is simply where to begin handing out new values =
for AVPs. The</FONT>
<BR><FONT SIZE=3D2>highest value now is 39. We have two choices.</FONT>
</P>

<P><FONT SIZE=3D2>A. Begin at 40</FONT>
<BR><FONT SIZE=3D2>B. Begin at some other value slightly higher, say, =
50, so that *if* we</FONT>
<BR><FONT SIZE=3D2>end up adding an AVP or two to the base spec as it =
advances, we can</FONT>
<BR><FONT SIZE=3D2>remain contiguous in the base spec.</FONT>
</P>

<P><FONT SIZE=3D2>Opinions appreciated. Thanks,</FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01BFAAF6.558C19E8--


From owner-l2tp@ipsec.org  Thu Apr 20 17:06:53 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21370
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 17:06:52 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA02244; Thu, 20 Apr 2000 13:00:50 -0700 (PDT)
Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA02234 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 13:00:00 -0700 (PDT)
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.22 2000/04/06 17:58:51 dmccart Exp $) with SMTP id MAA16125;
	Thu, 20 Apr 2000 12:57:36 -0700 (PDT)
Received: from orsmsx29.jf.intel.com ([192.168.70.29]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Thu, 20 Apr 2000 19:57:35 0000 (GMT)
Received: by orsmsx29.jf.intel.com with Internet Mail Service (5.5.2448.0)
	id <JJ9R9XLF>; Thu, 20 Apr 2000 12:57:33 -0700
Message-ID: <392A357CE6FFD111AC3E00A0C99848B003694CC4@hdsmsx31.hd.intel.com>
From: "Shriver, John" <john.shriver@intel.com>
To: "'Verma, Rohit (US - Chicago)'" <rverma@dc.com>, gwz@cisco.com,
        Madhvi Verma <Madhvi_Verma@mw.3com.com>, l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM
Date: Thu, 20 Apr 2000 12:57:28 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

As a co-author of the RFC (and author of the text in question), note that
when Tunel-Medium-Type isn't IPv4 or IPv6, Tunnel-Client-Endpoint and
Tunnel-Server-Endpoint are string names.  Freeform.  Not structured
according to any rule based on the value of Tunnel-Medium-Type.  Note that
Tunnel-Client-Endpoint can be an address, or an interface, as necessary.
 
These strings are tags that refer to some part of the tunnel initiator's
configuration database, which indicates the interface to be used and the
endpoint theron.  It's done this way because there is no IETF standard
syntax for naming interfaces.  
 
Yes, this does mean that you have to coordinate the configuration of the
RADIUS server and the RADIUS client.  But by making it be this way, you can
serve three different brands of RADIUS clients with one RADIUS server.  If
the Ascend RADIUS client wanted a Tunnel-Client-Endpoint in the format
"FrameRelaySlot3:Port4", and the Cisco RADIUS client wanted "Frame Relay
3/4", you would be screwed.  The RADIUS server could not provide an answer
that was correct for both.  By making it clear that it must be a tag
indendpendent from the configuration of any particular product, you're not
screwed in this case.
 
I put this in because when we were Shiva, we had to add mappings to map our
configuration to Ascend syntax for some of their proprietary attributes that
we implemented.  I wanted this standard to be vendor-neutral, and this was
the simplest way to do that.
 
 -----Original Message-----
From: Verma, Rohit (US - Chicago) [mailto:rverma@dc.com]
Sent: Thursday, April 20, 2000 12:01 AM
To: gwz@cisco.com; Madhvi Verma; l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM



Please see comments below.
 
Regards

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

-----Original Message-----
From: Glen Zorn [mailto:gwz@cisco.com]
Sent: Wednesday, April 19, 2000 8:30 PM
To: Verma, Rohit (US - Chicago); Madhvi Verma; l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM





The mediuam-type field is a guideline to the Tunnel Initiator what to expect
in the Tunnel Endpoint Address field. 
I do agree with you that it does not clearly capture the medium (For
Example: E.164 is the addressing standard and it does not specify (SMDS, FR
or ATM). 

Is it really necessary to do so, though?  If so, why? 
[Rohit Verma] 

Yes, it is important for tunnel initiators (TI) that support both ATM and FR
type interfaces. When a TI receives a RADIUS accept with tunne type set to
L2TP and the medium type to an E.164 address, it needs to figure out what
interface (FR or ATM) to use for the tunnel. 

Pardon my ignorance but I am not sure if E.164 address on its own can be
used to do that distinction. Can anybody confirm that ?

May be we need to add a more specific value to the set of AVPs retrieved
from RADIUS. 

Regards 

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


-----Original Message----- 
From: Madhvi Verma [ mailto:Madhvi_Verma@mw.3com.com
<mailto:Madhvi_Verma@mw.3com.com> ] 
Sent: Wednesday, April 19, 2000 1:45 PM 
To: l2tp@ipsec.org 
Subject: Tunnel-Medium-Type value for FR and ATM 




Hi, 
What do you use as the tunnel-medium-type (RADIUS attribute :65) value for
the 
following media? 
FR: 
AAL5: 

The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following
address 
values : 
       1      IPv4 (IP version 4) 
       2      IPv6 (IP version 6) 
       3      NSAP 
       4      HDLC (8-bit multidrop) 
       5      BBN 1822 
       6      802 (includes all 802 media plus Ethernet "canonical format") 
       7      E.163 (POTS) 
       8      E.164 (SMDS, Frame Relay, ATM) 
       9      F.69 (Telex) 
       10     X.121 (X.25, Frame Relay) 
       11     IPX 
       12     Appletalk 
       13     Decnet IV 
       14     Banyan Vines 
       15     E.164 with NSAP format subaddress 


Does this mean that the value is addressing dependent, and not media
dependent ! 
Inputs appreciated? 

Madhvi 




From owner-l2tp@ipsec.org  Thu Apr 20 17:57:10 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21968
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 17:57:09 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA02320; Thu, 20 Apr 2000 13:49:43 -0700 (PDT)
Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA02316 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 13:48:35 -0700 (PDT)
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.22 2000/04/06 17:58:51 dmccart Exp $) with SMTP id UAA07166;
	Thu, 20 Apr 2000 20:48:56 GMT
Received: from fmsmsx27.FM.INTEL.COM ([132.233.48.27]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Thu, 20 Apr 2000 20:48:10 0000 (GMT)
Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <JF5V3D57>; Thu, 20 Apr 2000 13:48:06 -0700
Message-ID: <392A357CE6FFD111AC3E00A0C99848B003694CC5@hdsmsx31.hd.intel.com>
From: "Shriver, John" <john.shriver@intel.com>
To: "'Verma, Rohit (US - Chicago)'" <rverma@dc.com>,
        "Shriver, John"
	 <john.shriver@intel.com>, gwz@cisco.com,
        Madhvi Verma
	 <Madhvi_Verma@mw.3com.com>, l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM
Date: Thu, 20 Apr 2000 13:48:02 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

The medium is inherent in the Tunnel-Server-Endpoint.  That is a "name" that
encodes a interface and medium.  So the tunnel initiatior must have a
mapping from that name to something it understands.
 
What are we going to do for change control if we make an attribute that
includes Frame Relay and ATM when someone wants to add a new interface, say
G.shdsl?  It's endless.
 
Plus, knowing the medium still tells you absolutely NOTHING when you have
two interfaces of the same medium.  It adds no value above
Tunnel-Server-Endpoint.

-----Original Message-----
From: Verma, Rohit (US - Chicago) [mailto:rverma@dc.com]
Sent: Thursday, April 20, 2000 4:40 PM
To: Shriver, John; 'Verma, Rohit (US - Chicago)'; gwz@cisco.com; Madhvi
Verma; l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM



John I see your point however, we should definitely have an attribute that
can be used to specify what medium to use for the tunnel, because the TI can
not take that decision on its own.

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


-----Original Message----- 
From: Shriver, John [ mailto:john.shriver@intel.com
<mailto:john.shriver@intel.com> ] 
Sent: Thursday, April 20, 2000 2:57 PM 
To: 'Verma, Rohit (US - Chicago)'; gwz@cisco.com <mailto:gwz@cisco.com> ;
Madhvi Verma; 
l2tp@ipsec.org 
Subject: RE: Tunnel-Medium-Type value for FR and ATM 


As a co-author of the RFC (and author of the text in question), note that 
when Tunel-Medium-Type isn't IPv4 or IPv6, Tunnel-Client-Endpoint and 
Tunnel-Server-Endpoint are string names.  Freeform.  Not structured 
according to any rule based on the value of Tunnel-Medium-Type.  Note that 
Tunnel-Client-Endpoint can be an address, or an interface, as necessary. 
  
These strings are tags that refer to some part of the tunnel initiator's 
configuration database, which indicates the interface to be used and the 
endpoint theron.  It's done this way because there is no IETF standard 
syntax for naming interfaces.  
  
Yes, this does mean that you have to coordinate the configuration of the 
RADIUS server and the RADIUS client.  But by making it be this way, you can 
serve three different brands of RADIUS clients with one RADIUS server.  If 
the Ascend RADIUS client wanted a Tunnel-Client-Endpoint in the format 
"FrameRelaySlot3:Port4", and the Cisco RADIUS client wanted "Frame Relay 
3/4", you would be screwed.  The RADIUS server could not provide an answer 
that was correct for both.  By making it clear that it must be a tag 
indendpendent from the configuration of any particular product, you're not 
screwed in this case. 
  
I put this in because when we were Shiva, we had to add mappings to map our 
configuration to Ascend syntax for some of their proprietary attributes that

we implemented.  I wanted this standard to be vendor-neutral, and this was 
the simplest way to do that. 
  
 -----Original Message----- 
From: Verma, Rohit (US - Chicago) [ mailto:rverma@dc.com
<mailto:rverma@dc.com> ] 
Sent: Thursday, April 20, 2000 12:01 AM 
To: gwz@cisco.com; Madhvi Verma; l2tp@ipsec.org 
Subject: RE: Tunnel-Medium-Type value for FR and ATM 



Please see comments below. 
  
Regards 

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

-----Original Message----- 
From: Glen Zorn [ mailto:gwz@cisco.com <mailto:gwz@cisco.com> ] 
Sent: Wednesday, April 19, 2000 8:30 PM 
To: Verma, Rohit (US - Chicago); Madhvi Verma; l2tp@ipsec.org 
Subject: RE: Tunnel-Medium-Type value for FR and ATM 





The mediuam-type field is a guideline to the Tunnel Initiator what to expect

in the Tunnel Endpoint Address field. 
I do agree with you that it does not clearly capture the medium (For 
Example: E.164 is the addressing standard and it does not specify (SMDS, FR 
or ATM). 

Is it really necessary to do so, though?  If so, why? 
[Rohit Verma] 

Yes, it is important for tunnel initiators (TI) that support both ATM and FR

type interfaces. When a TI receives a RADIUS accept with tunne type set to 
L2TP and the medium type to an E.164 address, it needs to figure out what 
interface (FR or ATM) to use for the tunnel. 

Pardon my ignorance but I am not sure if E.164 address on its own can be 
used to do that distinction. Can anybody confirm that ? 

May be we need to add a more specific value to the set of AVPs retrieved 
from RADIUS. 

Regards 

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


-----Original Message----- 
From: Madhvi Verma [ mailto:Madhvi_Verma@mw.3com.com
<mailto:Madhvi_Verma@mw.3com.com>  
< mailto:Madhvi_Verma@mw.3com.com <mailto:Madhvi_Verma@mw.3com.com> > ] 
Sent: Wednesday, April 19, 2000 1:45 PM 
To: l2tp@ipsec.org 
Subject: Tunnel-Medium-Type value for FR and ATM 




Hi, 
What do you use as the tunnel-medium-type (RADIUS attribute :65) value for 
the 
following media? 
FR: 
AAL5: 

The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following 
address 
values : 
       1      IPv4 (IP version 4) 
       2      IPv6 (IP version 6) 
       3      NSAP 
       4      HDLC (8-bit multidrop) 
       5      BBN 1822 
       6      802 (includes all 802 media plus Ethernet "canonical format") 
       7      E.163 (POTS) 
       8      E.164 (SMDS, Frame Relay, ATM) 
       9      F.69 (Telex) 
       10     X.121 (X.25, Frame Relay) 
       11     IPX 
       12     Appletalk 
       13     Decnet IV 
       14     Banyan Vines 
       15     E.164 with NSAP format subaddress 


Does this mean that the value is addressing dependent, and not media 
dependent ! 
Inputs appreciated? 

Madhvi 




From owner-l2tp@ipsec.org  Thu Apr 20 18:03:56 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22073
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 18:03:56 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA02307; Thu, 20 Apr 2000 13:44:39 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id NAA02303 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 13:42:20 -0700 (PDT)
Received: by ans2-pub.dttus.com id PAA08978
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Thu, 20 Apr 2000 15:42:19 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Thu, 20 Apr 2000 15:42:19 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Thu, 20 Apr 2000 15:42:19 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E6564DFCD4@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: "Shriver, John" <john.shriver@intel.com>,
        "'Verma, Rohit (US - Chicago)'" <rverma@dc.com>, gwz@cisco.com,
        Madhvi Verma <Madhvi_Verma@mw.3com.com>, l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM
Date: Thu, 20 Apr 2000 15:39:59 -0500
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFAB08.96139BBE"
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_01BFAB08.96139BBE
Content-Type: text/plain;
	charset="iso-8859-1"

John I see your point however, we should definitely have an attribute that
can be used to specify what medium to use for the tunnel, because the TI can
not take that decision on its own.

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


-----Original Message-----
From: Shriver, John [mailto:john.shriver@intel.com]
Sent: Thursday, April 20, 2000 2:57 PM
To: 'Verma, Rohit (US - Chicago)'; gwz@cisco.com; Madhvi Verma;
l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM


As a co-author of the RFC (and author of the text in question), note that
when Tunel-Medium-Type isn't IPv4 or IPv6, Tunnel-Client-Endpoint and
Tunnel-Server-Endpoint are string names.  Freeform.  Not structured
according to any rule based on the value of Tunnel-Medium-Type.  Note that
Tunnel-Client-Endpoint can be an address, or an interface, as necessary.
 
These strings are tags that refer to some part of the tunnel initiator's
configuration database, which indicates the interface to be used and the
endpoint theron.  It's done this way because there is no IETF standard
syntax for naming interfaces.  
 
Yes, this does mean that you have to coordinate the configuration of the
RADIUS server and the RADIUS client.  But by making it be this way, you can
serve three different brands of RADIUS clients with one RADIUS server.  If
the Ascend RADIUS client wanted a Tunnel-Client-Endpoint in the format
"FrameRelaySlot3:Port4", and the Cisco RADIUS client wanted "Frame Relay
3/4", you would be screwed.  The RADIUS server could not provide an answer
that was correct for both.  By making it clear that it must be a tag
indendpendent from the configuration of any particular product, you're not
screwed in this case.
 
I put this in because when we were Shiva, we had to add mappings to map our
configuration to Ascend syntax for some of their proprietary attributes that
we implemented.  I wanted this standard to be vendor-neutral, and this was
the simplest way to do that.
 
 -----Original Message-----
From: Verma, Rohit (US - Chicago) [mailto:rverma@dc.com]
Sent: Thursday, April 20, 2000 12:01 AM
To: gwz@cisco.com; Madhvi Verma; l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM



Please see comments below.
 
Regards

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

-----Original Message-----
From: Glen Zorn [mailto:gwz@cisco.com]
Sent: Wednesday, April 19, 2000 8:30 PM
To: Verma, Rohit (US - Chicago); Madhvi Verma; l2tp@ipsec.org
Subject: RE: Tunnel-Medium-Type value for FR and ATM





The mediuam-type field is a guideline to the Tunnel Initiator what to expect
in the Tunnel Endpoint Address field. 
I do agree with you that it does not clearly capture the medium (For
Example: E.164 is the addressing standard and it does not specify (SMDS, FR
or ATM). 

Is it really necessary to do so, though?  If so, why? 
[Rohit Verma] 

Yes, it is important for tunnel initiators (TI) that support both ATM and FR
type interfaces. When a TI receives a RADIUS accept with tunne type set to
L2TP and the medium type to an E.164 address, it needs to figure out what
interface (FR or ATM) to use for the tunnel. 

Pardon my ignorance but I am not sure if E.164 address on its own can be
used to do that distinction. Can anybody confirm that ?

May be we need to add a more specific value to the set of AVPs retrieved
from RADIUS. 

Regards 

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


-----Original Message----- 
From: Madhvi Verma [ mailto:Madhvi_Verma@mw.3com.com
<mailto:Madhvi_Verma@mw.3com.com> ] 
Sent: Wednesday, April 19, 2000 1:45 PM 
To: l2tp@ipsec.org 
Subject: Tunnel-Medium-Type value for FR and ATM 




Hi, 
What do you use as the tunnel-medium-type (RADIUS attribute :65) value for
the 
following media? 
FR: 
AAL5: 

The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following
address 
values : 
       1      IPv4 (IP version 4) 
       2      IPv6 (IP version 6) 
       3      NSAP 
       4      HDLC (8-bit multidrop) 
       5      BBN 1822 
       6      802 (includes all 802 media plus Ethernet "canonical format") 
       7      E.163 (POTS) 
       8      E.164 (SMDS, Frame Relay, ATM) 
       9      F.69 (Telex) 
       10     X.121 (X.25, Frame Relay) 
       11     IPX 
       12     Appletalk 
       13     Decnet IV 
       14     Banyan Vines 
       15     E.164 with NSAP format subaddress 


Does this mean that the value is addressing dependent, and not media
dependent ! 
Inputs appreciated? 

Madhvi 


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Tunnel-Medium-Type value for FR and ATM</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>John I see your point however, we should definitely =
have an attribute that can be used to specify what medium to use for =
the tunnel, because the TI can not take that decision on its =
own.</FONT></P>

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Shriver, John [<A =
HREF=3D"mailto:john.shriver@intel.com">mailto:john.shriver@intel.com</A>=
]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, April 20, 2000 2:57 PM</FONT>
<BR><FONT SIZE=3D2>To: 'Verma, Rohit (US - Chicago)'; gwz@cisco.com; =
Madhvi Verma;</FONT>
<BR><FONT SIZE=3D2>l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: Tunnel-Medium-Type value for FR and =
ATM</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>As a co-author of the RFC (and author of the text in =
question), note that</FONT>
<BR><FONT SIZE=3D2>when Tunel-Medium-Type isn't IPv4 or IPv6, =
Tunnel-Client-Endpoint and</FONT>
<BR><FONT SIZE=3D2>Tunnel-Server-Endpoint are string names.&nbsp; =
Freeform.&nbsp; Not structured</FONT>
<BR><FONT SIZE=3D2>according to any rule based on the value of =
Tunnel-Medium-Type.&nbsp; Note that</FONT>
<BR><FONT SIZE=3D2>Tunnel-Client-Endpoint can be an address, or an =
interface, as necessary.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>These strings are tags that refer to some part of =
the tunnel initiator's</FONT>
<BR><FONT SIZE=3D2>configuration database, which indicates the =
interface to be used and the</FONT>
<BR><FONT SIZE=3D2>endpoint theron.&nbsp; It's done this way because =
there is no IETF standard</FONT>
<BR><FONT SIZE=3D2>syntax for naming interfaces.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Yes, this does mean that you have to coordinate the =
configuration of the</FONT>
<BR><FONT SIZE=3D2>RADIUS server and the RADIUS client.&nbsp; But by =
making it be this way, you can</FONT>
<BR><FONT SIZE=3D2>serve three different brands of RADIUS clients with =
one RADIUS server.&nbsp; If</FONT>
<BR><FONT SIZE=3D2>the Ascend RADIUS client wanted a =
Tunnel-Client-Endpoint in the format</FONT>
<BR><FONT SIZE=3D2>&quot;FrameRelaySlot3:Port4&quot;, and the Cisco =
RADIUS client wanted &quot;Frame Relay</FONT>
<BR><FONT SIZE=3D2>3/4&quot;, you would be screwed.&nbsp; The RADIUS =
server could not provide an answer</FONT>
<BR><FONT SIZE=3D2>that was correct for both.&nbsp; By making it clear =
that it must be a tag</FONT>
<BR><FONT SIZE=3D2>indendpendent from the configuration of any =
particular product, you're not</FONT>
<BR><FONT SIZE=3D2>screwed in this case.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>I put this in because when we were Shiva, we had to =
add mappings to map our</FONT>
<BR><FONT SIZE=3D2>configuration to Ascend syntax for some of their =
proprietary attributes that</FONT>
<BR><FONT SIZE=3D2>we implemented.&nbsp; I wanted this standard to be =
vendor-neutral, and this was</FONT>
<BR><FONT SIZE=3D2>the simplest way to do that.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&nbsp;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Verma, Rohit (US - Chicago) [<A =
HREF=3D"mailto:rverma@dc.com">mailto:rverma@dc.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, April 20, 2000 12:01 AM</FONT>
<BR><FONT SIZE=3D2>To: gwz@cisco.com; Madhvi Verma; =
l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: Tunnel-Medium-Type value for FR and ATM<=
/FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Please see comments below.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Regards</FONT>
</P>

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Glen Zorn [<A =
HREF=3D"mailto:gwz@cisco.com">mailto:gwz@cisco.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 19, 2000 8:30 PM</FONT>
<BR><FONT SIZE=3D2>To: Verma, Rohit (US - Chicago); Madhvi Verma; =
l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: Tunnel-Medium-Type value for FR and =
ATM</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>The mediuam-type field is a guideline to the Tunnel =
Initiator what to expect</FONT>
<BR><FONT SIZE=3D2>in the Tunnel Endpoint Address field. </FONT>
<BR><FONT SIZE=3D2>I do agree with you that it does not clearly capture =
the medium (For</FONT>
<BR><FONT SIZE=3D2>Example: E.164 is the addressing standard and it =
does not specify (SMDS, FR</FONT>
<BR><FONT SIZE=3D2>or ATM). </FONT>
</P>

<P><FONT SIZE=3D2>Is it really necessary to do so, though?&nbsp; If so, =
why? </FONT>
<BR><FONT SIZE=3D2>[Rohit Verma] </FONT>
</P>

<P><FONT SIZE=3D2>Yes, it is important for tunnel initiators (TI) that =
support both ATM and FR</FONT>
<BR><FONT SIZE=3D2>type interfaces. When a TI receives a RADIUS accept =
with tunne type set to</FONT>
<BR><FONT SIZE=3D2>L2TP and the medium type to an E.164 address, it =
needs to figure out what</FONT>
<BR><FONT SIZE=3D2>interface (FR or ATM) to use for the tunnel. </FONT>
</P>

<P><FONT SIZE=3D2>Pardon my ignorance but I am not sure if E.164 =
address on its own can be</FONT>
<BR><FONT SIZE=3D2>used to do that distinction. Can anybody confirm =
that ?</FONT>
</P>

<P><FONT SIZE=3D2>May be we need to add a more specific value to the =
set of AVPs retrieved</FONT>
<BR><FONT SIZE=3D2>from RADIUS. </FONT>
</P>

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

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

<P><FONT SIZE=3D2>-----Original Message----- </FONT>
<BR><FONT SIZE=3D2>From: Madhvi Verma [ <A =
HREF=3D"mailto:Madhvi_Verma@mw.3com.com">mailto:Madhvi_Verma@mw.3com.com=
</A></FONT>
<BR><FONT SIZE=3D2>&lt;<A =
HREF=3D"mailto:Madhvi_Verma@mw.3com.com">mailto:Madhvi_Verma@mw.3com.com=
</A>&gt; ] </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 19, 2000 1:45 PM </FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org </FONT>
<BR><FONT SIZE=3D2>Subject: Tunnel-Medium-Type value for FR and ATM =
</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi, </FONT>
<BR><FONT SIZE=3D2>What do you use as the tunnel-medium-type (RADIUS =
attribute :65) value for</FONT>
<BR><FONT SIZE=3D2>the </FONT>
<BR><FONT SIZE=3D2>following media? </FONT>
<BR><FONT SIZE=3D2>FR: </FONT>
<BR><FONT SIZE=3D2>AAL5: </FONT>
</P>

<P><FONT SIZE=3D2>The draft =
&quot;draft-ietf-radius-tunnel-auth-09.txt&quot; mentions the =
following</FONT>
<BR><FONT SIZE=3D2>address </FONT>
<BR><FONT SIZE=3D2>values : </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv4 (IP version 4) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6 (IP version 6) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NSAP </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HDLC (8-bit multidrop) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BBN 1822 </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 802 (includes all 802 media plus =
Ethernet &quot;canonical format&quot;) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; E.163 (POTS) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E.164 (SMDS, Frame Relay, ATM) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; F.69 (Telex) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
10&nbsp;&nbsp;&nbsp;&nbsp; X.121 (X.25, Frame Relay) </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
11&nbsp;&nbsp;&nbsp;&nbsp; IPX </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
12&nbsp;&nbsp;&nbsp;&nbsp; Appletalk </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
13&nbsp;&nbsp;&nbsp;&nbsp; Decnet IV </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
14&nbsp;&nbsp;&nbsp;&nbsp; Banyan Vines </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
15&nbsp;&nbsp;&nbsp;&nbsp; E.164 with NSAP format subaddress </FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Does this mean that the value is addressing =
dependent, and not media</FONT>
<BR><FONT SIZE=3D2>dependent ! </FONT>
<BR><FONT SIZE=3D2>Inputs appreciated? </FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01BFAB08.96139BBE--


From owner-l2tp@ipsec.org  Thu Apr 20 18:40:36 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22368
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 18:40:36 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id OAA02423; Thu, 20 Apr 2000 14:30:09 -0700 (PDT)
Received: from coredump.ae.usr.com (coredump.ae.usr.com [207.24.169.214]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA02416 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 14:29:57 -0700 (PDT)
Received: from otherland (IP-207-24-169-227.ae.usr.com [207.24.169.227])
	by coredump.ae.usr.com (8.9.2/8.9.2) with SMTP id QAA13562
	for <l2tp@ipsec.org>; Thu, 20 Apr 2000 16:29:55 -0500 (CDT)
From: "Mike Wronski" <mike@coredump.ae.usr.com>
To: <l2tp@ipsec.org>
Subject: Win2K as LNS w/o IPSEC
Date: Thu, 20 Apr 2000 16:29:52 -0500
Message-ID: <001101bfab0f$90a2a2e0$e3a918cf@otherland.mw.3com.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am looking for a firm answer on this question. My search on  M$'s
knowledgedbase has not given great results.

Can someone confirm or deny that Windows 2K can act as an LNS for L2TP and
NOT use IPSEC?  Everything I read states that Win2k does (L2TP)/IPSEC.

If this is possible, is there a pointer to the required configs on the win2k
side?

Thanks,
-M



From owner-l2tp@ipsec.org  Thu Apr 20 19:47:06 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23086
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 19:47:04 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id PAA02590; Thu, 20 Apr 2000 15:38:08 -0700 (PDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA02583 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 15:36:32 -0700 (PDT)
From: Peter_Rizk@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 PAA09311;
	Thu, 20 Apr 2000 15:36:31 -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 PAA19708;
	Thu, 20 Apr 2000 15:36:30 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568C7.007C1AA4 ; Thu, 20 Apr 2000 15:35:32 -0700
X-Lotus-FromDomain: 3COM
To: "Mike Wronski" <mike@coredump.ae.usr.com>
cc: l2tp@ipsec.org
Message-ID: <882568C7.007C1851.00@hqoutbound.ops.3com.com>
Date: Thu, 20 Apr 2000 15:35:57 -0700
Subject: Re: Win2K as LNS w/o IPSEC
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=RB4knPRxCr2dQjdCCBZCxgLP8CSd1PpZQIETixVLmRuiCuq1hyDZ5ygj"
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk

--0__=RB4knPRxCr2dQjdCCBZCxgLP8CSd1PpZQIETixVLmRuiCuq1hyDZ5ygj
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable




Hi Everyone,

I've been working with L2TP and L2TP over IPsec (or should I say IPsec =
over
L2TP)  with Win2K for a while and here is how you do it....

There are two ways to get L2TP to work under Win2K.
1) L2TP without IPsec (no security)
2) L2TP with IPsec (provides good security). L2TP with IPsec requires t=
he use of
digital certificates. So, you need to configure the remote L2TP VPN use=
r to
request and install a certificate before an L2TP/IPsec tunnel can be
established.

L2TP without IPsec:
By default, L2TP requires IPsec which requires the use of certificates =
for
authentication. To make L2TP work without IPsec, you need to disable IP=
sec on
BOTH the L2TP client and the L2TP server. To disable IPsec, you need to=
 edit the
registry. We need to add an entry to the registry called ProhitbitIpSec=
 and set
its value to 1. So, do the following:
a- Click on Start--> Run and type "regedt32" and click OK. This will la=
unch the
registry editor.
b- Goto to HKEY_LOCAL_MACHINE - System - CurrentControl Set - Service -=
 RasMan -
Parameters
c- Click on Edit - Add Value... and type "ProhibitIpSec" EXACTLY LIKE T=
HAT...
(ProhibitIpSec)
d- Set the Data Type to REG_DWORD, then click OK
e- Type 1 and click OK.
Now, you should see the following entry to the right hand side: Prohibi=
tIpSec:
REG_DWORD: 0x1

YOU MUST REBOOT THE MACHINE FOR THIS ENTRY TO TAKE EFFECT...So, reboot =
the
machine now.

After you do this on BOTH the client and server, the client will then b=
e able to
establish an L2TP tunnel with the VPN server WITHOUT IPsec.


L2TP with IPsec:
To get L2TP to work with IPsec, we need to use certificates.You need to=
 request
a certificate from a CA and install that certificate. In this example, =
I am
going to cover the Win2K CA.... All the work that we will do here will =
be mainly
done on the client. I assume you already have a Win2K CA up and running=
....There
are several things that needs to be done of the client to get L2TP with=
 IPsec
working. We need to launch MMC add the certificate services, then reque=
st a
certificate and install a certificate (after it has been approved) then=

establish the L2TP-IPsec tunnel. Note that our server has both the L2TP=
 VPN
sever as well as CA (certificate authority) and IIS (which is needed fo=
r the CA
to work). So, do the following:
1) On the client PC, click on Start--> Run and type MMC, then click OK.=
 This
will launch the Microsoft Management Console (MMC).
2) Click on Console --> Add/Remove Snap-in..., then click on Add... and=
 select
"Certificates" and click Add, select "Computer account" and click Next =
and click
Finish, click Close and click OK.
3) Double click on "Certificates (Local computer)" and you will see six=
 folders
starting with "Personal" and ending with "SPC". The two folders that we=
 care
about are "Personal" and "Trusted Root Certification Authorities".  If =
you look
inside the Personal folder you will see that it is empty... That we are=
 going to
do is request a certificate from the CA and install the certificate. On=
ce the
certificate gets installed it will appear in the Personal folders, AND =
the root
CA certificate will be installed in the "Trusted Root Certification Aut=
horities"
AUTOMATICALLY!
4) Let's save our setup for now. Click on Console---> Save As... Type i=
n
"Policy1" and save it on the desktop for easy access.

5) Now we are ready to request a certificate from the CA. We can do the=

certificate request through a Web browser. So, launch Internet Explore.=
 If you
are launch Internet Explorer for the first time, then do the following =
steps,
otherwise, got step 6.
     a) When you launch it for the firs time, you will see "Welcome to =
the
     Internet Connection Wizard", select the "I want to setup my Intern=
et
     connection manually, or I want to connect through a local area net=
work
     (LAN)." and click Next.
     b) Select "I connect through a local area network (LAN)" and click=
 on Next.
     c) Uncheck the "Automatic discovery of proxy server (recommended)"=
 box
     (make it empty), then uncheck the "Manual Proxy Server" box (make =
it empty
     too) and click on Next.
     d) Select No and click Next.
     e) Click on Finish and Internet explorer will be automatically lau=
nched.

6) Type the URL of the certitifcate server ex: http://x.x.x.x/certsrv a=
nd hit
enter.
7) "Request a certificate" is selected by default (which is the action =
that we
want to take right now). Click Next.
8) Select "Advanced request" and click Next.
9) "Submit a certificate request to this CA using a form" is selected w=
hich is
what we want to do right now, so click Next.
10) In the Name field type in your name and leave the other fields blan=
k.
11) Under "Intended Purpose" click on "Client Authentication Certificat=
e" and
then select "IPsec Certificate"
12) Under Key Options: YOU MUST CHECK THE "Use local machine store" box=
. DON'T
LEAVE IT EMPTY.
13) Click Submit and your request will be sent to the CA for approval.

At this point, we need to go to the CA and approve this request. So go =
to the
VPN server and do the following:
1) Start --> Programs --> Administrative Tools --> Certification Author=
ity
2) Double click "Certification Authority (Local)", then double click th=
e name of
the CA (which in our case we called it 3Com). After that you will see f=
our
folders starting with "Revoked Certificates" and ending with "Failed
Certificates".
3) Click on the "Pending Requests" folder and to the right hand side yo=
u will
see the certificate request that we sent towards the end of step 13 ear=
lier...
4) Select that certificate, and right click on it, select ALL Tasks, th=
en select
Issue. Now, this certificate request has been approved and the certific=
ate has
moved to the "Issued Certificate" folder.
5) That's all what need to be done at the server... now, we need to go =
back to
the client and install the certificate.

Now, at the client do the following:
14) We are now at step 14 (continuation of step 13 earlier). Point Inte=
rnet
Explorer to the following URL  http://x.x.x.x/certsrv
15) Select "Check on pending certificate" and click Next...
16) You will now see you IPsec certificate, click on Next.
17) Now, you are ready to install the certificate. Click on "Install th=
is
certificate" and in few seconds your IPsec certificate will be installe=
d on your
system. That certificate will be located in the "Personal" folder.
18) Goto the MMC program where we saved our configuration in Policy1 an=
d look
inside the "Personal" folder and you will see the IPsec certificate tha=
t you
have just downloaded. If you can't see it, simply right click on "Perso=
nal" and
select Refresh, then double click on Personal you should then see a fol=
der
called Certificates. Double click on that, and you will see your IPsec
certificate. Double click on the certificate and you will see various i=
nfo about
the certificate.
19) Goto the "Trusted Root Certification Authorities", and right click =
on it,
then select Refresh. Double click on the "Trusted Root Certification
Authorities", then double click on "Certificates" and locate the certif=
icate for
the CA that issued you the certificate. It must be there....

There is one more thing left to do before the client can establish an L=
2TP IPsec
tunnel with the VPN Server.
We MUST set the ProhibitIpSec entry in the registry to 0 (Zero). So set=
 the
ProhibitIpSec to 0 on BOTH the client AND server.

Very important: The VPN server MUST also have an IPsec certificate for
L2TP/IPsec to work. That means, the VPN server must also request and in=
stall an
IPsec certificate so that the L2TP client can connect to the L2TP serve=
r and use
IPsec for security. So, you pretty much have to repeat steps 1 - 19 on =
the VPN
server...

After all of the above is taken care of, you can now have the client es=
tablish
an L2TP tunnel with the VPN server and automatically all traffic will b=
e
protected via Ipsec. By default you get ESP DES. If you apply the ?High=

Encryption Pack?, then you get ESP 3DES.

Hope this will fix your problem...

Regards,
Peter





"Mike Wronski" <mike@coredump.ae.usr.com> on 04/20/2000 02:29:52 PM

Sent by:  "Mike Wronski" <mike@coredump.ae.usr.com>


To:   l2tp@ipsec.org
cc:    (Peter Rizk/HQ/3Com)
Subject:  Win2K as LNS w/o IPSEC


=

--0__=RB4knPRxCr2dQjdCCBZCxgLP8CSd1PpZQIETixVLmRuiCuq1hyDZ5ygj
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline


I am looking for a firm answer on this question. My search on  M$'s
knowledgedbase has not given great results.

Can someone confirm or deny that Windows 2K can act as an LNS for L2TP and
NOT use IPSEC?  Everything I read states that Win2k does (L2TP)/IPSEC.

If this is possible, is there a pointer to the required configs on the win2k
side?

Thanks,
-M




--0__=RB4knPRxCr2dQjdCCBZCxgLP8CSd1PpZQIETixVLmRuiCuq1hyDZ5ygj--



From owner-l2tp@ipsec.org  Thu Apr 20 23:13:16 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26562
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 23:13:15 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id TAA03016; Thu, 20 Apr 2000 19:20:34 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA03012 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 19:20:04 -0700 (PDT)
Received: from cisco.com (rtp-dial-2-218.cisco.com [10.83.96.218]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id TAA09519; Thu, 20 Apr 2000 19:18:59 -0700 (PDT)
Message-ID: <38FFBA91.7E2E8115@cisco.com>
Date: Thu, 20 Apr 2000 22:18:57 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Bill Palter <palter@zev.net>
CC: Evan Caves <evan.caves@ericsson.com>, l2tp@ipsec.org
Subject: Re: IANA Considerations
References: <200004201659.JAA08041@zev.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Bill Palter wrote:
> 
> > Would it make it any easier if we defined an 'experimental' vendor ID
> > which IANA can allocate AVP types/values out of. The number space could
> > mirror the IETF number space (may be hard to manage) so that if adopted
> > the type/values remain the same, just the vendor ID changes.
> >
> > just a thought,
> 
>   I like it......Wonder what we need to do to get a vendor id allocated..

I doubt the ADs would go for this. Pretty soon, every working group will
want their own Vendor ID. Not a bad idea per se, but additional
adminstrative overhead is often resisted...

However, if we wanted to buck the system, there are a number of
companies that could donate their SMI Enterprise code to us :-) 

- Mark

> >
> > evan
> > -
> >
> > "W. Mark Townsley" wrote:
> > >
> > > I initiated discussion with our ADs recently regarding the IANA
> > > considerations in RFC 2661.
> > >
> > > There are two decisions we face, and have not reached clear agreement.
> > > I'd like to get a feel of the WGs opinion here.
> > >
> > > Issue #1
> > >
> > > Currently, a new IETF AVP value may only be requested for RFCs. That is,
> > > after last call and approval by the IESG. In DC we discussed (and agreed
> > > upon) the value in obtaining numbers from IANA here at an earlier stage
> > > so as to reduce the risk of ultimately maintaining two values (the IANA
> > > number and whatever vendor-specific number that was originally
> > > documented).
> > >
> > > We have three choices.
> > >
> > > A. Stay where we are, and request IANA numbers only after the RFC
> > > publication is imminent.
> > > B. Write a short RFC modifying the policy.
> > > C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
> > > until it is published before it can be followed.
> > >
> > > The new policy might be that a person (such as the WG chair) is
> > > appointed to determine when the WG has sufficient consensus to request a
> > > value. This would typically be at or near the point of last call,
> > > depending on implementation demand and clarity of consensus.
> > >
> > > Issue #2
> > >
> > > This is simply where to begin handing out new values for AVPs. The
> > > highest value now is 39. We have two choices.
> > >
> > > A. Begin at 40
> > > B. Begin at some other value slightly higher, say, 50, so that *if* we
> > > end up adding an AVP or two to the base spec as it advances, we can
> > > remain contiguous in the base spec.
> > >
> > > Opinions appreciated. Thanks,
> > >
> > > - Mark
> --
> Bill Palter (Palter@zev.net)


From owner-l2tp@ipsec.org  Thu Apr 20 23:20:39 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26610
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 23:20:38 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id TAA03033; Thu, 20 Apr 2000 19:26:52 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA03029 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 19:26:37 -0700 (PDT)
Received: from cisco.com (rtp-dial-2-218.cisco.com [10.83.96.218]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id TAA09614; Thu, 20 Apr 2000 19:25:18 -0700 (PDT)
Message-ID: <38FFBC0C.CDFA86C3@cisco.com>
Date: Thu, 20 Apr 2000 22:25:16 -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: "pcalhoun@eng.sun.com" <pcalhoun@ha1mpk-mail.Eng.Sun.COM>
CC: Bill Palter <palter@zev.net>, Evan Caves <evan.caves@ericsson.com>,
        l2tp@ipsec.org
Subject: Re: IANA Considerations
References: <Roam.SIMC.2.0.6.956251472.4832.pcalhoun@ha1mpk-mail>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"pcalhoun@eng.sun.com" wrote:
> 
> hmmm... I'm not sure that this is really the direction that we want. I would
> actually ask that we update RFC2661, and state that the numbers are assigned
> from a Designated Expert, which is frequently done.
> 
> The con: We have to reset the clock before moving to draft standard.

Which clock? We have edits to do anyway and the draft standard goal is
still months away. Are you suggesting that such a change would require
recycling at PS?

> 
> The pro: Number allocation actually works

A nice upshot.

> 
> PatC


From owner-l2tp@ipsec.org  Thu Apr 20 23:32:03 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27048
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 23:32:02 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id TAA03044; Thu, 20 Apr 2000 19:27:20 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA03034 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 19:26:56 -0700 (PDT)
Received: from cisco.com (rtp-dial-2-218.cisco.com [10.83.96.218]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id TAA09622; Thu, 20 Apr 2000 19:26:23 -0700 (PDT)
Message-ID: <38FFBC4E.67DBAF5@cisco.com>
Date: Thu, 20 Apr 2000 22:26:22 -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: gwz@cisco.com
CC: l2tp@ipsec.org
Subject: Re: IANA Considerations
References: <NDBBIHMPILAAGDHPCIOPCELICCAA.gwz@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Glen Zorn wrote:
> > Issue #2
> >
> > This is simply where to begin handing out new values for AVPs. The
> > highest value now is 39. We have two choices.
> >
> > A. Begin at 40
> > B. Begin at some other value slightly higher, say, 50, so that *if* we
> > end up adding an AVP or two to the base spec as it advances, we can
> > remain contiguous in the base spec.
> 
> Semi-contiguous, unless all 10 numbers are used.  If none are used, then
> there will be a hole; how big a hole is acceptable seems to be highly
> implementation-dependent, to the point of being a matter of taste.

Precisely what I am trying to get a handle on. I know my taste, but
would like to know the WG's taste.

- Mark

> 
> >
> > Opinions appreciated. Thanks,
> >
> > - Mark
> >
> >


From owner-l2tp@ipsec.org  Thu Apr 20 23:49:03 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27199
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 23:49:02 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id TAA03062; Thu, 20 Apr 2000 19:33:30 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA03056 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 19:32:23 -0700 (PDT)
Received: from cisco.com (rtp-dial-2-218.cisco.com [10.83.96.218]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id TAA09775; Thu, 20 Apr 2000 19:31:16 -0700 (PDT)
Message-ID: <38FFBD72.9DDA2893@cisco.com>
Date: Thu, 20 Apr 2000 22:31:14 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Shriver, John" <john.shriver@intel.com>
CC: "'Verma, Rohit (US - Chicago)'" <rverma@dc.com>, gwz@cisco.com,
        Madhvi Verma <Madhvi_Verma@mw.3com.com>, l2tp@ipsec.org
Subject: Re: Tunnel-Medium-Type value for FR and ATM
References: <392A357CE6FFD111AC3E00A0C99848B003694CC5@hdsmsx31.hd.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


This rings of the Sub-Address argument of long ago. I am inclined to
agree with John here that freeform strings are best when there is no
clear IETF addressing standard.

"Shriver, John" wrote:
> 
> The medium is inherent in the Tunnel-Server-Endpoint.  That is a "name" that
> encodes a interface and medium.  So the tunnel initiatior must have a
> mapping from that name to something it understands.
> 
> What are we going to do for change control if we make an attribute that
> includes Frame Relay and ATM when someone wants to add a new interface, say
> G.shdsl?  It's endless.
> 
> Plus, knowing the medium still tells you absolutely NOTHING when you have
> two interfaces of the same medium.  It adds no value above
> Tunnel-Server-Endpoint.
> 
> -----Original Message-----
> From: Verma, Rohit (US - Chicago) [mailto:rverma@dc.com]
> Sent: Thursday, April 20, 2000 4:40 PM
> To: Shriver, John; 'Verma, Rohit (US - Chicago)'; gwz@cisco.com; Madhvi
> Verma; l2tp@ipsec.org
> Subject: RE: Tunnel-Medium-Type value for FR and ATM
> 
> John I see your point however, we should definitely have an attribute that
> can be used to specify what medium to use for the tunnel, because the TI can
> not take that decision on its own.
> 
> Regards
> Rohit Verma
> Deloitte Consulting
> 180, N. Stetson Avenue
> Chicago, Illinois 60601
> Phone:312-374-2475
> 
> -----Original Message-----
> From: Shriver, John [ mailto:john.shriver@intel.com
> <mailto:john.shriver@intel.com> ]
> Sent: Thursday, April 20, 2000 2:57 PM
> To: 'Verma, Rohit (US - Chicago)'; gwz@cisco.com <mailto:gwz@cisco.com> ;
> Madhvi Verma;
> l2tp@ipsec.org
> Subject: RE: Tunnel-Medium-Type value for FR and ATM
> 
> As a co-author of the RFC (and author of the text in question), note that
> when Tunel-Medium-Type isn't IPv4 or IPv6, Tunnel-Client-Endpoint and
> Tunnel-Server-Endpoint are string names.  Freeform.  Not structured
> according to any rule based on the value of Tunnel-Medium-Type.  Note that
> Tunnel-Client-Endpoint can be an address, or an interface, as necessary.
> 
> These strings are tags that refer to some part of the tunnel initiator's
> configuration database, which indicates the interface to be used and the
> endpoint theron.  It's done this way because there is no IETF standard
> syntax for naming interfaces.
> 
> Yes, this does mean that you have to coordinate the configuration of the
> RADIUS server and the RADIUS client.  But by making it be this way, you can
> serve three different brands of RADIUS clients with one RADIUS server.  If
> the Ascend RADIUS client wanted a Tunnel-Client-Endpoint in the format
> "FrameRelaySlot3:Port4", and the Cisco RADIUS client wanted "Frame Relay
> 3/4", you would be screwed.  The RADIUS server could not provide an answer
> that was correct for both.  By making it clear that it must be a tag
> indendpendent from the configuration of any particular product, you're not
> screwed in this case.
> 
> I put this in because when we were Shiva, we had to add mappings to map our
> configuration to Ascend syntax for some of their proprietary attributes that
> 
> we implemented.  I wanted this standard to be vendor-neutral, and this was
> the simplest way to do that.
> 
>  -----Original Message-----
> From: Verma, Rohit (US - Chicago) [ mailto:rverma@dc.com
> <mailto:rverma@dc.com> ]
> Sent: Thursday, April 20, 2000 12:01 AM
> To: gwz@cisco.com; Madhvi Verma; l2tp@ipsec.org
> Subject: RE: Tunnel-Medium-Type value for FR and ATM
> 
> Please see comments below.
> 
> Regards
> 
> Rohit Verma
> Deloitte Consulting
> 180, N. Stetson Avenue
> Chicago, Illinois 60601
> Phone:312-374-2475
> 
> -----Original Message-----
> From: Glen Zorn [ mailto:gwz@cisco.com <mailto:gwz@cisco.com> ]
> Sent: Wednesday, April 19, 2000 8:30 PM
> To: Verma, Rohit (US - Chicago); Madhvi Verma; l2tp@ipsec.org
> Subject: RE: Tunnel-Medium-Type value for FR and ATM
> 
> The mediuam-type field is a guideline to the Tunnel Initiator what to expect
> 
> in the Tunnel Endpoint Address field.
> I do agree with you that it does not clearly capture the medium (For
> Example: E.164 is the addressing standard and it does not specify (SMDS, FR
> or ATM).
> 
> Is it really necessary to do so, though?  If so, why?
> [Rohit Verma]
> 
> Yes, it is important for tunnel initiators (TI) that support both ATM and FR
> 
> type interfaces. When a TI receives a RADIUS accept with tunne type set to
> L2TP and the medium type to an E.164 address, it needs to figure out what
> interface (FR or ATM) to use for the tunnel.
> 
> Pardon my ignorance but I am not sure if E.164 address on its own can be
> used to do that distinction. Can anybody confirm that ?
> 
> May be we need to add a more specific value to the set of AVPs retrieved
> from RADIUS.
> 
> Regards
> 
> Rohit Verma
> Deloitte Consulting
> 180, N. Stetson Avenue
> Chicago, Illinois 60601
> Phone:312-374-2475
> 
> -----Original Message-----
> From: Madhvi Verma [ mailto:Madhvi_Verma@mw.3com.com
> <mailto:Madhvi_Verma@mw.3com.com>
> < mailto:Madhvi_Verma@mw.3com.com <mailto:Madhvi_Verma@mw.3com.com> > ]
> Sent: Wednesday, April 19, 2000 1:45 PM
> To: l2tp@ipsec.org
> Subject: Tunnel-Medium-Type value for FR and ATM
> 
> Hi,
> What do you use as the tunnel-medium-type (RADIUS attribute :65) value for
> the
> following media?
> FR:
> AAL5:
> 
> The draft "draft-ietf-radius-tunnel-auth-09.txt" mentions the following
> address
> values :
>        1      IPv4 (IP version 4)
>        2      IPv6 (IP version 6)
>        3      NSAP
>        4      HDLC (8-bit multidrop)
>        5      BBN 1822
>        6      802 (includes all 802 media plus Ethernet "canonical format")
>        7      E.163 (POTS)
>        8      E.164 (SMDS, Frame Relay, ATM)
>        9      F.69 (Telex)
>        10     X.121 (X.25, Frame Relay)
>        11     IPX
>        12     Appletalk
>        13     Decnet IV
>        14     Banyan Vines
>        15     E.164 with NSAP format subaddress
> 
> Does this mean that the value is addressing dependent, and not media
> dependent !
> Inputs appreciated?
> 
> Madhvi


From owner-l2tp@ipsec.org  Thu Apr 20 23:57:02 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27250
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Apr 2000 23:57:00 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id TAA03081; Thu, 20 Apr 2000 19:41:43 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA03077 for <l2tp@ipsec.org>; Thu, 20 Apr 2000 19:41:03 -0700 (PDT)
Received: from cisco.com (rtp-dial-2-218.cisco.com [10.83.96.218]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id TAA09874; Thu, 20 Apr 2000 19:40:30 -0700 (PDT)
Message-ID: <38FFBF9C.EBBBBB10@cisco.com>
Date: Thu, 20 Apr 2000 22:40:28 -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: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
CC: l2tp@ipsec.org
Subject: Re: IANA Considerations
References: <2F4A3F6B7BF5D3119E2500508B94E6564DFAFD@uscntnt405a.us.deloitte.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



> "Verma, Rohit (US - Chicago)" wrote:
> 
> For Issue #2:-
> We have 2 bytes available for the Attribute Type. Why don't we hand
> new AVP's with the precondition that the MSBit for the new AVPs must
> be 1.
> 
> New AVPs 0x80, 0x81 ....0xff
> Base Spec AVPs 0x01....0x7f
> 
> This precondition it will ensure continuity for the base spec to a
> large Attribute Type space.

Effectively defining a bit field that states "this is part of the base
spec" 

I think this adds unnecessary complexity. Takes a chunk out of the
number space for extensions as well. Adding values to the base spec
should be the exception, not the rule. If we are going to go nuts with
new values, we should separate these out in separate specs 'ala DHCP
anyway. I doubt this is the case.

> Also it will be easier for implementations to differentiate between
> base spec AVPs and new ones.

There is no real need for implementations to be able to do this though.
The only thing choice #2B is trying to do is protect against an RFC that
has a big gap in its list of values. Pros are (1) Readability, and (2)
no need to code around a gap for the base implementation. Cons are (1)
Some obvious confusion, (2) building in a small gap in the overall space
for perhaps no good reason.

> 
> Regards
> Rohit Verma
> Deloitte Consulting
> 180, N. Stetson Avenue
> Chicago, Illinois 60601
> Phone:312-374-2475
> 
> -----Original Message-----
> From: W. Mark Townsley [mailto:townsley@cisco.com]
> Sent: Wednesday, April 19, 2000 11:07 PM
> To: l2tp@ipsec.org
> Subject: IANA Considerations
> 
> I initiated discussion with our ADs recently regarding the IANA
> considerations in RFC 2661.
> 
> There are two decisions we face, and have not reached clear agreement.
> 
> I'd like to get a feel of the WGs opinion here.
> 
> Issue #1
> 
> Currently, a new IETF AVP value may only be requested for RFCs. That
> is,
> after last call and approval by the IESG. In DC we discussed (and
> agreed
> upon) the value in obtaining numbers from IANA here at an earlier
> stage
> so as to reduce the risk of ultimately maintaining two values (the
> IANA
> number and whatever vendor-specific number that was originally
> documented).
> 
> We have three choices.
> 
> A. Stay where we are, and request IANA numbers only after the RFC
> publication is imminent.
> B. Write a short RFC modifying the policy.
> C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
> until it is published before it can be followed.
> 
> The new policy might be that a person (such as the WG chair) is
> appointed to determine when the WG has sufficient consensus to request
> a
> value. This would typically be at or near the point of last call,
> depending on implementation demand and clarity of consensus.
> 
> Issue #2
> 
> This is simply where to begin handing out new values for AVPs. The
> highest value now is 39. We have two choices.
> 
> A. Begin at 40
> B. Begin at some other value slightly higher, say, 50, so that *if* we
> 
> end up adding an AVP or two to the base spec as it advances, we can
> remain contiguous in the base spec.
> 
> Opinions appreciated. Thanks,
> 
> - Mark


From owner-l2tp@ipsec.org  Fri Apr 21 15:44:32 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24373
	for <l2tpext-archive@odin.ietf.org>; Fri, 21 Apr 2000 15:44:31 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA05225; Fri, 21 Apr 2000 10:32:54 -0700 (PDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA05221 for <l2tp@ipsec.org>; Fri, 21 Apr 2000 10:32:36 -0700 (PDT)
Received: from gwz (sj-dial-1-188.cisco.com [171.68.179.189]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id KAA02260; Fri, 21 Apr 2000 10:31:28 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "W. Mark Townsley" <townsley@cisco.com>,
        "pcalhoun@eng.sun.com" <pcalhoun@ha1mpk-mail.Eng.Sun.COM>
Cc: "Bill Palter" <palter@zev.net>, "Evan Caves" <evan.caves@ericsson.com>,
        <l2tp@ipsec.org>
Subject: RE: IANA Considerations
Date: Fri, 21 Apr 2000 10:31:16 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPIEMNCCAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <38FFBC0C.CDFA86C3@cisco.com>
Importance: Normal
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

W. Mark Townsley [mailto://townsley@cisco.com] writes:

>
> "pcalhoun@eng.sun.com" wrote:
> >
> > hmmm... I'm not sure that this is really the direction that we
> want. I would
> > actually ask that we update RFC2661, and state that the numbers
> are assigned
> > from a Designated Expert, which is frequently done.
> >
> > The con: We have to reset the clock before moving to draft standard.
>
> Which clock? We have edits to do anyway and the draft standard goal is
> still months away. Are you suggesting that such a change would require
> recycling at PS?

Perhaps the ADs would care to comment on this, but I doubt that this kind of
change would cause recycling at PS, since the change is substantively
administrative rather than technical.

>
> >
> > The pro: Number allocation actually works
>
> A nice upshot.
>
> >
> > PatC
>
>



From owner-l2tp@ipsec.org  Fri Apr 21 15:44:33 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24384
	for <l2tpext-archive@odin.ietf.org>; Fri, 21 Apr 2000 15:44:33 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id KAA05219; Fri, 21 Apr 2000 10:30:07 -0700 (PDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA05212 for <l2tp@ipsec.org>; Fri, 21 Apr 2000 10:29:29 -0700 (PDT)
Received: from gwz (sj-dial-1-188.cisco.com [171.68.179.189]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id KAA25508; Fri, 21 Apr 2000 10:26:44 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "W. Mark Townsley" <townsley@cisco.com>, "Bill Palter" <palter@zev.net>
Cc: "Evan Caves" <evan.caves@ericsson.com>, <l2tp@ipsec.org>
Subject: RE: IANA Considerations
Date: Fri, 21 Apr 2000 10:26:31 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPEEMNCCAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <38FFBA91.7E2E8115@cisco.com>
Importance: Normal
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


W. Mark Townsley [mailto://townsley@cisco.com] writes:

>
> Bill Palter wrote:
> >
> > > Would it make it any easier if we defined an 'experimental' vendor ID
> > > which IANA can allocate AVP types/values out of. The number
> space could
> > > mirror the IETF number space (may be hard to manage) so that
> if adopted
> > > the type/values remain the same, just the vendor ID changes.
> > >
> > > just a thought,
> >
> >   I like it......Wonder what we need to do to get a vendor id
> allocated..

I'm not sure what advantage this scheme has over just using the vendor ID of
the primary draft author's company (cisco, MSFT, etc.) in combination w/some
modest coordination of number assignment (perhaps by the WG Chair?).  You're
still likely to have to support 2 AVPs w/the same (or at least similar)
semantics (the "experimental" and the standard)for an indeterminateperiod
after the issuance of the RFC, right?

>
> I doubt the ADs would go for this. Pretty soon, every working group will
> want their own Vendor ID. Not a bad idea per se, but additional
> adminstrative overhead is often resisted...
>
> However, if we wanted to buck the system, there are a number of
> companies that could donate their SMI Enterprise code to us :-)
>
> - Mark
>
> > >
> > > evan
> > > -
> > >
> > > "W. Mark Townsley" wrote:
> > > >
> > > > I initiated discussion with our ADs recently regarding the IANA
> > > > considerations in RFC 2661.
> > > >
> > > > There are two decisions we face, and have not reached clear
> agreement.
> > > > I'd like to get a feel of the WGs opinion here.
> > > >
> > > > Issue #1
> > > >
> > > > Currently, a new IETF AVP value may only be requested for
> RFCs. That is,
> > > > after last call and approval by the IESG. In DC we
> discussed (and agreed
> > > > upon) the value in obtaining numbers from IANA here at an
> earlier stage
> > > > so as to reduce the risk of ultimately maintaining two
> values (the IANA
> > > > number and whatever vendor-specific number that was originally
> > > > documented).
> > > >
> > > > We have three choices.
> > > >
> > > > A. Stay where we are, and request IANA numbers only after the RFC
> > > > publication is imminent.
> > > > B. Write a short RFC modifying the policy.
> > > > C. Modify RFC 2661 in the next rev to reflect a new policy, and wait
> > > > until it is published before it can be followed.
> > > >
> > > > The new policy might be that a person (such as the WG chair) is
> > > > appointed to determine when the WG has sufficient consensus
> to request a
> > > > value. This would typically be at or near the point of last call,
> > > > depending on implementation demand and clarity of consensus.
> > > >
> > > > Issue #2
> > > >
> > > > This is simply where to begin handing out new values for AVPs. The
> > > > highest value now is 39. We have two choices.
> > > >
> > > > A. Begin at 40
> > > > B. Begin at some other value slightly higher, say, 50, so
> that *if* we
> > > > end up adding an AVP or two to the base spec as it advances, we can
> > > > remain contiguous in the base spec.
> > > >
> > > > Opinions appreciated. Thanks,
> > > >
> > > > - Mark
> > --
> > Bill Palter (Palter@zev.net)
>
>



From owner-l2tp@ipsec.org  Fri Apr 21 17:23:44 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25909
	for <l2tpext-archive@odin.ietf.org>; Fri, 21 Apr 2000 17:23:44 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id MAA05379; Fri, 21 Apr 2000 12:33:13 -0700 (PDT)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA05375 for <l2tp@ipsec.org>; Fri, 21 Apr 2000 12:32:56 -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 PAA23616;
	Fri, 21 Apr 2000 15:32:22 -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 PAA29016;
	Fri, 21 Apr 2000 15:32:20 -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 PAA17446; Fri, 21 Apr 2000 15:29:30 -0400
Message-Id: <200004211929.PAA17446@ludwigia.raleigh.ibm.com>
To: gwz@cisco.com
cc: l2tp@ipsec.org
Subject: Re: IANA Considerations 
In-Reply-To: Message from "Glen Zorn" <gwz@cisco.com> 
   of "Fri, 21 Apr 2000 10:31:16 PDT." <NDBBIHMPILAAGDHPCIOPIEMNCCAA.gwz@cisco.com> 
Date: Fri, 21 Apr 2000 15:29:30 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-l2tp@ipsec.org
Precedence: bulk

> > > The con: We have to reset the clock before moving to draft standard.
> >
> > Which clock? We have edits to do anyway and the draft standard goal is
> > still months away. Are you suggesting that such a change would require
> > recycling at PS?

> Perhaps the ADs would care to comment on this, but I doubt that this
> kind of change would cause recycling at PS, since the change is
> substantively administrative rather than technical.

Changing the IANA considerations will have no effect on whether the
document needs to recycle at Proposed or can advance to Draft.

When deciding whether to advance or recycle, interoperability
considerations are the main concern. If a revised document results in
implementations compliant with the old spec no longer being
interoperable with implementations based only on the new, recycling is
required. Otherwise, advancing is probably OK. I.e., you can't advance
if there are substantive changes.

Thomas


From owner-l2tp@ipsec.org  Mon Apr 24 16:17:29 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13934
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Apr 2000 16:17:28 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id LAA13120; Mon, 24 Apr 2000 11:51:41 -0700 (PDT)
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA13110 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 11:51:22 -0700 (PDT)
Received: from globespan.net (phoenix.ficon-tech.com [209.125.90.2]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 29ABXJWF; Mon, 24 Apr 2000 14:48:13 -0400
Message-ID: <390499BF.97C94E4D@globespan.net>
Date: Mon, 24 Apr 2000 15:00:15 -0400
From: Srinivasan Balaji <sbalaji@globespan.net>
Organization: GlobeSpan, Inc
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: Protocols other than PPP in L2TP
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,
  I am very new to L2TP & this mailing list. I was wondering
if there is any provision to carry packets other than PPP in
the L2TP tunnels.  If there is no such provision, is there a
plan to make such a thing possible or is there sufficient
interest to carry other packets in the tunnel? I have not
seen a AVP about encapsulation yet and hence had
the doubt.
  Also, is there an uptodate archive of the mailing
list somewhere? I have seen one recommended by
the WG, but the last mail is dated Nov 11,'99 which
seems quite old (http://www.ipsec.org/email/l2tp).

TIA,
Balaji.
--
  Srinivasan Balaji
GlobeSpan, Inc. Voice : (732) 283-2770 xtn.303
mailto:sbalaji@globespan.net
Web: http://www.globespan.net




From owner-l2tp@ipsec.org  Mon Apr 24 16:19:14 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13962
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Apr 2000 16:19:14 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id MAA13190; Mon, 24 Apr 2000 12:22:26 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA13184 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 12:22:07 -0700 (PDT)
Received: from cisco.com (rtp7-dhcp-58-133.cisco.com [161.44.58.133]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id MAA23855; Mon, 24 Apr 2000 12:21:35 -0700 (PDT)
Message-ID: <39049EC0.4D11267D@cisco.com>
Date: Mon, 24 Apr 2000 15:21:36 -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: Srinivasan Balaji <sbalaji@globespan.net>
CC: l2tp@ipsec.org
Subject: Re: Protocols other than PPP in L2TP
References: <390499BF.97C94E4D@globespan.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srinivasan Balaji wrote:
> 
> Folks,
>   I am very new to L2TP & this mailing list. I was wondering
> if there is any provision to carry packets other than PPP in
> the L2TP tunnels.  If there is no such provision, is there a
> plan to make such a thing possible or is there sufficient
> interest to carry other packets in the tunnel? I have not
> seen a AVP about encapsulation yet and hence had
> the doubt.

L2TP is certainly extensible enough to carry other L2 protocols, however
it is currently beyond the WGs charter to pursue this.

>   Also, is there an uptodate archive of the mailing
> list somewhere? I have seen one recommended by
> the WG, but the last mail is dated Nov 11,'99 which
> seems quite old (http://www.ipsec.org/email/l2tp).

This is being addressed now. Should have a new archive available
shortly. Apologies for the current gap.

- Mark

> 
> TIA,
> Balaji.
> --
>   Srinivasan Balaji
> GlobeSpan, Inc. Voice : (732) 283-2770 xtn.303
> mailto:sbalaji@globespan.net
> Web: http://www.globespan.net


From owner-l2tp@ipsec.org  Mon Apr 24 17:51:33 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15888
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Apr 2000 17:51:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id NAA13410; Mon, 24 Apr 2000 13:56:03 -0700 (PDT)
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA13406 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 13:55:34 -0700 (PDT)
Received: from globespan.net (phoenix.ficon-tech.com [209.125.90.2]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 29ABXK2M; Mon, 24 Apr 2000 16:52:27 -0400
Message-ID: <3904B6D5.A1D6894@globespan.net>
Date: Mon, 24 Apr 2000 17:04:21 -0400
From: Srinivasan Balaji <sbalaji@globespan.net>
Organization: GlobeSpan, Inc
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
CC: l2tp@ipsec.org
Subject: Re: Protocols other than PPP in L2TP
References: <390499BF.97C94E4D@globespan.net> <39049EC0.4D11267D@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mark,
  I completely agree with the fact that L2TP is extensible
to carry other protocols other than PPP. Do you know
if anyone else is/was trying to pursue such extensions?
Which other WG would be working on such aspects?

    I think it is probably a matter a defining an AVP to
indicate that the incoming packets would be say RFC2684
encapsulated to get every thing that this RFC has defined.
This also has PPP so the default of PPP would also
get covered. What the WG can also do is that if this AVP is
not defined then PPP can be assumed by default for
backward compatibility.
    I would definitely like to hear from others also to see
if there is any interest in this.
    Mark, is it possible to know how many subscribers
are there for the mailing list (any mailing list for that
matter).

Thanks
Balaji.

"W. Mark Townsley" wrote:

> Srinivasan Balaji wrote:
> >
> > Folks,
> >   I am very new to L2TP & this mailing list. I was wondering
> > if there is any provision to carry packets other than PPP in
> > the L2TP tunnels.  If there is no such provision, is there a
> > plan to make such a thing possible or is there sufficient
> > interest to carry other packets in the tunnel? I have not
> > seen a AVP about encapsulation yet and hence had
> > the doubt.
>
> L2TP is certainly extensible enough to carry other L2 protocols, however
> it is currently beyond the WGs charter to pursue this.
>
> >   Also, is there an uptodate archive of the mailing
> > list somewhere? I have seen one recommended by
> > the WG, but the last mail is dated Nov 11,'99 which
> > seems quite old (http://www.ipsec.org/email/l2tp).
>
> This is being addressed now. Should have a new archive available
> shortly. Apologies for the current gap.
>
> - Mark
>
> >
> > TIA,
> > Balaji.
> > --
> >   Srinivasan Balaji
> > GlobeSpan, Inc. Voice : (732) 283-2770 xtn.303
> > mailto:sbalaji@globespan.net
> > Web: http://www.globespan.net

--
  Srinivasan Balaji
GlobeSpan, Inc. Voice : (732) 283-2770 xtn.303
mailto:sbalaji@globespan.net
Web: http://www.globespan.net




From owner-l2tp@ipsec.org  Mon Apr 24 19:08:24 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17209
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Apr 2000 19:08:23 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id PAA13636; Mon, 24 Apr 2000 15:12:24 -0700 (PDT)
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.69.63.18]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA13632 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 15:11:49 -0700 (PDT)
Received: from cisco.com (rtp7-dhcp-58-133.cisco.com [161.44.58.133]) by iwan-view3.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id PAA25951; Mon, 24 Apr 2000 15:11:17 -0700 (PDT)
Message-ID: <3904C686.F435C190@cisco.com>
Date: Mon, 24 Apr 2000 18:11:18 -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: Srinivasan Balaji <sbalaji@globespan.net>
CC: l2tp@ipsec.org
Subject: Re: Protocols other than PPP in L2TP
References: <390499BF.97C94E4D@globespan.net> <39049EC0.4D11267D@cisco.com> <3904B6D5.A1D6894@globespan.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Srinivasan Balaji wrote:
> 
> Mark,
>   I completely agree with the fact that L2TP is extensible
> to carry other protocols other than PPP. Do you know
> if anyone else is/was trying to pursue such extensions?
> Which other WG would be working on such aspects?

None within the IETF. It was decided during the development of l2tp
(within pppext) that we would focus on PPP tunneling only. This,
however, is not the first time I have heard about doing otherwise. If
there is a *resounding* concensus in l2tpext that we should persue this,
we could look into adding it to the charter. 

> 
>     I think it is probably a matter a defining an AVP to
> indicate that the incoming packets would be say RFC2684
> encapsulated to get every thing that this RFC has defined.
> This also has PPP so the default of PPP would also
> get covered. What the WG can also do is that if this AVP is
> not defined then PPP can be assumed by default for
> backward compatibility.
>     I would definitely like to hear from others also to see
> if there is any interest in this.

If there is potential for standards work here, yes, please speak up now.

>     Mark, is it possible to know how many subscribers
> are there for the mailing list (any mailing list for that
> matter).

http://www.greatcircle.com/majordomo/majordomo-faq.html

> 
> Thanks
> Balaji.
> 
> "W. Mark Townsley" wrote:
> 
> > Srinivasan Balaji wrote:
> > >
> > > Folks,
> > >   I am very new to L2TP & this mailing list. I was wondering
> > > if there is any provision to carry packets other than PPP in
> > > the L2TP tunnels.  If there is no such provision, is there a
> > > plan to make such a thing possible or is there sufficient
> > > interest to carry other packets in the tunnel? I have not
> > > seen a AVP about encapsulation yet and hence had
> > > the doubt.
> >
> > L2TP is certainly extensible enough to carry other L2 protocols, however
> > it is currently beyond the WGs charter to pursue this.
> >
> > >   Also, is there an uptodate archive of the mailing
> > > list somewhere? I have seen one recommended by
> > > the WG, but the last mail is dated Nov 11,'99 which
> > > seems quite old (http://www.ipsec.org/email/l2tp).
> >
> > This is being addressed now. Should have a new archive available
> > shortly. Apologies for the current gap.
> >
> > - Mark
> >
> > >
> > > TIA,
> > > Balaji.
> > > --
> > >   Srinivasan Balaji
> > > GlobeSpan, Inc. Voice : (732) 283-2770 xtn.303
> > > mailto:sbalaji@globespan.net
> > > Web: http://www.globespan.net
> 
> --
>   Srinivasan Balaji
> GlobeSpan, Inc. Voice : (732) 283-2770 xtn.303
> mailto:sbalaji@globespan.net
> Web: http://www.globespan.net


From owner-l2tp@ipsec.org  Mon Apr 24 21:58:09 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20542
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Apr 2000 21:58:09 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id RAA13817; Mon, 24 Apr 2000 17:56:46 -0700 (PDT)
Received: from tea.uk.pw.com (tea.uk.pw.com [193.131.169.130]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id RAA13813 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 17:56:25 -0700 (PDT)
From: damjan.gautschi@ch.pwcglobal.com
Received: by tea.uk.pw.com; id BAA26893; Tue, 25 Apr 2000 01:50:54 +0100
Received: from olive.uk.pw.com(10.44.240.46) by tea.uk.pw.com via smap (4.1)
	id xma026401; Tue, 25 Apr 00 01:50:21 +0100
Received: from intleursmtp10.uk.pw.com by olive.uk.pw.com (PMDF V5.1-12 #U3018)
 with SMTP id <0FTJ00FPLRPZNK@olive.uk.pw.com>; Tue,
 25 Apr 2000 01:51:35 +0100 (BST)
Received: by intleursmtp10.uk.pw.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))
 id 802568CC.0004DD06 ; Tue, 25 Apr 2000 01:53:07 +0100
Date: Tue, 25 Apr 2000 02:51:26 +0200
Subject: =?iso-8859-1?Q?L2TP_and_MPLS_VPN=B4s?=
To: l2tp@ipsec.org
Cc: mpls@UU.NET
Message-id: <802568CC.0004DC6E.00@intleursmtp10.uk.pw.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-disposition: inline
X-Lotus-FromDomain: EMEA-CH@INTL
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA20542




how does L2TP work together with MPLS VPN´s?
Can it be used to ensure additional security, and is it reasonable to
interconnect different VNP´s trough L2-tunnels through a MPLS core?
Is there an extension for l2tp in PPPoATM to make it work over/under MPLS?

I'd appreciate any insite into this issue that you can provide.


cheers,

damjan
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material.  Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited.   If you received this in error, please
contact the sender and delete the material from any computer.




From owner-l2tp@ipsec.org  Mon Apr 24 22:09:46 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20707
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Apr 2000 22:09:45 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id SAA13836; Mon, 24 Apr 2000 18:09:44 -0700 (PDT)
Received: from people.cisco.com (people.cisco.com [171.69.43.33]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA13832 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 18:09:24 -0700 (PDT)
Received: from cisco.com (warsaw.cisco.com [171.69.71.119])
	by people.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id SAA05768;
	Mon, 24 Apr 2000 18:04:41 -0700 (PDT)
Message-ID: <3904EFCA.7689E450@cisco.com>
Date: Mon, 24 Apr 2000 18:07:22 -0700
From: Robert Raszuk <rraszuk@cisco.com>
Reply-To: rraszuk@cisco.com
Organization: http://wwwin-mpls.cisco.com/
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: damjan.gautschi@ch.pwcglobal.com
CC: l2tp@ipsec.org, mpls@UU.NET
Subject: Re: L2TP and MPLS =?iso-8859-1?Q?VPN=B4s?=
References: <802568CC.0004DC6E.00@intleursmtp10.uk.pw.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 8bit


L2TP is mainly used as an access method to mpls-vpn network. There you
can also run IPSec if needed for encryption. I don't think that using it
inside your core which already is running mpls makes too much sens.

R.

> damjan.gautschi@ch.pwcglobal.com wrote:
> 
> how does L2TP work together with MPLS VPN´s?
> Can it be used to ensure additional security, and is it reasonable to
> interconnect different VNP´s trough L2-tunnels through a MPLS core?
> Is there an extension for l2tp in PPPoATM to make it work over/under MPLS?
> 
> I'd appreciate any insite into this issue that you can provide.
> 
> cheers,
> 
> damjan
> ----------------------------------------------------------------
> The information transmitted is intended only for the person or entity to which
> it is addressed and may contain confidential and/or privileged material.  Any
> review, retransmission, dissemination or other use of, or taking of any action
> in reliance upon, this information by persons or entities other than the
> intended recipient is prohibited.   If you received this in error, please
> contact the sender and delete the material from any computer.

-- 

_____________________________________________________________________

     |          |         Robert Raszuk, CCIE #3690  ICQ #12710752
    :|:        :|:        IOS-Engineering, MPLS Development Team
   :|||:      :|||:       170 W. Tasman Dr. N2, San Jose, CA 95134
.:|||||||:..:|||||||:.    Phone: 408-525-7588     Pager: 888-581-1312
C I S C O S Y S T E M S   Email: raszuk@cisco.com   Fax: 408-525-7588
                          URL:   http://wwwin-mpls.cisco.com/
_____________________________________________________________________


From owner-l2tp@ipsec.org  Tue Apr 25 01:02:41 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24200
	for <l2tpext-archive@odin.ietf.org>; Tue, 25 Apr 2000 01:02:40 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns3.sailpix.com (8.8.8/8.6.9) id UAA14116; Mon, 24 Apr 2000 20:44:07 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns3.sailpix.com (8.8.8/8.6.9) with SMTP id UAA14085 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 20:41:49 -0700 (PDT)
Received: by ans2-pub.dttus.com id WAA19146
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Mon, 24 Apr 2000 22:41:38 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Mon, 24 Apr 2000 22:41:38 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Mon, 24 Apr 2000 22:41:38 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E656755756@uscntnt405a.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: damjan.gautschi@ch.pwcglobal.com
Cc: l2tp@ipsec.org
Subject: =?iso-8859-1?Q?RE=3A_L2TP_and_MPLS_VPN=B4s?=
Date: Mon, 24 Apr 2000 20:39:23 -0700
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFAE67.D484ACB4"
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_01BFAE67.D484ACB4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

L2TP is an encapsulation protocol for PPP. It is independent of the =
network
carrying it (although current standards are for UDP, ATM and FR)
L2TP provides no additional security, infact additional forms of =
security
such as IPSec are recommended when using L2TP. PPPoATM and L2TP are two
different things. PPPoATM describes an encapsulation method for
encapsulating PPP in an ATM network only.

Hope this helps.

Regards

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


-----Original Message-----
From: damjan.gautschi@ch.pwcglobal.com
[mailto:damjan.gautschi@ch.pwcglobal.com]
Sent: Monday, April 24, 2000 7:51 PM
To: l2tp@ipsec.org
Cc: mpls@UU.NET
Subject: L2TP and MPLS VPN=B4s





how does L2TP work together with MPLS VPN=B4s?
Can it be used to ensure additional security, and is it reasonable to
interconnect different VNP=B4s trough L2-tunnels through a MPLS core?
Is there an extension for l2tp in PPPoATM to make it work over/under =
MPLS?

I'd appreciate any insite into this issue that you can provide.


cheers,

damjan
----------------------------------------------------------------
The information transmitted is intended only for the person or entity =
to
which
it is addressed and may contain confidential and/or privileged =
material.
Any
review, retransmission, dissemination or other use of, or taking of any
action
in reliance upon, this information by persons or entities other than =
the
intended recipient is prohibited.   If you received this in error, =
please
contact the sender and delete the material from any computer.


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: L2TP and MPLS VPN=B4s</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>L2TP is an encapsulation protocol for PPP. It is =
independent of the network carrying it (although current standards are =
for UDP, ATM and FR)</FONT></P>

<P><FONT SIZE=3D2>L2TP provides no additional security, infact =
additional forms of security such as IPSec are recommended when using =
L2TP. PPPoATM and L2TP are two different things. PPPoATM describes an =
encapsulation method for encapsulating PPP in an ATM network =
only.</FONT></P>

<P><FONT SIZE=3D2>Hope this helps.</FONT>
</P>

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

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: damjan.gautschi@ch.pwcglobal.com</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:damjan.gautschi@ch.pwcglobal.com">mailto:damjan.gautschi@=
ch.pwcglobal.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, April 24, 2000 7:51 PM</FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Cc: mpls@UU.NET</FONT>
<BR><FONT SIZE=3D2>Subject: L2TP and MPLS VPN=B4s</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>how does L2TP work together with MPLS VPN=B4s?</FONT>
<BR><FONT SIZE=3D2>Can it be used to ensure additional security, and is =
it reasonable to</FONT>
<BR><FONT SIZE=3D2>interconnect different VNP=B4s trough L2-tunnels =
through a MPLS core?</FONT>
<BR><FONT SIZE=3D2>Is there an extension for l2tp in PPPoATM to make it =
work over/under MPLS?</FONT>
</P>

<P><FONT SIZE=3D2>I'd appreciate any insite into this issue that you =
can provide.</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>damjan</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
-</FONT>
<BR><FONT SIZE=3D2>The information transmitted is intended only for the =
person or entity to which</FONT>
<BR><FONT SIZE=3D2>it is addressed and may contain confidential and/or =
privileged material.&nbsp; Any</FONT>
<BR><FONT SIZE=3D2>review, retransmission, dissemination or other use =
of, or taking of any action</FONT>
<BR><FONT SIZE=3D2>in reliance upon, this information by persons or =
entities other than the</FONT>
<BR><FONT SIZE=3D2>intended recipient is prohibited.&nbsp;&nbsp; If you =
received this in error, please</FONT>
<BR><FONT SIZE=3D2>contact the sender and delete the material from any =
computer.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFAE67.D484ACB4--


From owner-l2tp@ipsec.org  Tue Apr 25 03:00:45 2000
Received: from ns3.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06464
	for <l2tpext-archive@odin.ietf.org>; Tue, 25 Apr 2000 03:00:44 -0400 (EDT)
Received: (from majordomo@localhost) by ns3.sailpix.com (8.8.8/8.6.9) id WAA14368; Mon, 24 Apr 2000 22:48:05 -0700 (PDT)
Received: from tcb.net (tcb.net [205.168.100.1]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA14364 for <l2tp@ipsec.org>; Mon, 24 Apr 2000 22:47: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 FAA22347;
	Tue, 25 Apr 2000 05:53:14 -0600
Message-Id: <200004251153.FAA22347@tcb.net>
To: "W. Mark Townsley" <townsley@cisco.com>
cc: l2tp@ipsec.org
From: Danny McPherson <danny@ambernetworks.com>
Reply-To: danny@ambernetworks.com
Subject: Re: Protocols other than PPP in L2TP 
Date: Tue, 25 Apr 2000 05:53:14 -0600
Sender: owner-l2tp@ipsec.org
Precedence: bulk


I'd certainly like to see the charter expanded to support 
additional work of this nature, I know of implementations
that already use L2TP to support "additional" services.  

-danny


From owner-l2tp@ipsec.org  Thu Apr 27 01:30: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 BAA15603
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Apr 2000 01:30:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id SAA00256; Wed, 26 Apr 2000 18:54:31 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.3.78]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA00252 for <l2tp@ipsec.org>; Wed, 26 Apr 2000 18:54:16 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.3.78]) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id AAA06499; Thu, 27 Apr 2000 00:16:27 -0400 (EDT)
Date: Thu, 27 Apr 2000 00:16:27 -0400 (EDT)
From: "W. Mark Townsley" <townsley@cisco.com>
To: =?iso-8859-1?Q?=DFN=B7=AC?= <yhf@ms.chttl.com.tw>
cc: Glen Zorn <gwz@cisco.com>, l2tp@ipsec.org
Subject: Re: new draft about "Securing L2TP using IPSEC" ?
In-Reply-To: <39078754.BE263B8F@ms.chttl.com.tw>
Message-ID: <Pine.GSO.4.10.10004270013560.23817-100000@claret.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id BAA15603

On Thu, 27 Apr 2000, [iso-8859-1] ßN·¬ wrote:

> 
> But it has expired.

Check again. The name changed from "pppext" to "l2tpext" 

This draft was submitted in Feb of this year.

> 
> 
> Glen Zorn wrote:
> 
> > > Hi,
> > > Is there any new draft or standard comes out to obsoletes
> > > the expired draft, "Securing L2TP using IPSEC" ?
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-security-00.txt
> >
> > >
> > > Hsiao-Feng
> > >
> 



From owner-l2tp@ipsec.org  Thu Apr 27 01:31:50 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15885
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Apr 2000 01:31:50 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id SAA00172; Wed, 26 Apr 2000 18:22:26 -0700 (PDT)
Received: from firewall.chttl.com.tw ([202.39.157.254]) by ns3.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA00503 for <l2tp@ipsec.org>; Wed, 26 Apr 2000 17:16:28 -0700 (PDT)
Received: from ms.chttl.com.tw (ms.tl.gov.tw. [10.144.2.104])
	by firewall.chttl.com.tw (8.9.3/8.9.3) with ESMTP id IAA01421;
	Thu, 27 Apr 2000 08:15:50 +0800 (CST)
Received: from ms.chttl.com.tw ([10.144.169.37])
	by ms.chttl.com.tw (8.9.3/8.9.3) with ESMTP id IAA10091;
	Thu, 27 Apr 2000 08:16:58 +0800 (CST)
Message-ID: <39078754.BE263B8F@ms.chttl.com.tw>
Date: Thu, 27 Apr 2000 08:18:28 +0800
From: =?iso-8859-1?Q?=DFN=B7=AC?= <yhf@ms.chttl.com.tw>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Glen Zorn <gwz@cisco.com>, l2tp@ipsec.org
Subject: Re: new draft about "Securing L2TP using IPSEC" ?
References: <NDBBIHMPILAAGDHPCIOPKENDCBAA.gwz@cisco.com>
Content-Type: multipart/mixed;
 boundary="------------4399CF6D685E6BF5624807DC"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

This is a multi-part message in MIME format.
--------------4399CF6D685E6BF5624807DC
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


But it has expired.


Glen Zorn wrote:

> > Hi,
> > Is there any new draft or standard comes out to obsoletes
> > the expired draft, "Securing L2TP using IPSEC" ?
>
> http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-security-00.txt
>
> >
> > Hsiao-Feng
> >

--------------4399CF6D685E6BF5624807DC
Content-Type: text/x-vcard; charset=us-ascii;
 name="yhf.vcf"
Content-Description: Card for ßN·¬
Content-Disposition: attachment;
 filename="yhf.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Yeh;Hsiao-Feng
tel;work:+886-3-4245064
x-mozilla-html:FALSE
fn;quoted-printable:=B8=AD=DFN=B7=AC
org:Chunghwa Telecom Co. TL.
adr:;;;;;;
version:2.1
email;internet:yhf@chttl.com.tw
end:vcard

--------------4399CF6D685E6BF5624807DC--



From owner-l2tp@ipsec.org  Thu Apr 27 16:34:04 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06342
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Apr 2000 16:34:04 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id KAA02466; Thu, 27 Apr 2000 10:02:04 -0700 (PDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id KAA02462 for <l2tp@ipsec.org>; Thu, 27 Apr 2000 10:01:43 -0700 (PDT)
Received: (qmail 26807 invoked by uid 60001); 27 Apr 2000 19:24:59 -0000
Message-ID: <20000427192459.26806.qmail@web1406.mail.yahoo.com>
Received: from [38.186.47.9] by web1406.mail.yahoo.com; Thu, 27 Apr 2000 12:24:59 PDT
Date: Thu, 27 Apr 2000 12:24:59 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: new draft about "Securing L2TP using IPSEC" ?
To: "W. Mark Townsley" <townsley@cisco.com>, "ßN·¬" <yhf@ms.chttl.com.tw>
Cc: Glen Zorn <gwz@cisco.com>, l2tp@ipsec.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-l2tp@ipsec.org
Precedence: bulk



Sorry, I had to submit this as an independent draft, as the draft did
not seem to fit within the WG charters of pppext or l2tpext or ipsra.
The new draft ID is <draft-srisuresh-secure-ra-01.txt>

cheers,
suresh

--- "W. Mark Townsley" <townsley@cisco.com> wrote:
> On Thu, 27 Apr 2000, [iso-8859-1] ßN·¬ wrote:
> 
> > 
> > But it has expired.
> 
> Check again. The name changed from "pppext" to "l2tpext" 
> 
> This draft was submitted in Feb of this year.
> 
> > 
> > 
> > Glen Zorn wrote:
> > 
> > > > Hi,
> > > > Is there any new draft or standard comes out to obsoletes
> > > > the expired draft, "Securing L2TP using IPSEC" ?
> > >
> > > http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-security-00.txt
> > >
> > > >
> > > > Hsiao-Feng
> > > >
> > 
> 

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


