From owner-l2tp@ipsec.org  Wed Mar  1 00:33:54 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11931
	for <l2tpext-archive@odin.ietf.org>; Wed, 1 Mar 2000 00:33:54 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id UAA23610; Tue, 29 Feb 2000 20:27:01 -0800 (PST)
Received: from web1405.mail.yahoo.com (web1405.mail.yahoo.com [128.11.23.169]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id UAA23606 for <l2tp@ipsec.org>; Tue, 29 Feb 2000 20:26:40 -0800 (PST)
Received: (qmail 10687 invoked by uid 60001); 1 Mar 2000 04:29:28 -0000
Message-ID: <20000301042928.10686.qmail@web1405.mail.yahoo.com>
Received: from [38.186.47.232] by web1405.mail.yahoo.com; Tue, 29 Feb 2000 20:29:28 PST
Date: Tue, 29 Feb 2000 20:29:28 -0800 (PST)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: L2TP Over IPSec & Tunnel Setup
To: Gokul Subramaniam <gokuls@nortelnetworks.com>, l2tp@ipsec.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-l2tp@sailpix.com
Precedence: bulk


You might want to take a look at the draft titled 
"Secure Remote Access with L2TP" 
(<draft-ietf-pppext-secure-ra-00.txt>).

The document proposes three new RADIUS parameters for 
use by the LNS, acting as Secure Remote Access Server (SRAS). 

cheers,
suresh

--- Gokul Subramaniam <gokuls@nortelnetworks.com> wrote:
> Hello.,
> 
> Problem Context:
> The implementation of an L2TP tunnel was to access private network.
> Compulsory tunneling is used. Tunnel setup is done for the users after
> authentication using RADIUS.
> RADIUS is used to get the tunnel information (using access request and
> accept messages passing the LAC-tunnel initiator info in access req and
> receiving LNS-tunnel terminator info in access accept message) - in
> conformance to IETF Draft: RADIUS Attributes for Tunnel Protocol Support
> <draft-ietf-radius-tunnel-auth-09.txt>.
> 
> Problem:
> Although the RADIUS extension for tunnel-auth provides the LNS ip
> address and supported tunnel type, it does not support configuration
> information for ipsec.
> LNS gets the LAC information from RADIUS. But where does the LNS get
> ipsec related information for the tunnel terminator (LAC). This is not
> addressed in the RADIUS Tunnel support draft. In order to get the ipsec
> profile and ike profiles should the LNS be configured separately on a
> per tunnel terminator basis?
> 
> Are there any extensions that support getting the profiles or
> negotiating the ipsec and ike profiles as part of getting the tunnel
> terminator information.
> 
> Input is appreciated.
> 
> 

=====

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


From owner-l2tp@ipsec.org  Thu Mar  2 05:26:35 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09478
	for <l2tpext-archive@odin.ietf.org>; Thu, 2 Mar 2000 05:26:34 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id BAA26959; Thu, 2 Mar 2000 01:10:42 -0800 (PST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA26955 for <l2tp@ipsec.org>; Thu, 2 Mar 2000 01:10:27 -0800 (PST)
Received: from haag-ultra.cisco.com (haag-ultra.cisco.com [161.44.49.30])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id BAA27944;
	Thu, 2 Mar 2000 01:33:07 -0800 (PST)
Received: from cisco.com (sj-dial-1-2.cisco.com [171.68.179.3]) by haag-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id EAA24973; Thu, 2 Mar 2000 04:09:58 -0500 (EST)
Message-ID: <38BE2FAC.FC2C9B3B@cisco.com>
Date: Thu, 02 Mar 2000 04:09:00 -0500
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: l2tp@ipsec.org
CC: agenda@ietf.org
Subject: Agenda for l2tpext in Adelaide
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


l2tpext will meet 1530-1730, on Wednesday March 29, opposite rmonmib,
rtgarea, smime and avt.

This is the current agenda. Please let me know ASAP if you wish a slot
and are not listed here.

1530 Agenda Bashing

1535 Bernard Aboba 
     draft-ietf-l2tpext-security-00.txt
     (formally draft-ietf-pppext-l2tp-security-05.txt)
     
1605 Pat Calhoun
     draft-ietf-pppext-l2tp-ds-03.txt

1620 Pat Calhoun     
     draft-ietf-pppext-l2tp-mpls-02.txt

1635 Yves T'Joens
     draft-ietf-pppext-l2tp-atmext-01.txt

1645 Evan Caves, Ross Wheeler or Pat Calhoun
     will discuss the MIB. If it gets updated in time, 
     it will be draft-ietf-l2tpext-mib-00.txt

1700 W. Mark Townsley
     L2TP v2 draft discussion, 
     Status of other drafts, 
     Charter milestone update and review


From owner-l2tp@ipsec.org  Fri Mar  3 07:52:38 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24751
	for <l2tpext-archive@odin.ietf.org>; Fri, 3 Mar 2000 07:52:38 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id DAA01002; Fri, 3 Mar 2000 03:28:38 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA00998 for <l2tp@ipsec.org>; Fri, 3 Mar 2000 03:28:07 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22661;
	Fri, 3 Mar 2000 06:27:55 -0500 (EST)
Message-Id: <200003031127.GAA22661@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: l2tp@ipsec.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l2tpext-atmext-01.txt
Date: Fri, 03 Mar 2000 06:27:54 -0500
Sender: owner-l2tp@sailpix.com
Precedence: bulk

--NextPart

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

	Title		: Layer Two Tunnelling Protocol : ATM access network 
                          extensions
	Author(s)	: Y. T'Joens, P. Crivellari, B. Sales
 	Filename	: draft-ietf-l2tpext-atmext-01.txt
	Pages		: 18
	Date		: 02-Mar-00
	
L2TP [RFC2661] specifies a protocol which permits the tunnelling of
the link layer of PPP over packet based networks, to support remote
access (mainly) by ISDN and PSTN networks. This document augments the
procedures described in [RFC2661] to further support ATM SVC or PVC
based access networks. The extensions defined within this document
allow for asymmetric bi-directional call establishment and service
selection in the ATM access network.

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Fri Mar  3 13:21:31 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05337
	for <l2tpext-archive@odin.ietf.org>; Fri, 3 Mar 2000 13:21:28 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id IAA00341; Fri, 3 Mar 2000 08:09:19 -0800 (PST)
Received: from coredump.ae.usr.com (coredump.ae.usr.com [207.24.169.214]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA00337 for <l2tp@ipsec.org>; Fri, 3 Mar 2000 08:09:09 -0800 (PST)
Received: from otherland (localhost [127.0.0.1])
	by coredump.ae.usr.com (8.9.2/8.9.2) with SMTP id LAA23113
	for <l2tp@ipsec.org>; Fri, 3 Mar 2000 11:11:24 -0600 (CST)
From: "Mike Wronski" <mike@coredump.ae.usr.com>
To: <l2tp@ipsec.org>
Subject: Radius Tag field???
Date: Fri, 3 Mar 2000 11:11:24 -0600
Message-ID: <000101bf8533$81225380$7fa918cf@otherland.ae.usr.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
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Importance: Normal
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

What does this actually do?? The draft states that it is four grouping
attributes that are part of the same tunnel..
Is there a case where multiple tunnels would be built based on a single
Access Accept packet??

-
Mike Wronski
3Com Network Systems Engineer



From owner-l2tp@ipsec.org  Fri Mar  3 13:34:18 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05825
	for <l2tpext-archive@odin.ietf.org>; Fri, 3 Mar 2000 13:34:18 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id IAA00394; Fri, 3 Mar 2000 08:23:28 -0800 (PST)
Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id IAA00390 for <l2tp@ipsec.org>; Fri, 3 Mar 2000 08:23:18 -0800 (PST)
From: Barney Wolff <barney@databus.com>
To: <l2tp@ipsec.org>
Date: Fri, 3 Mar 2000 12:21 EST
Subject: Re: Radius Tag field???
Content-Type: text/plain
Message-ID: <38bff5a90.114e@databus.databus.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

No, it's to handle cases where there are multiple possibilities,
and tunnel establishment may not always succeed.
Barney Wolff  <barney@databus.com>

> From: "Mike Wronski" <mike@coredump.ae.usr.com>
> Date: Fri, 3 Mar 2000 11:11:24 -0600
> 
> What does this actually do?? The draft states that it is four grouping
> attributes that are part of the same tunnel..
> Is there a case where multiple tunnels would be built based on a single
> Access Accept packet??


From owner-l2tp@ipsec.org  Fri Mar  3 15:12:10 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08159
	for <l2tpext-archive@odin.ietf.org>; Fri, 3 Mar 2000 15:12:02 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id JAA00572; Fri, 3 Mar 2000 09:58:20 -0800 (PST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA00567 for <l2tp@ipsec.org>; Fri, 3 Mar 2000 09:58:08 -0800 (PST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA04513;
	Fri, 3 Mar 2000 11:00:53 -0800 (PST)
Received: from ha1mpk-mail.eng.sun.com (phys-ha1mpka.Eng.Sun.COM [129.146.91.34])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with SMTP id LAA18729;
	Fri, 3 Mar 2000 11:00:52 -0800 (PST)
Received: from mordor by ha1mpk-mail.eng.sun.com (SMI-8.6/SMI-SVR4)
	id LAA24798; Fri, 3 Mar 2000 11:00:51 -0800
Date: Fri, 3 Mar 2000 11:00:50 -0800 (PST)
From: "pcalhoun@eng.sun.com" <pcalhoun@ha1mpk-mail.Eng.Sun.COM>
Reply-To: "pcalhoun@eng.sun.com" <pcalhoun@ha1mpk-mail.Eng.Sun.COM>
Subject: New versions of L2TP DS and MPLS drafts available
To: l2tp@ipsec.org
Cc: Ken@malibunetworks.com
Message-ID: <Roam.SIMC.2.0.6.952110050.27820.pcalhoun@ha1mpk-mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-l2tp@sailpix.com
Precedence: bulk

All,

I just sent out the new versions of the L2TP Differentiated Services and
Multi-Protocol Label Switching drafts to the secretariat. I will be presenting
these drafts at the IETF, and I am making them available from my web site  for
those that want to get their hands on them earlier.

They can be found at:
	www.diameter.org/l2tp/draft-ietf-l2tpext-ds-00.txt
	www.diameter.org/l2tp/draft-ietf-l2tpext-mpls-00.txt

Enjoy,

PatC



From owner-l2tp@ipsec.org  Mon Mar  6 08:34:29 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04725
	for <l2tpext-archive@odin.ietf.org>; Mon, 6 Mar 2000 08:34:29 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id CAA06172; Mon, 6 Mar 2000 02:55:45 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id CAA06164 for <l2tp@ipsec.org>; Mon, 6 Mar 2000 02:54:49 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02494;
	Mon, 6 Mar 2000 06:57:35 -0500 (EST)
Message-Id: <200003061157.GAA02494@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-ds-00.txt
Date: Mon, 06 Mar 2000 06:57:35 -0500
Sender: owner-l2tp@sailpix.com
Precedence: bulk

--NextPart

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

	Title		: Layer Two Tunneling Protocol 'L2TP' IP Differentiated 
                          Services Extension
	Author(s)	: P. Calhoun, K. Peirce
	Filename	: draft-ietf-l2tpext-ds-00.txt
	Pages		: 5
	Date		: 03-Mar-00
	
The L2TP document [1] defines the base protocol which describes the
method of tunneling PPP data. The L2TP base protocol does not address
any Differentiated Services extensions.
The ability to outsource dial access with Quality of Service
assurances is important to internet applications development. This
draft addresses this issue by allowing each L2TP Data Session to be
assigned an appropriate differentiated services indicator.

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

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

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


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

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

--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:	<20000303140637.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Mon Mar  6 08:35:17 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04822
	for <l2tpext-archive@odin.ietf.org>; Mon, 6 Mar 2000 08:35:17 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id CAA06173; Mon, 6 Mar 2000 02:55:49 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id CAA06168 for <l2tp@ipsec.org>; Mon, 6 Mar 2000 02:54:54 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02480;
	Mon, 6 Mar 2000 06:57:31 -0500 (EST)
Message-Id: <200003061157.GAA02480@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-mpls-00.txt
Date: Mon, 06 Mar 2000 06:57:30 -0500
Sender: owner-l2tp@sailpix.com
Precedence: bulk

--NextPart

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

	Title		: Layer Two Tunneling Protocol 'L2TP' Multi-Protocol 
                          Label Switching Extension
	Author(s)	: P. Calhoun, K. Peirce 
	Filename	: draft-ietf-l2tpext-mpls-00.txt
	Pages		: 5
	Date		: 03-Mar-00
	
The L2TP document [1] defines the base protocol which describes the
method of tunneling PPP data. The L2TP base protocol does not address
any MPLS extensions.
The goal of MPLS is to speed forwarding of packets by reducing the
lookup required in routing. This draft proposes a method to allow
L2TP Data Sessions to be assigned an MPLS Label Switched Path Id
(LSPID)[3] for an explicit route (ER). Assignment of such an ER is
necessary for traffic engineering.

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Mon Mar  6 17:09:19 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11217
	for <l2tpext-archive@odin.ietf.org>; Mon, 6 Mar 2000 17:09:18 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id LAA08073; Mon, 6 Mar 2000 11:43:42 -0800 (PST)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA08069 for <l2tp@ipsec.org>; Mon, 6 Mar 2000 11:43:30 -0800 (PST)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id NAA03102 for <l2tp@ipsec.org>; Mon, 6 Mar 2000 13:46:16 -0700 (MST)]
Received: [from ilms06.cig.mot.com (ilms06.cig.mot.com [136.182.15.18]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id NAA25958 for <l2tp@ipsec.org>; Mon, 6 Mar 2000 13:45:39 -0700 (MST)]
Received: from email.mot.com ([160.44.110.59]) by ilms06.cig.mot.com
          (Netscape Messaging Server 3.01)  with ESMTP id AAA12034;
          Mon, 6 Mar 2000 14:44:55 -0600
Message-ID: <38C40EA3.42F99FD3@email.mot.com>
Date: Mon, 06 Mar 2000 14:01:39 -0600
From: "Ajoy Singh" <ASINGH1@email.mot.com>
Organization: Motorola
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: 3gpp2tsgp@3gpp2.org, "l2tp@ipsec.org" <l2tp@ipsec.org>,
        Charles Hirschman <Charles_Brent_Hirschman-QA4053@email.mot.com>,
        Ali Irfan-FIA225 <Irfan_Ali-FIA225@email.mot.com>,
        Gopal Dommety <gdommety@cisco.com>, "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: FLOW Control for L2TP data 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

 Can some body provide me some of the explanation why flow control was
removed from L2TP ? Currently we are working on some tunneling protocol
called R-P which although looks like L2TP/PPTP but has some different
requirements.  We want to find out why flow control was removed from
L2TP and does the same logic applies at R-P interface.  I would
appreciate your reply regarding this matter.
regards,
ajoy






From owner-l2tp@ipsec.org  Wed Mar  8 08:13:57 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01394
	for <l2tpext-archive@odin.ietf.org>; Wed, 8 Mar 2000 08:13:56 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id CAA12019; Wed, 8 Mar 2000 02:30:29 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id CAA12012 for <l2tp@ipsec.org>; Wed, 8 Mar 2000 02:29:56 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29061;
	Wed, 8 Mar 2000 06:32:39 -0500 (EST)
Message-Id: <200003081132.GAA29061@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: l2tp@ipsec.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l2tpext-l2tp-mib-00.txt
Date: Wed, 08 Mar 2000 06:32:39 -0500
Sender: owner-l2tp@sailpix.com
Precedence: bulk

--NextPart

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

	Title		: Layer Two Tunneling Protocol 'L2TP' Management    
                          Information Base
	Author(s)	: E. Caves, P. Calhoun, R. Wheeler
	Filename	: draft-ietf-l2tpext-l2tp-mib-00.txt
	Pages		: 71
	Date		: 07-Mar-00
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing networks using Layer 2
Tunneling Protocol.
This memo specifies a MIB module in a manner that is both compliant
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
definitions.

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Thu Mar  9 16:48:42 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04087
	for <l2tpext-archive@odin.ietf.org>; Thu, 9 Mar 2000 16:48:35 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id LAA16916; Thu, 9 Mar 2000 11:07:14 -0800 (PST)
Received: from chef.redback.com (chef.redbacknetworks.com [155.53.190.24]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA16912 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 11:07:08 -0800 (PST)
Received: from localhost (localhost [[UNIX: localhost]])
	by chef.redback.com (8.8.8/8.8.8) id MAA01200
	for l2tp@ipsec.org; Thu, 9 Mar 2000 12:08:39 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA16834 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 10:13:47 -0800 (PST)
Received: from gdommety-pc2 (dhcp-sjc9-233-161.cisco.com [171.71.233.161])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id LAA04813
	for <l2tp@ipsec.org>; Thu, 9 Mar 2000 11:16:03 -0800 (PST)
Message-Id: <200003091916.LAA04813@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Thu, 09 Mar 2000 11:28:35 -0800
To: l2tp@ipsec.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: New GRE Draft Extensions
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hello:

I am  attaching the  GRE addendum/extensions.  As  you go  through the
 draft at places identified by # there are request for comments. I have 
split the sequence no into two subfeilds (the other option is to define an
acknowledgement like PPTP WHEN such a need it felt).

Please subscribe to gre@ops.ietf.org by sending email to 
gre-request@ops.ietf.org. Please send (or cc) all discussion 
to this mailing list.


Thanks
Gopal




Network Working Group                                      Gopal Dommety
INTERNET DRAFT                                             cisco Systems 
March 2000                                               

Expires October 2000

		Key and Sequence Number Extensions to GRE
		    draft-dommety-gre-ext-00.txt

Status of this Memo

   This document is a submission by the Network Working Group of the
   Internet Engineering Task Force (IETF).  Comments should be submitted
   to the gre@ops.ietf.org mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet Draft and is in full conformance with
   all provisions of Section 10 of RFC2026. Internet Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and working groups. Note that other groups may also distribute
   working documents as Internet Drafts.

   Internet Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.
   
Abstract
   
   This  document describes extensions  by which  two fields,  Key and
Sequence Number, can be optionally carried in the GRE (Generic Routing
Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
of an arbitrary network  layer protocol over another arbitrary network
layer  protocol. 

Dommety		                                                  [Page 1]

Internet Draft  Key and Sequence Number Extensions to GRE  February 2000

1. Introduction

   Current specification of Generic Routing Encapsulation [1] specifies
a protocol  for encapsulation of  an arbitrary network  layer protocol
over another arbitrary network layer protocol. This document describes
enhancements  by which  two fields,  Key and  Sequence Number,  can be
optionally carried  in the GRE  Header [1]. The  Key field is  used to
create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
is used to maintain sequence of packets within a GRE Tunnel.

1.1. Specification Language

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC 2119 [3].

   In addition, the following words are used to signify the 
   requirements of the specification.  

   Silently discard
              The implementation discards the datagram without
              further processing, and without indicating an error
              to the sender.  The implementation SHOULD provide the
              capability of logging the error, including the contents
              of the discarded datagram, and SHOULD record the event
              in a statistics counter.

2. Extensions to GRE Header

   The GRE packet header[1] has the following format:

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |C|       Reserved0       | Ver |         Protocol Type         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      Checksum (optional)      |       Reserved1 (Optional)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


    The proposed GRE header will have the following format:

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |C| |K|S| Reserved0       | Ver |         Protocol Type         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      Checksum (optional)      |       Reserved1 (Optional)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         Key (optional)                        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Rx Sequence Number (Optional)| Tx Sequence Number (Optional) |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      

      Key Present (bit 2)

      If the Key Present bit is set to 1, then it indicates that the Key
      field is present in the GRE header.  Otherwise, the Key field is
      not present in the GRE header.

      Sequence Number Present (bit 3)

      If the Sequence Number Present bit is set to 1, then it indicates
      that the Sequence Number field is present.  Otherwise, the
      Sequence Number field is not present in the GRE header.

      The  Key and Sequence Present bits are chosen to be  compatible 
      with RFC 1701 [2].
 
2.1. Key Field (4 octets)

     The Key field contains a  four octet number which was inserted by
     the encapsulator. The actual method by which this Key is obtained
     is beyond the scope of this document.  Key field is intended to be
     used for  creating separate sub-tunnels within a  GRE Tunnel and the
     Key field identifies the sub-tunnel. 

2.2. Sequence Number (4 octets)
 
    The Sequence Number  field is divided into two  sub-fields (Tx and
    Rx sequence number). These subfields are inserted by the encapsulator 
    when Sequence Number Present Bit is set . Tx Sequence Number  MUST 
    be used by the receiver to establish the  order in which  packets
    have been  transmitted from the  encapsulator  to  the  receiver.  
    The intended  use  of  the Tx Sequence  Field is  to provide 
    unreliable and in-order delivery.   If the Key  present bit (bit 2) 
    is set, the sequence number is specific to the sub-tunnel identified
    by the Key field.

    The Tx sequence number  value ranges from 1 to  65535. The first 
    datagram is sent with a Tx sequence number of 1. The Tx sequence 
    number is thus a free running counter represented modulo 65536, 
    with the exception that 1 is used when modulo 65536 results in 0 
    (i.e., rollover to 1 instead of 0). The Rx Sequence number is set to 0.

#Q The Rx can be the Tx  sequence number of the last successfully decap
  pack.  And  say  that  how  you  use  this  info  is  implementation
  dependent.  I am currently saying Rx sequence no
  is set to 0. Comments?


    When the decapsulator receives an out-of sequence packet it SHOULD
    be silently discarded. Additionally, reordering of out-of sequence
    packets  MAY  be  performed   by  the  decapsulator  for  improved
    performance and  tolerance to reordering in the  network (since the
    state of the stateful compression or encryption is reset by packet
    loss, it  might help the  performance to tolerate some  amount of
    packet reordering in the network by buffering). Exact buffering 
    schemes are outside the scope
    of  this  document. Note that the  Tx sequence number is used to detect
    lost packets and/or restore  the original sequence of packets that
    may have been reordered during transport.

   A packet  is considered an out-of-sequence packet  if the Tx sequence
   number  of  the  received packet  is  lesser than or equal to  the Tx
   sequence  number   of last  successfully  decapsulated
   packet. The  Tx sequence number  of a received message is considered
   less than or equal to the last successfully received Tx sequence number 
   if its value lies in the range of the last received Tx sequence number 
   and the preceding 32766 values, inclusive.  For example, if the last 
   successfully received Tx sequence number was 15, then messages with Tx 
   sequence numbers 1 through 15, as well as 32784 through 65535, would be 
   considered less than or equal. Such a message would be considered an 
   out-of-sequence packet and  ignored from processing.

    If the received packet is an in-sequence packet, it is successfully
    de capsulated. Note that  the TX sequence number is  used to detect
    lost packets and/or restore the original sequence of packets (with
    buffering) that may have been reordered during transport.

#C I have considered trying to  have a different starting point for TX
sequence nos  during rollover and initial starting  point.  This would
let a node  identify if the other end  reset (like agent advertisement
sequence no to identify reboot and normal rollover). This is useful if
we keep  turning on  and off  sequence nos option  in a  tunnel. Since
there  is no  security it  is easy  for others  to reset  the sequence
also. Comments?


3. IANA Considerations

4. Acknowledgments

 
5. References

   [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
   "Generic           Routing           Encapsulation          (GRE),"
   draft-meyer-gre-update-03.txt, January 2000.

   [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
   Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems, 
   October 1994.

   [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
       Levels", RFC 2119, March 1997.
  

Dommety                                                 [Page 4]

Internet Draft   Key and Sequence Number extensions to GRE   February 2000

Author Information

   Gopal Dommety
   Cisco Systems, Inc.
   170 West Tasman Drive
   San Jose, CA 95134
   e-mail: gdommety@cisco.com

Dommety





Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Thu Mar  9 19:47:50 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27464
	for <l2tpext-archive@odin.ietf.org>; Thu, 9 Mar 2000 19:47:49 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA17308; Thu, 9 Mar 2000 14:47:22 -0800 (PST)
Received: from chef.redback.com (chef.redbacknetworks.com [155.53.190.24]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA17301 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 14:47:12 -0800 (PST)
Received: (from carrel@localhost)
	by chef.redback.com (8.8.8/8.8.8) id PAA02665
	for l2tp@ipsec.org; Thu, 9 Mar 2000 15:48:43 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA17023 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 11:44:01 -0800 (PST)
Received: from gdommety-pc2 (dhcp-sjc9-233-161.cisco.com [171.71.233.161])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id MAA21507;
	Thu, 9 Mar 2000 12:46:21 -0800 (PST)
Message-Id: <200003092046.MAA21507@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Thu, 09 Mar 2000 12:58:46 -0800
To: ietf-ppp@merit.edu, l2tp@ipsec.org, gre@ops.ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: New GRE Draft  Extensions
Cc: mobile-ip@standards.nortelnetworks.com, dmm@cisco.com,
        Erik.Nordmark@eng.sun.com, fred@cisco.com, udlr@sophia.inria.fr,
        narten@raleigh.ibm.com
In-Reply-To: <200003092018.MAA17086@omega.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk


>Please send  your comments to  gre@ops.ietf.org mailing list.  you can
>subscribe   to   this   mailing   list   by  sending   an   email   to
>request-gre@ops.ietf.org

Sorry, you need to send the email to gre-request@ops.ietf.org

-Gopal


Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Thu Mar  9 19:50:02 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28190
	for <l2tpext-archive@odin.ietf.org>; Thu, 9 Mar 2000 19:50:01 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA17372; Thu, 9 Mar 2000 14:56:46 -0800 (PST)
Received: from hotmail.com (f89.law8.hotmail.com [216.33.241.89]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id OAA17368 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 14:56:38 -0800 (PST)
Received: (qmail 13524 invoked by uid 0); 9 Mar 2000 23:58:59 -0000
Message-ID: <20000309235859.13523.qmail@hotmail.com>
Received: from 63.89.164.2 by www.hotmail.com with HTTP;
	Thu, 09 Mar 2000 15:58:59 PST
X-Originating-IP: [63.89.164.2]
From: "Seamus O'Kelly" <seamus_oc@hotmail.com>
To: l2tp@ipsec.org
Subject: ToS For L2TP
Date: Thu, 09 Mar 2000 15:58:59 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Can anyone refer me to where I can find what types of service L2TP supports?

Thank You
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



From owner-l2tp@ipsec.org  Thu Mar  9 20:02:58 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02185
	for <l2tpext-archive@odin.ietf.org>; Thu, 9 Mar 2000 20:02:56 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id OAA17307; Thu, 9 Mar 2000 14:47:20 -0800 (PST)
Received: from chef.redback.com (chef.redbacknetworks.com [155.53.190.24]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA17296 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 14:47:08 -0800 (PST)
Received: from localhost (localhost [[UNIX: localhost]])
	by chef.redback.com (8.8.8/8.8.8) id PAA02660
	for l2tp@ipsec.org; Thu, 9 Mar 2000 15:48:38 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA16929 for <l2tp@ipsec.org>; Thu, 9 Mar 2000 11:16:30 -0800 (PST)
Received: from gdommety-pc2 (dhcp-sjc9-233-161.cisco.com [171.71.233.161])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id MAA17086;
	Thu, 9 Mar 2000 12:18:47 -0800 (PST)
Message-Id: <200003092018.MAA17086@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Thu, 09 Mar 2000 12:31:14 -0800
To: ietf-ppp@merit.edu, l2tp@ipsec.org, gre@ops.ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: New GRE Draft  Extensions
Cc: mobile-ip@standards.nortelnetworks.com, dmm@cisco.com,
        Erik.Nordmark@eng.sun.com, fred@cisco.com, udlr@sophia.inria.fr,
        narten@raleigh.ibm.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hello:

I am  attaching the  GRE addendum/extensions.  As  you go  through the
 draft at places identified by # there are request for comments. I have 
split the sequence no into two subfeilds (the other option is to define an
acknowledgement like PPTP WHEN such a need it felt).

Please send  your comments to  gre@ops.ietf.org mailing list.  you can
subscribe   to   this   mailing   list   by  sending   an   email   to
request-gre@ops.ietf.org


Thanks
Gopal




Network Working Group                                      Gopal Dommety
INTERNET DRAFT                                             cisco Systems 
March 2000                                               

Expires October 2000

		Key and Sequence Number Extensions to GRE
		    draft-dommety-gre-ext-00.txt

Status of this Memo

   This document is a submission by the Network Working Group of the
   Internet Engineering Task Force (IETF).  Comments should be submitted
   to the gre@ops.ietf.org mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet Draft and is in full conformance with
   all provisions of Section 10 of RFC2026. Internet Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and working groups. Note that other groups may also distribute
   working documents as Internet Drafts.

   Internet Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.
   
Abstract
   
   This  document describes extensions  by which  two fields,  Key and
Sequence Number, can be optionally carried in the GRE (Generic Routing
Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
of an arbitrary network  layer protocol over another arbitrary network
layer  protocol. 

Dommety		                                                  [Page 1]

Internet Draft  Key and Sequence Number Extensions to GRE  February 2000

1. Introduction

   Current specification of Generic Routing Encapsulation [1] specifies
a protocol  for encapsulation of  an arbitrary network  layer protocol
over another arbitrary network layer protocol. This document describes
enhancements  by which  two fields,  Key and  Sequence Number,  can be
optionally carried  in the GRE  Header [1]. The  Key field is  used to
create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
is used to maintain sequence of packets within a GRE Tunnel.

1.1. Specification Language

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC 2119 [3].

   In addition, the following words are used to signify the 
   requirements of the specification.  

   Silently discard
              The implementation discards the datagram without
              further processing, and without indicating an error
              to the sender.  The implementation SHOULD provide the
              capability of logging the error, including the contents
              of the discarded datagram, and SHOULD record the event
              in a statistics counter.

2. Extensions to GRE Header

   The GRE packet header[1] has the following format:

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |C|       Reserved0       | Ver |         Protocol Type         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      Checksum (optional)      |       Reserved1 (Optional)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


    The proposed GRE header will have the following format:

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |C| |K|S| Reserved0       | Ver |         Protocol Type         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      Checksum (optional)      |       Reserved1 (Optional)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         Key (optional)                        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |  Rx Sequence Number (Optional)| Tx Sequence Number (Optional) |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      

      Key Present (bit 2)

      If the Key Present bit is set to 1, then it indicates that the Key
      field is present in the GRE header.  Otherwise, the Key field is
      not present in the GRE header.

      Sequence Number Present (bit 3)

      If the Sequence Number Present bit is set to 1, then it indicates
      that the Sequence Number field is present.  Otherwise, the
      Sequence Number field is not present in the GRE header.

      The  Key and Sequence Present bits are chosen to be  compatible 
      with RFC 1701 [2].
 
2.1. Key Field (4 octets)

     The Key field contains a  four octet number which was inserted by
     the encapsulator. The actual method by which this Key is obtained
     is beyond the scope of this document.  Key field is intended to be
     used for  creating separate sub-tunnels within a  GRE Tunnel and the
     Key field identifies the sub-tunnel. 

2.2. Sequence Number (4 octets)
 
    The Sequence Number  field is divided into two  sub-fields (Tx and
    Rx sequence number). These subfields are inserted by the encapsulator 
    when Sequence Number Present Bit is set . Tx Sequence Number  MUST 
    be used by the receiver to establish the  order in which  packets
    have been  transmitted from the  encapsulator  to  the  receiver.  
    The intended  use  of  the Tx Sequence  Field is  to provide 
    unreliable and in-order delivery.   If the Key  present bit (bit 2) 
    is set, the sequence number is specific to the sub-tunnel identified
    by the Key field.

    The Tx sequence number  value ranges from 1 to  65535. The first 
    datagram is sent with a Tx sequence number of 1. The Tx sequence 
    number is thus a free running counter represented modulo 65536, 
    with the exception that 1 is used when modulo 65536 results in 0 
    (i.e., rollover to 1 instead of 0). The Rx Sequence number is set to 0.

#Q The Rx can be the Tx  sequence number of the last successfully decap
  pack.  And  say  that  how  you  use  this  info  is  implementation
  dependent.  I am currently saying Rx sequence no
  is set to 0. Comments?


    When the decapsulator receives an out-of sequence packet it SHOULD
    be silently discarded. Additionally, reordering of out-of sequence
    packets  MAY  be  performed   by  the  decapsulator  for  improved
    performance and  tolerance to reordering in the  network (since the
    state of the stateful compression or encryption is reset by packet
    loss, it  might help the  performance to tolerate some  amount of
    packet reordering in the network by buffering). Exact buffering 
    schemes are outside the scope
    of  this  document. Note that the  Tx sequence number is used to detect
    lost packets and/or restore  the original sequence of packets that
    may have been reordered during transport.

   A packet  is considered an out-of-sequence packet  if the Tx sequence
   number  of  the  received packet  is  lesser than or equal to  the Tx
   sequence  number   of last  successfully  decapsulated
   packet. The  Tx sequence number  of a received message is considered
   less than or equal to the last successfully received Tx sequence number 
   if its value lies in the range of the last received Tx sequence number 
   and the preceding 32766 values, inclusive.  For example, if the last 
   successfully received Tx sequence number was 15, then messages with Tx 
   sequence numbers 1 through 15, as well as 32784 through 65535, would be 
   considered less than or equal. Such a message would be considered an 
   out-of-sequence packet and  ignored from processing.

    If the received packet is an in-sequence packet, it is successfully
    de capsulated. Note that  the TX sequence number is  used to detect
    lost packets and/or restore the original sequence of packets (with
    buffering) that may have been reordered during transport.

#C I have considered trying to  have a different starting point for TX
sequence nos  during rollover and initial starting  point.  This would
let a node  identify if the other end  reset (like agent advertisement
sequence no to identify reboot and normal rollover). This is useful if
we keep  turning on  and off  sequence nos option  in a  tunnel. Since
there  is no  security it  is easy  for others  to reset  the sequence
also. Comments?


3. IANA Considerations

4. Acknowledgments

 
5. References

   [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
   "Generic           Routing           Encapsulation          (GRE),"
   draft-meyer-gre-update-03.txt, January 2000.

   [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
   Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems, 
   October 1994.

   [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
       Levels", RFC 2119, March 1997.
  

Dommety                                                 [Page 4]

Internet Draft   Key and Sequence Number extensions to GRE   February 2000

Author Information

   Gopal Dommety
   Cisco Systems, Inc.
   170 West Tasman Drive
   San Jose, CA 95134
   e-mail: gdommety@cisco.com

Dommety





Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Fri Mar 10 14:56:16 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22949
	for <l2tpext-archive@odin.ietf.org>; Fri, 10 Mar 2000 14:56:14 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id JAA19842; Fri, 10 Mar 2000 09:07:46 -0800 (PST)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA19834 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 09:06:18 -0800 (PST)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id LAA22742 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 11:09:04 -0700 (MST)]
Received: [from ilms06.cig.mot.com (ilms06.cig.mot.com [136.182.15.18]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id LAA02950 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 11:09:04 -0700 (MST)]
Received: from email.mot.com ([160.44.110.59]) by ilms06.cig.mot.com
          (Netscape Messaging Server 3.01)  with ESMTP id AAA24248;
          Fri, 10 Mar 2000 12:08:52 -0600
Message-ID: <38C92FF2.1F789629@email.mot.com>
Date: Fri, 10 Mar 2000 11:25:06 -0600
From: "Ajoy Singh" <ASINGH1@email.mot.com>
Organization: Motorola
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Gopal Dommety <gdommety@cisco.com>
CC: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, gre-request@ops.ietf.org,
        l2tp@ipsec.org
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
References: <200003092018.MAA17086@omega.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Gopal,

Here is couple of questions i have regarding the attached GRE draft.  I have not participated in previous
discussion of GRE, so i am
not aware of any decision made by IESG regarding this respect.

1. What is the Value of Version number field of  proposed GRE header ?  Is it 0 or something else ?  Does it mean
that all existing GRE implementations need to change to support this header format to be standard compliant?  I
was hoping that we can use different version number to support the new extensions and that way we do not require
to change existing deployment of GRE. This way any network element can discard right away the GRE packets which
it does not support ?
2. In GRE header format you have  specified RX Sequence number which seems to me same as ack sequence number of
PPTP GRE. Why we need similar thing represented in two different way in two different standards ?

thanks,
ajoy

Gopal Dommety wrote:

> Hello:
>
> I am  attaching the  GRE addendum/extensions.  As  you go  through the
>  draft at places identified by # there are request for comments. I have
> split the sequence no into two subfeilds (the other option is to define an
> acknowledgement like PPTP WHEN such a need it felt).
>
> Please send  your comments to  gre@ops.ietf.org mailing list.  you can
> subscribe   to   this   mailing   list   by  sending   an   email   to
> request-gre@ops.ietf.org
>
> Thanks
> Gopal
>
> Network Working Group                                      Gopal Dommety
> INTERNET DRAFT                                             cisco Systems
> March 2000
>
> Expires October 2000
>
>                 Key and Sequence Number Extensions to GRE
>                     draft-dommety-gre-ext-00.txt
>
> Status of this Memo
>
>    This document is a submission by the Network Working Group of the
>    Internet Engineering Task Force (IETF).  Comments should be submitted
>    to the gre@ops.ietf.org mailing list.
>
>    Distribution of this memo is unlimited.
>
>    This document is an Internet Draft and is in full conformance with
>    all provisions of Section 10 of RFC2026. Internet Drafts are working
>    documents of the Internet Engineering Task Force (IETF), its areas,
>    and working groups. Note that other groups may also distribute
>    working documents as Internet Drafts.
>
>    Internet Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time. It is inappropriate to use Internet Drafts as reference
>    material or to cite them other than as "work in progress."
>
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
>
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
>
> Abstract
>
>    This  document describes extensions  by which  two fields,  Key and
> Sequence Number, can be optionally carried in the GRE (Generic Routing
> Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
> of an arbitrary network  layer protocol over another arbitrary network
> layer  protocol.
>
> Dommety                                                           [Page 1]
>
> Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
>
> 1. Introduction
>
>    Current specification of Generic Routing Encapsulation [1] specifies
> a protocol  for encapsulation of  an arbitrary network  layer protocol
> over another arbitrary network layer protocol. This document describes
> enhancements  by which  two fields,  Key and  Sequence Number,  can be
> optionally carried  in the GRE  Header [1]. The  Key field is  used to
> create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
> is used to maintain sequence of packets within a GRE Tunnel.
>
> 1.1. Specification Language
>
>    The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>    this document are to be interpreted as described in RFC 2119 [3].
>
>    In addition, the following words are used to signify the
>    requirements of the specification.
>
>    Silently discard
>               The implementation discards the datagram without
>               further processing, and without indicating an error
>               to the sender.  The implementation SHOULD provide the
>               capability of logging the error, including the contents
>               of the discarded datagram, and SHOULD record the event
>               in a statistics counter.
>
> 2. Extensions to GRE Header
>
>    The GRE packet header[1] has the following format:
>
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |C|       Reserved0       | Ver |         Protocol Type         |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |      Checksum (optional)      |       Reserved1 (Optional)    |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>     The proposed GRE header will have the following format:
>
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |C| |K|S| Reserved0       | Ver |         Protocol Type         |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |      Checksum (optional)      |       Reserved1 (Optional)    |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                         Key (optional)                        |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |  Rx Sequence Number (Optional)| Tx Sequence Number (Optional) |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       Key Present (bit 2)
>
>       If the Key Present bit is set to 1, then it indicates that the Key
>       field is present in the GRE header.  Otherwise, the Key field is
>       not present in the GRE header.
>
>       Sequence Number Present (bit 3)
>
>       If the Sequence Number Present bit is set to 1, then it indicates
>       that the Sequence Number field is present.  Otherwise, the
>       Sequence Number field is not present in the GRE header.
>
>       The  Key and Sequence Present bits are chosen to be  compatible
>       with RFC 1701 [2].
>
> 2.1. Key Field (4 octets)
>
>      The Key field contains a  four octet number which was inserted by
>      the encapsulator. The actual method by which this Key is obtained
>      is beyond the scope of this document.  Key field is intended to be
>      used for  creating separate sub-tunnels within a  GRE Tunnel and the
>      Key field identifies the sub-tunnel.
>
> 2.2. Sequence Number (4 octets)
>
>     The Sequence Number  field is divided into two  sub-fields (Tx and
>     Rx sequence number). These subfields are inserted by the encapsulator
>     when Sequence Number Present Bit is set . Tx Sequence Number  MUST
>     be used by the receiver to establish the  order in which  packets
>     have been  transmitted from the  encapsulator  to  the  receiver.
>     The intended  use  of  the Tx Sequence  Field is  to provide
>     unreliable and in-order delivery.   If the Key  present bit (bit 2)
>     is set, the sequence number is specific to the sub-tunnel identified
>     by the Key field.
>
>     The Tx sequence number  value ranges from 1 to  65535. The first
>     datagram is sent with a Tx sequence number of 1. The Tx sequence
>     number is thus a free running counter represented modulo 65536,
>     with the exception that 1 is used when modulo 65536 results in 0
>     (i.e., rollover to 1 instead of 0). The Rx Sequence number is set to 0.
>
> #Q The Rx can be the Tx  sequence number of the last successfully decap
>   pack.  And  say  that  how  you  use  this  info  is  implementation
>   dependent.  I am currently saying Rx sequence no
>   is set to 0. Comments?

The only possible way this sequence number can be used to support some type of sliding window protocol either for

flow control or retransmission. I belive this does

>
>
>     When the decapsulator receives an out-of sequence packet it SHOULD
>     be silently discarded. Additionally, reordering of out-of sequence
>     packets  MAY  be  performed   by  the  decapsulator  for  improved
>     performance and  tolerance to reordering in the  network (since the
>     state of the stateful compression or encryption is reset by packet
>     loss, it  might help the  performance to tolerate some  amount of
>     packet reordering in the network by buffering). Exact buffering
>     schemes are outside the scope
>     of  this  document. Note that the  Tx sequence number is used to detect
>     lost packets and/or restore  the original sequence of packets that
>     may have been reordered during transport.
>
>    A packet  is considered an out-of-sequence packet  if the Tx sequence
>    number  of  the  received packet  is  lesser than or equal to  the Tx
>    sequence  number   of last  successfully  decapsulated
>    packet. The  Tx sequence number  of a received message is considered
>    less than or equal to the last successfully received Tx sequence number
>    if its value lies in the range of the last received Tx sequence number
>    and the preceding 32766 values, inclusive.  For example, if the last
>    successfully received Tx sequence number was 15, then messages with Tx
>    sequence numbers 1 through 15, as well as 32784 through 65535, would be
>    considered less than or equal. Such a message would be considered an
>    out-of-sequence packet and  ignored from processing.
>
>     If the received packet is an in-sequence packet, it is successfully
>     de capsulated. Note that  the TX sequence number is  used to detect
>     lost packets and/or restore the original sequence of packets (with
>     buffering) that may have been reordered during transport.
>
> #C I have considered trying to  have a different starting point for TX
> sequence nos  during rollover and initial starting  point.  This would
> let a node  identify if the other end  reset (like agent advertisement
> sequence no to identify reboot and normal rollover). This is useful if
> we keep  turning on  and off  sequence nos option  in a  tunnel. Since
> there  is no  security it  is easy  for others  to reset  the sequence
> also. Comments?
>
> 3. IANA Considerations
>
> 4. Acknowledgments
>
> 5. References
>
>    [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
>    "Generic           Routing           Encapsulation          (GRE),"
>    draft-meyer-gre-update-03.txt, January 2000.
>
>    [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
>    Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems,
>    October 1994.
>
>    [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
>        Levels", RFC 2119, March 1997.
>
> Dommety                                                 [Page 4]
>
> Internet Draft   Key and Sequence Number extensions to GRE   February 2000
>
> Author Information
>
>    Gopal Dommety
>    Cisco Systems, Inc.
>    170 West Tasman Drive
>    San Jose, CA 95134
>    e-mail: gdommety@cisco.com
>
> Dommety
>
> Thank You.
> Regards,
> Gopal
> -------------------------------------------------------------------------------------------------------------
>
> Gopal Dommety
> 408 525 1404
> gdommety@cisco.com
> Cisco Systems, San Jose, CA, 95051



From owner-l2tp@ipsec.org  Fri Mar 10 15:09:03 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27041
	for <l2tpext-archive@odin.ietf.org>; Fri, 10 Mar 2000 15:09:02 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id JAA19919; Fri, 10 Mar 2000 09:52:18 -0800 (PST)
Received: from smtpproxy1.mitre.org (mbunix.mitre.org [129.83.20.100]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA19915 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 09:52:01 -0800 (PST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id NAA17494;
	Fri, 10 Mar 2000 13:54:31 -0500 (EST)
Received: from linus.mitre.org (linus.mitre.org [129.83.10.1])
	by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id NAA00349;
	Fri, 10 Mar 2000 13:54:06 -0500 (EST)
Received: from mitre.org (fchase.mitre.org [129.83.114.44])
	by linus.mitre.org (8.9.3/8.9.3) with ESMTP id NAA26751;
	Fri, 10 Mar 2000 13:54:24 -0500 (EST)
Message-ID: <38C94502.7D3D5026@mitre.org>
Date: Fri, 10 Mar 2000 13:54:58 -0500
From: "Frederick N. Chase" <fnc@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.7 [en]C-19991010M  (WinNT; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Gopal Dommety <gdommety@cisco.com>
CC: ietf-ppp@merit.edu, l2tp@ipsec.org, gre@ops.ietf.org,
        mobile-ip@standards.nortelnetworks.com, dmm@cisco.com,
        Erik.Nordmark@eng.sun.com, fred@cisco.com, udlr@sophia.inria.fr,
        narten@raleigh.ibm.com
Subject: Re: New GRE Draft  Extensions
References: <200003092046.MAA21507@omega.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Re:  Key and Sequence Number Extensions to GRE
                    
                    
                    
The proposed use of two previously-reserved header bits
in  draft-dommety-gre-ext-00.txt 
differ in a fundamental way.

The proposed use of a reserved bit as a
"Sequence Number Present" bit is a
potentially-beneficial modifier
on encapsulator/decapsulator behavior and therefore
seems to me to be advisable or at least not inadvisable.

The proposed use of a reserved bit as a
"Key Present" bit does not affect (narrowly construed)
encapsulator/decapsulator behavior but rather
concerns the processor of the encapsulated or decapsulated 
data.  This proposal seems to me to be inadvisable.

Acceptance of the "Key Present" proposal unnecessarily 
encumbers some other 
processor of encapsulated or decapsulated data
which might like to have an optional extra 32 bits for some purpose
where the terms "Key and "sub-tunnel" would be 
confusing and inappropriate.


   -Fred Chase


From owner-l2tp@ipsec.org  Fri Mar 10 15:27:08 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03406
	for <l2tpext-archive@odin.ietf.org>; Fri, 10 Mar 2000 15:27:06 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id KAA19978; Fri, 10 Mar 2000 10:07:42 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA19970 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 10:06:04 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id LAA06922;
	Fri, 10 Mar 2000 11:08:27 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id LAA16962; Fri, 10 Mar 2000 11:08:26 -0800 (PST)
Date: Fri, 10 Mar 2000 11:08:26 -0800
From: Rene Tio <tor@redback.com>
To: Ajoy Singh <ASINGH1@email.mot.com>
Cc: Gopal Dommety <gdommety@cisco.com>, MOBILE-IP@STANDARDS.NORTELNETWORKS.COM,
        gre-request@ops.ietf.org, l2tp@ipsec.org
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
Message-ID: <20000310110826.B16343@redback.com>
References: <200003092018.MAA17086@omega.cisco.com> <38C92FF2.1F789629@email.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38C92FF2.1F789629@email.mot.com>; from ASINGH1@email.mot.com on Fri, Mar 10, 2000 at 11:25:06AM -0600
Sender: owner-l2tp@sailpix.com
Precedence: bulk

On Fri, Mar 10, 2000 at 11:25:06AM -0600, Ajoy Singh wrote:
> Hello Gopal,
> 
> Here is couple of questions i have regarding the attached GRE draft.  I
> have not participated in previous discussion of GRE, so i am not aware of
> any decision made by IESG regarding this respect.

I do not know if the IESG figures into this since GRE is informational.
However I would like to know the reason behind the updates because
draft-meyer + draft-dommety looks pretty close to RFC 1701.  The changes
appear to be the semantics of the key field, which was somewhat semantic
free before since its use as an authenticator was always suspect, and the
split sequence number field.  What's the use of deprecating some fields in
one draft and extending it with the same deprecated fields in another draft?

> 1. What is the Value of Version number field of proposed GRE header ?  Is
> it 0 or something else ?  Does it mean that all existing GRE
> implementations need to change to support this header format to be
> standard compliant?

There is no change between draft-meyer-gre-update-03.txt and RFC 1701.  The
version field remains 0.

> I was hoping that we can use different version number to support the new
> extensions and that way we do not require to change existing deployment of
> GRE. This way any network element can discard right away the GRE packets
> which it does not support ?

Your point is well-taken.  Since the sequence number field is now split, RFC
1701 GRE will not understand draft-dommety GRE.  A new version number may be
required.  This is in contrast to draft-meyer, which is interoperable with
RFC 1701.

> 2. In GRE header format you have specified RX Sequence number which seems
> to me same as ack sequence number of PPTP GRE. Why we need similar thing
> represented in two different way in two different standards ?

Neither of them are "standards".  And not everyone uses GRE for PPTP.

R.

> thanks,
> ajoy
> 
> Gopal Dommety wrote:
> 
> > Hello:
> >
> > I am  attaching the  GRE addendum/extensions.  As  you go  through the
> >  draft at places identified by # there are request for comments. I have
> > split the sequence no into two subfeilds (the other option is to define an
> > acknowledgement like PPTP WHEN such a need it felt).
> >
> > Please send  your comments to  gre@ops.ietf.org mailing list.  you can
> > subscribe   to   this   mailing   list   by  sending   an   email   to
> > request-gre@ops.ietf.org
> >
> > Thanks
> > Gopal
> >
> > Network Working Group                                      Gopal Dommety
> > INTERNET DRAFT                                             cisco Systems
> > March 2000
> >
> > Expires October 2000
> >
> >                 Key and Sequence Number Extensions to GRE
> >                     draft-dommety-gre-ext-00.txt
> >
> > Status of this Memo
> >
> >    This document is a submission by the Network Working Group of the
> >    Internet Engineering Task Force (IETF).  Comments should be submitted
> >    to the gre@ops.ietf.org mailing list.
> >
> >    Distribution of this memo is unlimited.
> >
> >    This document is an Internet Draft and is in full conformance with
> >    all provisions of Section 10 of RFC2026. Internet Drafts are working
> >    documents of the Internet Engineering Task Force (IETF), its areas,
> >    and working groups. Note that other groups may also distribute
> >    working documents as Internet Drafts.
> >
> >    Internet Drafts are draft documents valid for a maximum of six months
> >    and may be updated, replaced, or obsoleted by other documents at any
> >    time. It is inappropriate to use Internet Drafts as reference
> >    material or to cite them other than as "work in progress."
> >
> >    The list of current Internet-Drafts can be accessed at
> >    http://www.ietf.org/ietf/1id-abstracts.txt.
> >
> >    The list of Internet-Draft Shadow Directories can be accessed at
> >    http://www.ietf.org/shadow.html.
> >
> > Abstract
> >
> >    This  document describes extensions  by which  two fields,  Key and
> > Sequence Number, can be optionally carried in the GRE (Generic Routing
> > Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
> > of an arbitrary network  layer protocol over another arbitrary network
> > layer  protocol.
> >
> > Dommety                                                           [Page 1]
> >
> > Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
> >
> > 1. Introduction
> >
> >    Current specification of Generic Routing Encapsulation [1] specifies
> > a protocol  for encapsulation of  an arbitrary network  layer protocol
> > over another arbitrary network layer protocol. This document describes
> > enhancements  by which  two fields,  Key and  Sequence Number,  can be
> > optionally carried  in the GRE  Header [1]. The  Key field is  used to
> > create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
> > is used to maintain sequence of packets within a GRE Tunnel.
> >
> > 1.1. Specification Language
> >
> >    The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
> >    this document are to be interpreted as described in RFC 2119 [3].
> >
> >    In addition, the following words are used to signify the
> >    requirements of the specification.
> >
> >    Silently discard
> >               The implementation discards the datagram without
> >               further processing, and without indicating an error
> >               to the sender.  The implementation SHOULD provide the
> >               capability of logging the error, including the contents
> >               of the discarded datagram, and SHOULD record the event
> >               in a statistics counter.
> >
> > 2. Extensions to GRE Header
> >
> >    The GRE packet header[1] has the following format:
> >
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |C|       Reserved0       | Ver |         Protocol Type         |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |      Checksum (optional)      |       Reserved1 (Optional)    |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >     The proposed GRE header will have the following format:
> >
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |C| |K|S| Reserved0       | Ver |         Protocol Type         |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |      Checksum (optional)      |       Reserved1 (Optional)    |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |                         Key (optional)                        |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |  Rx Sequence Number (Optional)| Tx Sequence Number (Optional) |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >       Key Present (bit 2)
> >
> >       If the Key Present bit is set to 1, then it indicates that the Key
> >       field is present in the GRE header.  Otherwise, the Key field is
> >       not present in the GRE header.
> >
> >       Sequence Number Present (bit 3)
> >
> >       If the Sequence Number Present bit is set to 1, then it indicates
> >       that the Sequence Number field is present.  Otherwise, the
> >       Sequence Number field is not present in the GRE header.
> >
> >       The  Key and Sequence Present bits are chosen to be  compatible
> >       with RFC 1701 [2].
> >
> > 2.1. Key Field (4 octets)
> >
> >      The Key field contains a  four octet number which was inserted by
> >      the encapsulator. The actual method by which this Key is obtained
> >      is beyond the scope of this document.  Key field is intended to be
> >      used for  creating separate sub-tunnels within a  GRE Tunnel and the
> >      Key field identifies the sub-tunnel.
> >
> > 2.2. Sequence Number (4 octets)
> >
> >     The Sequence Number  field is divided into two  sub-fields (Tx and
> >     Rx sequence number). These subfields are inserted by the encapsulator
> >     when Sequence Number Present Bit is set . Tx Sequence Number  MUST
> >     be used by the receiver to establish the  order in which  packets
> >     have been  transmitted from the  encapsulator  to  the  receiver.
> >     The intended  use  of  the Tx Sequence  Field is  to provide
> >     unreliable and in-order delivery.   If the Key  present bit (bit 2)
> >     is set, the sequence number is specific to the sub-tunnel identified
> >     by the Key field.
> >
> >     The Tx sequence number  value ranges from 1 to  65535. The first
> >     datagram is sent with a Tx sequence number of 1. The Tx sequence
> >     number is thus a free running counter represented modulo 65536,
> >     with the exception that 1 is used when modulo 65536 results in 0
> >     (i.e., rollover to 1 instead of 0). The Rx Sequence number is set to 0.
> >
> > #Q The Rx can be the Tx  sequence number of the last successfully decap
> >   pack.  And  say  that  how  you  use  this  info  is  implementation
> >   dependent.  I am currently saying Rx sequence no
> >   is set to 0. Comments?
> 
> The only possible way this sequence number can be used to support some type of sliding window protocol either for
> 
> flow control or retransmission. I belive this does
> 
> >
> >
> >     When the decapsulator receives an out-of sequence packet it SHOULD
> >     be silently discarded. Additionally, reordering of out-of sequence
> >     packets  MAY  be  performed   by  the  decapsulator  for  improved
> >     performance and  tolerance to reordering in the  network (since the
> >     state of the stateful compression or encryption is reset by packet
> >     loss, it  might help the  performance to tolerate some  amount of
> >     packet reordering in the network by buffering). Exact buffering
> >     schemes are outside the scope
> >     of  this  document. Note that the  Tx sequence number is used to detect
> >     lost packets and/or restore  the original sequence of packets that
> >     may have been reordered during transport.
> >
> >    A packet  is considered an out-of-sequence packet  if the Tx sequence
> >    number  of  the  received packet  is  lesser than or equal to  the Tx
> >    sequence  number   of last  successfully  decapsulated
> >    packet. The  Tx sequence number  of a received message is considered
> >    less than or equal to the last successfully received Tx sequence number
> >    if its value lies in the range of the last received Tx sequence number
> >    and the preceding 32766 values, inclusive.  For example, if the last
> >    successfully received Tx sequence number was 15, then messages with Tx
> >    sequence numbers 1 through 15, as well as 32784 through 65535, would be
> >    considered less than or equal. Such a message would be considered an
> >    out-of-sequence packet and  ignored from processing.
> >
> >     If the received packet is an in-sequence packet, it is successfully
> >     de capsulated. Note that  the TX sequence number is  used to detect
> >     lost packets and/or restore the original sequence of packets (with
> >     buffering) that may have been reordered during transport.
> >
> > #C I have considered trying to  have a different starting point for TX
> > sequence nos  during rollover and initial starting  point.  This would
> > let a node  identify if the other end  reset (like agent advertisement
> > sequence no to identify reboot and normal rollover). This is useful if
> > we keep  turning on  and off  sequence nos option  in a  tunnel. Since
> > there  is no  security it  is easy  for others  to reset  the sequence
> > also. Comments?
> >
> > 3. IANA Considerations
> >
> > 4. Acknowledgments
> >
> > 5. References
> >
> >    [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
> >    "Generic           Routing           Encapsulation          (GRE),"
> >    draft-meyer-gre-update-03.txt, January 2000.
> >
> >    [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
> >    Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems,
> >    October 1994.
> >
> >    [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
> >        Levels", RFC 2119, March 1997.
> >
> > Dommety                                                 [Page 4]
> >
> > Internet Draft   Key and Sequence Number extensions to GRE   February 2000
> >
> > Author Information
> >
> >    Gopal Dommety
> >    Cisco Systems, Inc.
> >    170 West Tasman Drive
> >    San Jose, CA 95134
> >    e-mail: gdommety@cisco.com
> >
> > Dommety
> >
> > Thank You.
> > Regards,
> > Gopal
> > -------------------------------------------------------------------------------------------------------------
> >
> > Gopal Dommety
> > 408 525 1404
> > gdommety@cisco.com
> > Cisco Systems, San Jose, CA, 95051
> 


From owner-l2tp@ipsec.org  Fri Mar 10 15:50:47 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11850
	for <l2tpext-archive@odin.ietf.org>; Fri, 10 Mar 2000 15:50:46 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id KAA19991; Fri, 10 Mar 2000 10:14:58 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA19987 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 10:13:20 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id LAA08445;
	Fri, 10 Mar 2000 11:15:43 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id LAA17013; Fri, 10 Mar 2000 11:15:43 -0800 (PST)
Date: Fri, 10 Mar 2000 11:08:26 -0800
From: Rene Tio <tor@redback.com>
To: Ajoy Singh <ASINGH1@email.mot.com>
Cc: Gopal Dommety <gdommety@cisco.com>, MOBILE-IP@STANDARDS.NORTELNETWORKS.COM,
        gre@ops.ietf.org, l2tp@ipsec.org
Subject: RESEND: [MOBILE-IP] New GRE Draft Extensions
Message-ID: <20000310110826.B16343@redback.com>
References: <200003092018.MAA17086@omega.cisco.com> <38C92FF2.1F789629@email.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
X-Mailer: Mutt 1.0i
In-Reply-To: <38C92FF2.1F789629@email.mot.com>; from ASINGH1@email.mot.com on Fri, Mar 10, 2000 at 11:25:06AM -0600
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Resending this to cover the GRE mailing list and to prevent others from
replying to the majordomo.

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

On Fri, Mar 10, 2000 at 11:25:06AM -0600, Ajoy Singh wrote:
> Hello Gopal,
> 
> Here is couple of questions i have regarding the attached GRE draft.  I
> have not participated in previous discussion of GRE, so i am not aware of
> any decision made by IESG regarding this respect.

I do not know if the IESG figures into this since GRE is informational.
However I would like to know the reason behind the updates because
draft-meyer + draft-dommety looks pretty close to RFC 1701.  The changes
appear to be the semantics of the key field, which was somewhat semantic
free before since its use as an authenticator was always suspect, and the
split sequence number field.  What's the use of deprecating some fields in
one draft and extending it with the same deprecated fields in another draft?

> 1. What is the Value of Version number field of proposed GRE header ?  Is
> it 0 or something else ?  Does it mean that all existing GRE
> implementations need to change to support this header format to be
> standard compliant?

There is no change between draft-meyer-gre-update-03.txt and RFC 1701.  The
version field remains 0.

> I was hoping that we can use different version number to support the new
> extensions and that way we do not require to change existing deployment of
> GRE. This way any network element can discard right away the GRE packets
> which it does not support ?

Your point is well-taken.  Since the sequence number field is now split, RFC
1701 GRE will not understand draft-dommety GRE.  A new version number may be
required.  This is in contrast to draft-meyer, which is interoperable with
RFC 1701.

> 2. In GRE header format you have specified RX Sequence number which seems
> to me same as ack sequence number of PPTP GRE. Why we need similar thing
> represented in two different way in two different standards ?

Neither of them are "standards".  And not everyone uses GRE for PPTP.

R.

> thanks,
> ajoy
> 
> Gopal Dommety wrote:
> 
> > Hello:
> >
> > I am  attaching the  GRE addendum/extensions.  As  you go  through the
> >  draft at places identified by # there are request for comments. I have
> > split the sequence no into two subfeilds (the other option is to define an
> > acknowledgement like PPTP WHEN such a need it felt).
> >
> > Please send  your comments to  gre@ops.ietf.org mailing list.  you can
> > subscribe   to   this   mailing   list   by  sending   an   email   to
> > request-gre@ops.ietf.org
> >
> > Thanks
> > Gopal
> >
> > Network Working Group                                      Gopal Dommety
> > INTERNET DRAFT                                             cisco Systems
> > March 2000
> >
> > Expires October 2000
> >
> >                 Key and Sequence Number Extensions to GRE
> >                     draft-dommety-gre-ext-00.txt
> >
> > Status of this Memo
> >
> >    This document is a submission by the Network Working Group of the
> >    Internet Engineering Task Force (IETF).  Comments should be submitted
> >    to the gre@ops.ietf.org mailing list.
> >
> >    Distribution of this memo is unlimited.
> >
> >    This document is an Internet Draft and is in full conformance with
> >    all provisions of Section 10 of RFC2026. Internet Drafts are working
> >    documents of the Internet Engineering Task Force (IETF), its areas,
> >    and working groups. Note that other groups may also distribute
> >    working documents as Internet Drafts.
> >
> >    Internet Drafts are draft documents valid for a maximum of six months
> >    and may be updated, replaced, or obsoleted by other documents at any
> >    time. It is inappropriate to use Internet Drafts as reference
> >    material or to cite them other than as "work in progress."
> >
> >    The list of current Internet-Drafts can be accessed at
> >    http://www.ietf.org/ietf/1id-abstracts.txt.
> >
> >    The list of Internet-Draft Shadow Directories can be accessed at
> >    http://www.ietf.org/shadow.html.
> >
> > Abstract
> >
> >    This  document describes extensions  by which  two fields,  Key and
> > Sequence Number, can be optionally carried in the GRE (Generic Routing
> > Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
> > of an arbitrary network  layer protocol over another arbitrary network
> > layer  protocol.
> >
> > Dommety                                                           [Page 1]
> >
> > Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
> >
> > 1. Introduction
> >
> >    Current specification of Generic Routing Encapsulation [1] specifies
> > a protocol  for encapsulation of  an arbitrary network  layer protocol
> > over another arbitrary network layer protocol. This document describes
> > enhancements  by which  two fields,  Key and  Sequence Number,  can be
> > optionally carried  in the GRE  Header [1]. The  Key field is  used to
> > create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
> > is used to maintain sequence of packets within a GRE Tunnel.
> >
> > 1.1. Specification Language
> >
> >    The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
> >    this document are to be interpreted as described in RFC 2119 [3].
> >
> >    In addition, the following words are used to signify the
> >    requirements of the specification.
> >
> >    Silently discard
> >               The implementation discards the datagram without
> >               further processing, and without indicating an error
> >               to the sender.  The implementation SHOULD provide the
> >               capability of logging the error, including the contents
> >               of the discarded datagram, and SHOULD record the event
> >               in a statistics counter.
> >
> > 2. Extensions to GRE Header
> >
> >    The GRE packet header[1] has the following format:
> >
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |C|       Reserved0       | Ver |         Protocol Type         |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |      Checksum (optional)      |       Reserved1 (Optional)    |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >     The proposed GRE header will have the following format:
> >
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |C| |K|S| Reserved0       | Ver |         Protocol Type         |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |      Checksum (optional)      |       Reserved1 (Optional)    |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |                         Key (optional)                        |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >     |  Rx Sequence Number (Optional)| Tx Sequence Number (Optional) |
> >     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >       Key Present (bit 2)
> >
> >       If the Key Present bit is set to 1, then it indicates that the Key
> >       field is present in the GRE header.  Otherwise, the Key field is
> >       not present in the GRE header.
> >
> >       Sequence Number Present (bit 3)
> >
> >       If the Sequence Number Present bit is set to 1, then it indicates
> >       that the Sequence Number field is present.  Otherwise, the
> >       Sequence Number field is not present in the GRE header.
> >
> >       The  Key and Sequence Present bits are chosen to be  compatible
> >       with RFC 1701 [2].
> >
> > 2.1. Key Field (4 octets)
> >
> >      The Key field contains a  four octet number which was inserted by
> >      the encapsulator. The actual method by which this Key is obtained
> >      is beyond the scope of this document.  Key field is intended to be
> >      used for  creating separate sub-tunnels within a  GRE Tunnel and the
> >      Key field identifies the sub-tunnel.
> >
> > 2.2. Sequence Number (4 octets)
> >
> >     The Sequence Number  field is divided into two  sub-fields (Tx and
> >     Rx sequence number). These subfields are inserted by the encapsulator
> >     when Sequence Number Present Bit is set . Tx Sequence Number  MUST
> >     be used by the receiver to establish the  order in which  packets
> >     have been  transmitted from the  encapsulator  to  the  receiver.
> >     The intended  use  of  the Tx Sequence  Field is  to provide
> >     unreliable and in-order delivery.   If the Key  present bit (bit 2)
> >     is set, the sequence number is specific to the sub-tunnel identified
> >     by the Key field.
> >
> >     The Tx sequence number  value ranges from 1 to  65535. The first
> >     datagram is sent with a Tx sequence number of 1. The Tx sequence
> >     number is thus a free running counter represented modulo 65536,
> >     with the exception that 1 is used when modulo 65536 results in 0
> >     (i.e., rollover to 1 instead of 0). The Rx Sequence number is set to 0.
> >
> > #Q The Rx can be the Tx  sequence number of the last successfully decap
> >   pack.  And  say  that  how  you  use  this  info  is  implementation
> >   dependent.  I am currently saying Rx sequence no
> >   is set to 0. Comments?
> 
> The only possible way this sequence number can be used to support some type of sliding window protocol either for
> 
> flow control or retransmission. I belive this does
> 
> >
> >
> >     When the decapsulator receives an out-of sequence packet it SHOULD
> >     be silently discarded. Additionally, reordering of out-of sequence
> >     packets  MAY  be  performed   by  the  decapsulator  for  improved
> >     performance and  tolerance to reordering in the  network (since the
> >     state of the stateful compression or encryption is reset by packet
> >     loss, it  might help the  performance to tolerate some  amount of
> >     packet reordering in the network by buffering). Exact buffering
> >     schemes are outside the scope
> >     of  this  document. Note that the  Tx sequence number is used to detect
> >     lost packets and/or restore  the original sequence of packets that
> >     may have been reordered during transport.
> >
> >    A packet  is considered an out-of-sequence packet  if the Tx sequence
> >    number  of  the  received packet  is  lesser than or equal to  the Tx
> >    sequence  number   of last  successfully  decapsulated
> >    packet. The  Tx sequence number  of a received message is considered
> >    less than or equal to the last successfully received Tx sequence number
> >    if its value lies in the range of the last received Tx sequence number
> >    and the preceding 32766 values, inclusive.  For example, if the last
> >    successfully received Tx sequence number was 15, then messages with Tx
> >    sequence numbers 1 through 15, as well as 32784 through 65535, would be
> >    considered less than or equal. Such a message would be considered an
> >    out-of-sequence packet and  ignored from processing.
> >
> >     If the received packet is an in-sequence packet, it is successfully
> >     de capsulated. Note that  the TX sequence number is  used to detect
> >     lost packets and/or restore the original sequence of packets (with
> >     buffering) that may have been reordered during transport.
> >
> > #C I have considered trying to  have a different starting point for TX
> > sequence nos  during rollover and initial starting  point.  This would
> > let a node  identify if the other end  reset (like agent advertisement
> > sequence no to identify reboot and normal rollover). This is useful if
> > we keep  turning on  and off  sequence nos option  in a  tunnel. Since
> > there  is no  security it  is easy  for others  to reset  the sequence
> > also. Comments?
> >
> > 3. IANA Considerations
> >
> > 4. Acknowledgments
> >
> > 5. References
> >
> >    [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
> >    "Generic           Routing           Encapsulation          (GRE),"
> >    draft-meyer-gre-update-03.txt, January 2000.
> >
> >    [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
> >    Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems,
> >    October 1994.
> >
> >    [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
> >        Levels", RFC 2119, March 1997.
> >
> > Dommety                                                 [Page 4]
> >
> > Internet Draft   Key and Sequence Number extensions to GRE   February 2000
> >
> > Author Information
> >
> >    Gopal Dommety
> >    Cisco Systems, Inc.
> >    170 West Tasman Drive
> >    San Jose, CA 95134
> >    e-mail: gdommety@cisco.com
> >
> > Dommety
> >
> > Thank You.
> > Regards,
> > Gopal
> > -------------------------------------------------------------------------------------------------------------
> >
> > Gopal Dommety
> > 408 525 1404
> > gdommety@cisco.com
> > Cisco Systems, San Jose, CA, 95051
> 


From owner-l2tp@ipsec.org  Mon Mar 13 01:47:05 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28411
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 01:47:04 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id UAA25511; Sun, 12 Mar 2000 20:33:01 -0800 (PST)
Received: from fsnt.future.futusoft.com ([203.197.140.35]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id UAA25507 for <l2tp@ipsec.org>; Sun, 12 Mar 2000 20:32:47 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000275932@fsnt.future.futusoft.com> for <l2tp@ipsec.org>;
 Mon, 13 Mar 2000 11:13:44 +0530
Received: from aruljp.future.futsoft.com (aruljp.future.futsoft.com [10.0.12.18]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id KAA08843 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 10:53:13 +0530
Received: by localhost with Microsoft MAPI; Mon, 13 Mar 2000 11:04:55 +0530
Message-Id: <01BF8CDB.F69D65A0.aruljp@future.futsoft.com>
From: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Reply-To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RADIUS Accounting
Date: Mon, 13 Mar 2000 11:04:53 +0530
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hi,

Please clear the following doubt.

   The RADIUS Accounting RFC specifies that the Acct-Session-Id attribute is mandatory. 
When the LAC boots up it may send an Accounting On to Radius Server. If no user has logged in
what session-id is to be used in this packet.

Thanks in advance,

Regards,
Arul.



From owner-l2tp@ipsec.org  Mon Mar 13 03:44:09 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21799
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 03:44:08 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id WAA25677; Sun, 12 Mar 2000 22:24:05 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA25672 for <l2tp@ipsec.org>; Sun, 12 Mar 2000 22:22:30 -0800 (PST)
Received: from gdommety-pc2 (gdommety-dsl3.cisco.com [10.19.17.140])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id XAA13355;
	Sun, 12 Mar 2000 23:24:14 -0800 (PST)
Message-Id: <200003130724.XAA13355@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Sun, 12 Mar 2000 23:36:52 -0800
To: "Ajoy Singh" <ASINGH1@email.mot.com>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
Cc: MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, gre@ops.ietf.org, l2tp@ipsec.org
In-Reply-To: <38C92FF2.1F789629@email.mot.com>
References: <200003092018.MAA17086@omega.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

At 11:25 AM 10/03/00 -0600, Ajoy Singh wrote:
>Hello Gopal,
>
>Here is couple of questions i have regarding the attached GRE draft.  I have not participated in previous
>discussion of GRE, so i am
>not aware of any decision made by IESG regarding this respect.
>
>1. What is the Value of Version number field of  proposed GRE header ?  Is it 0 or something else ?  Does it mean

The Version is 0.

>that all existing GRE implementations need to change to support this header format to be standard compliant?  I
>was hoping that we can use different version number to support the new extensions and that way we do not require
>to change existing deployment of GRE. This way any network element can discard right away the GRE packets which
>it does not support ?

This is an addendum to the draft-meyers. Using a different version number will definetly make it easy. If the version number is 
to be changed then we have to change it in  draft-meyers. 

We should definetly not need to change all existing GRE implementations.

>2. In GRE header format you have  specified RX Sequence number which seems to me same as ack sequence number of
>PPTP GRE. Why we need similar thing represented in two different way in two different standards ?

We can  use the all the four octects for the Transmit sequence as in PPTP and if it is determined that we need an acknowledgement
feild, we can think about the acknowledgement extension. I will make that change.

BTW: PPTP uses the value of 1 for Version number.
 


>
>thanks,
>ajoy
>
>Gopal Dommety wrote:
>
>> Hello:
>>
>> I am  attaching the  GRE addendum/extensions.  As  you go  through the
>>  draft at places identified by # there are request for comments. I have
>> split the sequence no into two subfeilds (the other option is to define an
>> acknowledgement like PPTP WHEN such a need it felt).
>>
>> Please send  your comments to  gre@ops.ietf.org mailing list.  you can
>> subscribe   to   this   mailing   list   by  sending   an   email   to
>> request-gre@ops.ietf.org
>>
>> Thanks
>> Gopal
>>
>> Network Working Group                                      Gopal Dommety
>> INTERNET DRAFT                                             cisco Systems
>> March 2000
>>
>> Expires October 2000
>>
>>                 Key and Sequence Number Extensions to GRE
>>                     draft-dommety-gre-ext-00.txt
>>
>> Status of this Memo
>>
>>    This document is a submission by the Network Working Group of the
>>    Internet Engineering Task Force (IETF).  Comments should be submitted
>>    to the gre@ops.ietf.org mailing list.
>>
>>    Distribution of this memo is unlimited.
>>
>>    This document is an Internet Draft and is in full conformance with
>>    all provisions of Section 10 of RFC2026. Internet Drafts are working
>>    documents of the Internet Engineering Task Force (IETF), its areas,
>>    and working groups. Note that other groups may also distribute
>>    working documents as Internet Drafts.
>>
>>    Internet Drafts are draft documents valid for a maximum of six months
>>    and may be updated, replaced, or obsoleted by other documents at any
>>    time. It is inappropriate to use Internet Drafts as reference
>>    material or to cite them other than as "work in progress."
>>
>>    The list of current Internet-Drafts can be accessed at
>>    http://www.ietf.org/ietf/1id-abstracts.txt.
>>
>>    The list of Internet-Draft Shadow Directories can be accessed at
>>    http://www.ietf.org/shadow.html.
>>
>> Abstract
>>
>>    This  document describes extensions  by which  two fields,  Key and
>> Sequence Number, can be optionally carried in the GRE (Generic Routing
>> Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
>> of an arbitrary network  layer protocol over another arbitrary network
>> layer  protocol.
>>
>> Dommety                                                           [Page 1]
>>
>> Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
>>
>> 1. Introduction
>>
>>    Current specification of Generic Routing Encapsulation [1] specifies
>> a protocol  for encapsulation of  an arbitrary network  layer protocol
>> over another arbitrary network layer protocol. This document describes
>> enhancements  by which  two fields,  Key and  Sequence Number,  can be
>> optionally carried  in the GRE  Header [1]. The  Key field is  used to
>> create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
>> is used to maintain sequence of packets within a GRE Tunnel.
>>
>> 1.1. Specification Language
>>
>>    The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>>    this document are to be interpreted as described in RFC 2119 [3].
>>
>>    In addition, the following words are used to signify the
>>    requirements of the specification.
>>
>>    Silently discard
>>               The implementation discards the datagram without
>>               further processing, and without indicating an error
>>               to the sender.  The implementation SHOULD provide the
>>               capability of logging the error, including the contents
>>               of the discarded datagram, and SHOULD record the event
>>               in a statistics counter.
>>
>> 2. Extensions to GRE Header
>>
>>    The GRE packet header[1] has the following format:
>>
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     |C|       Reserved0       | Ver |         Protocol Type         |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     |      Checksum (optional)      |       Reserved1 (Optional)    |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>     The proposed GRE header will have the following format:
>>
>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     |C| |K|S| Reserved0       | Ver |         Protocol Type         |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     |      Checksum (optional)      |       Reserved1 (Optional)    |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     |                         Key (optional)                        |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     |  Rx Sequence Number (Optional)| Tx Sequence Number (Optional) |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>       Key Present (bit 2)
>>
>>       If the Key Present bit is set to 1, then it indicates that the Key
>>       field is present in the GRE header.  Otherwise, the Key field is
>>       not present in the GRE header.
>>
>>       Sequence Number Present (bit 3)
>>
>>       If the Sequence Number Present bit is set to 1, then it indicates
>>       that the Sequence Number field is present.  Otherwise, the
>>       Sequence Number field is not present in the GRE header.
>>
>>       The  Key and Sequence Present bits are chosen to be  compatible
>>       with RFC 1701 [2].
>>
>> 2.1. Key Field (4 octets)
>>
>>      The Key field contains a  four octet number which was inserted by
>>      the encapsulator. The actual method by which this Key is obtained
>>      is beyond the scope of this document.  Key field is intended to be
>>      used for  creating separate sub-tunnels within a  GRE Tunnel and the
>>      Key field identifies the sub-tunnel.
>>
>> 2.2. Sequence Number (4 octets)
>>
>>     The Sequence Number  field is divided into two  sub-fields (Tx and
>>     Rx sequence number). These subfields are inserted by the encapsulator
>>     when Sequence Number Present Bit is set . Tx Sequence Number  MUST
>>     be used by the receiver to establish the  order in which  packets
>>     have been  transmitted from the  encapsulator  to  the  receiver.
>>     The intended  use  of  the Tx Sequence  Field is  to provide
>>     unreliable and in-order delivery.   If the Key  present bit (bit 2)
>>     is set, the sequence number is specific to the sub-tunnel identified
>>     by the Key field.
>>
>>     The Tx sequence number  value ranges from 1 to  65535. The first
>>     datagram is sent with a Tx sequence number of 1. The Tx sequence
>>     number is thus a free running counter represented modulo 65536,
>>     with the exception that 1 is used when modulo 65536 results in 0
>>     (i.e., rollover to 1 instead of 0). The Rx Sequence number is set to 0.
>>
>> #Q The Rx can be the Tx  sequence number of the last successfully decap
>>   pack.  And  say  that  how  you  use  this  info  is  implementation
>>   dependent.  I am currently saying Rx sequence no
>>   is set to 0. Comments?
>
>The only possible way this sequence number can be used to support some type of sliding window protocol either for
>
>flow control or retransmission. I belive this does
>
>>
>>
>>     When the decapsulator receives an out-of sequence packet it SHOULD
>>     be silently discarded. Additionally, reordering of out-of sequence
>>     packets  MAY  be  performed   by  the  decapsulator  for  improved
>>     performance and  tolerance to reordering in the  network (since the
>>     state of the stateful compression or encryption is reset by packet
>>     loss, it  might help the  performance to tolerate some  amount of
>>     packet reordering in the network by buffering). Exact buffering
>>     schemes are outside the scope
>>     of  this  document. Note that the  Tx sequence number is used to detect
>>     lost packets and/or restore  the original sequence of packets that
>>     may have been reordered during transport.
>>
>>    A packet  is considered an out-of-sequence packet  if the Tx sequence
>>    number  of  the  received packet  is  lesser than or equal to  the Tx
>>    sequence  number   of last  successfully  decapsulated
>>    packet. The  Tx sequence number  of a received message is considered
>>    less than or equal to the last successfully received Tx sequence number
>>    if its value lies in the range of the last received Tx sequence number
>>    and the preceding 32766 values, inclusive.  For example, if the last
>>    successfully received Tx sequence number was 15, then messages with Tx
>>    sequence numbers 1 through 15, as well as 32784 through 65535, would be
>>    considered less than or equal. Such a message would be considered an
>>    out-of-sequence packet and  ignored from processing.
>>
>>     If the received packet is an in-sequence packet, it is successfully
>>     de capsulated. Note that  the TX sequence number is  used to detect
>>     lost packets and/or restore the original sequence of packets (with
>>     buffering) that may have been reordered during transport.
>>
>> #C I have considered trying to  have a different starting point for TX
>> sequence nos  during rollover and initial starting  point.  This would
>> let a node  identify if the other end  reset (like agent advertisement
>> sequence no to identify reboot and normal rollover). This is useful if
>> we keep  turning on  and off  sequence nos option  in a  tunnel. Since
>> there  is no  security it  is easy  for others  to reset  the sequence
>> also. Comments?
>>
>> 3. IANA Considerations
>>
>> 4. Acknowledgments
>>
>> 5. References
>>
>>    [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
>>    "Generic           Routing           Encapsulation          (GRE),"
>>    draft-meyer-gre-update-03.txt, January 2000.
>>
>>    [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
>>    Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems,
>>    October 1994.
>>
>>    [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
>>        Levels", RFC 2119, March 1997.
>>
>> Dommety                                                 [Page 4]
>>
>> Internet Draft   Key and Sequence Number extensions to GRE   February 2000
>>
>> Author Information
>>
>>    Gopal Dommety
>>    Cisco Systems, Inc.
>>    170 West Tasman Drive
>>    San Jose, CA 95134
>>    e-mail: gdommety@cisco.com
>>
>> Dommety
>>
>> Thank You.
>> Regards,
>> Gopal
>> -------------------------------------------------------------------------------------------------------------
>>
>> Gopal Dommety
>> 408 525 1404
>> gdommety@cisco.com
>> Cisco Systems, San Jose, CA, 95051
> 
Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Mon Mar 13 03:53:02 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24492
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 03:53:01 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id WAA25711; Sun, 12 Mar 2000 22:41:23 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA25707 for <l2tp@ipsec.org>; Sun, 12 Mar 2000 22:40:59 -0800 (PST)
Received: from gdommety-pc2 (gdommety-dsl3.cisco.com [10.19.17.140])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id XAA14315;
	Sun, 12 Mar 2000 23:42:51 -0800 (PST)
Message-Id: <200003130742.XAA14315@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Sun, 12 Mar 2000 23:55:23 -0800
To: "Frederick N. Chase" <fnc@mitre.org>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: New GRE Draft  Extensions
Cc: ietf-ppp@merit.edu, l2tp@ipsec.org, gre@ops.ietf.org,
        mobile-ip@standards.nortelnetworks.com, dmm@cisco.com,
        Erik.Nordmark@eng.sun.com, fred@cisco.com, udlr@sophia.inria.fr,
        narten@raleigh.ibm.com
In-Reply-To: <38C94502.7D3D5026@mitre.org>
References: <200003092046.MAA21507@omega.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

At 01:54 PM 10/03/00 -0500, Frederick N. Chase wrote:
>Re:  Key and Sequence Number Extensions to GRE
>                    
>                    
>                    
>The proposed use of two previously-reserved header bits
>in  draft-dommety-gre-ext-00.txt 
>differ in a fundamental way.
>
>The proposed use of a reserved bit as a
>"Sequence Number Present" bit is a
>potentially-beneficial modifier
>on encapsulator/decapsulator behavior and therefore
>seems to me to be advisable or at least not inadvisable.
>
>The proposed use of a reserved bit as a
>"Key Present" bit does not affect (narrowly construed)
>encapsulator/decapsulator behavior but rather
>concerns the processor of the encapsulated or decapsulated 
>data.  This proposal seems to me to be inadvisable.
>
>Acceptance of the "Key Present" proposal unnecessarily 
>encumbers some other 
>processor of encapsulated or decapsulated data
>which might like to have an optional extra 32 bits for some purpose
>where the terms "Key and "sub-tunnel" would be 
>confusing and inappropriate.

Fred,

	I am not sure of the concern. Would appreciate if you could explain.
Is your concern that we have to maintain a  Sequence number per Key when both are present? Or that
earlier (in RFC1701) it was supposed to be  used by the receiver to authenticate
      the source of the packet?

Thanks
Gopal




>
>
>   -Fred Chase
> 
Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Mon Mar 13 10:53:01 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27145
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 10:52:58 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id FAA27364; Mon, 13 Mar 2000 05:41:38 -0800 (PST)
Received: from sigma.cisco.com (sigma.cisco.com [171.69.63.142]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA27360 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 05:41:27 -0800 (PST)
Received: (from dmm@localhost)
	by sigma.cisco.com (8.8.8-Cisco List Logging/8.8.8) id GAA12264;
	Mon, 13 Mar 2000 06:43:06 -0800 (PST)
From: David Meyer <dmm@cisco.com>
Message-Id: <200003131443.GAA12264@sigma.cisco.com>
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
To: gdommety@cisco.com (Gopal Dommety)
Date: Mon, 13 Mar 2000 06:43:06 -0800 (PST)
Cc: ASINGH1@email.mot.com (Ajoy Singh), MOBILE-IP@STANDARDS.NORTELNETWORKS.COM,
        gre@ops.ietf.org, l2tp@ipsec.org
In-Reply-To: <200003130724.XAA13355@omega.cisco.com> from "Gopal Dommety" at Mar 12, 2000 11:36:52 PM
X-Mailer: ELM [version 2.5 PL1]
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


> This is an addendum to the draft-meyers. Using a different version number will definetly make it easy. If the version number is 
> to be changed then we have to change it in  draft-meyers. 

	We've been through this and decided not to change the
	version number.

> We should definetly not need to change all existing GRE implementations.

	right, should be backwardly compatable.


	Dave


From owner-l2tp@ipsec.org  Mon Mar 13 12:30:35 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06553
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 12:30:35 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id HAA27524; Mon, 13 Mar 2000 07:22:32 -0800 (PST)
Received: from eins.siemens.at (eins.siemens.at [193.81.246.11]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA27520; Mon, 13 Mar 2000 07:22:18 -0800 (PST)
Received: from scesie13.sie.siemens.at (forix-hme0 [10.1.140.2])
	by eins.siemens.at  with ESMTP id RAA00923;
	Mon, 13 Mar 2000 17:18:08 +0100 (MET)
Received: (from smap@localhost)
	by scesie13.sie.siemens.at (8.9.3/8.9.3) id RAA19454;
	Mon, 13 Mar 2000 17:24:39 +0100 (MET)
Received: from vies141a.sie.siemens.at(195.1.196.56) by scesie13 via smap (V2.0beta)
	id xma019314; Mon, 13 Mar 00 17:24:20 +0100
Received: by vies141a.sie.siemens.at with Internet Mail Service (5.5.2650.21)
	id <GPNBG3NX>; Mon, 13 Mar 2000 17:24:19 +0100
Message-ID: <D9F2B9CD7BD5D21196BC0800060D9ED601EFBCF5@vies186a.sie.siemens.at>
From: Klausberger Walter <walter.klausberger@siemens.at>
To: l2tp@ipsec.org, l2tp@SailPix.com
Subject: L2TP MIB
Date: Mon, 13 Mar 2000 17:24:18 +0100
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

Hi everybody,

Can someone tell me about the status of the L2TP MIB. The tunnel MIB is RFC
since last year and the L2TP MIB already had it's last call. But afterwards
all I saw was silence...

with best regards
Walter Klausberger
Siemens Austria


From owner-l2tp@ipsec.org  Mon Mar 13 13:34:00 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02595
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 13:33:59 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id IAA27703; Mon, 13 Mar 2000 08:37:39 -0800 (PST)
Received: from sigma.cisco.com (sigma.cisco.com [171.69.63.142]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA27699 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 08:37:27 -0800 (PST)
Received: (from dmm@localhost)
	by sigma.cisco.com (8.8.8-Cisco List Logging/8.8.8) id JAA00842;
	Mon, 13 Mar 2000 09:39:02 -0800 (PST)
From: David Meyer <dmm@cisco.com>
Message-Id: <200003131739.JAA00842@sigma.cisco.com>
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
To: gdommety@cisco.com (Gopal Dommety)
Date: Mon, 13 Mar 2000 09:39:01 -0800 (PST)
Cc: dmm@cisco.com (David Meyer), ASINGH1@email.mot.com (Ajoy Singh),
        MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, gre@ops.ietf.org,
        l2tp@ipsec.org
In-Reply-To: <200003131737.JAA25646@omega.cisco.com> from "Gopal Dommety" at Mar 13, 2000 09:50:03 AM
X-Mailer: ELM [version 2.5 PL1]
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

> >
> >	We've been through this and decided not to change the
> >	version number.
> 
> I am not suggesting we change the version number. I was clarifying that we cannot change the version no in draft-dommety. If at all it is done
> it has to be done in draft-meyers.
> 

	Sure. But we don't plan to do that.

	Dave


From owner-l2tp@ipsec.org  Mon Mar 13 13:35:51 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03399
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 13:35:50 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id IAA27695; Mon, 13 Mar 2000 08:35:49 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA27691 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 08:35:31 -0800 (PST)
Received: from gdommety-pc2 (gdommety-dsl3.cisco.com [10.19.17.140])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id JAA25646;
	Mon, 13 Mar 2000 09:37:13 -0800 (PST)
Message-Id: <200003131737.JAA25646@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Mon, 13 Mar 2000 09:50:03 -0800
To: David Meyer <dmm@cisco.com>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
Cc: ASINGH1@email.mot.com (Ajoy Singh), MOBILE-IP@STANDARDS.NORTELNETWORKS.COM,
        gre@ops.ietf.org, l2tp@ipsec.org
In-Reply-To: <200003131443.GAA12264@sigma.cisco.com>
References: <200003130724.XAA13355@omega.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk


Dave, 



At 06:43 AM 13/03/00 -0800, David Meyer wrote:
>
>> This is an addendum to the draft-meyers. Using a different version number will definetly make it easy. If the version number is 
>> to be changed then we have to change it in  draft-meyers. 
>
>	We've been through this and decided not to change the
>	version number.

I am not suggesting we change the version number. I was clarifying that we cannot change the version no in draft-dommety. If at all it is done
it has to be done in draft-meyers.

Thanks
Gopal


>
>> We should definetly not need to change all existing GRE implementations.
>
>	right, should be backwardly compatable.
>
>
>	Dave
> 
Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Mon Mar 13 13:49:00 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08200
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 13:48:59 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id IAA27775; Mon, 13 Mar 2000 08:50:01 -0800 (PST)
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA27768; Mon, 13 Mar 2000 08:49:47 -0800 (PST)
Received: from acc.com (unk105122.acc.com [129.192.105.122])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id JAA07816;
	Mon, 13 Mar 2000 09:55:03 -0800 (PST)
Message-ID: <38CD2B7B.9735E371@acc.com>
Date: Mon, 13 Mar 2000 09:55:07 -0800
From: Evan Caves <evan@acc.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Klausberger Walter <walter.klausberger@siemens.at>
CC: l2tp@ipsec.org, l2tp@SailPix.com
Subject: Re: L2TP MIB
References: <D9F2B9CD7BD5D21196BC0800060D9ED601EFBCF5@vies186a.sie.siemens.at>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@SailPix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

An updated L2TP MIB was published last week. Changes to the MIB were mostly
driven
from WG conversations after WG last call had closed. We encourage everyone to
review
the latest update and post comments. If all goes well we will ask Mark to issue
another WG
last call.

evan
-

Klausberger Walter wrote:

> Hi everybody,
>
> Can someone tell me about the status of the L2TP MIB. The tunnel MIB is RFC
> since last year and the L2TP MIB already had it's last call. But afterwards
> all I saw was silence...
>
> with best regards
> Walter Klausberger
> Siemens Austria



From owner-l2tp@ipsec.org  Mon Mar 13 16:17:13 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07312
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 16:17:12 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id LAA28151; Mon, 13 Mar 2000 11:07:45 -0800 (PST)
Received: from template.redback.com (chef.redbacknetworks.com [155.53.190.24]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA28146 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 11:07:38 -0800 (PST)
Received: (from carrel@localhost)
	by template.redback.com (8.8.8/8.8.8) id MAA19683
	for l2tp@ipsec.org; Mon, 13 Mar 2000 12:10:10 -0800 (PST)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA20263 for <l2tp@ipsec.org>; Fri, 10 Mar 2000 13:03:31 -0800 (PST)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id RAA31740;
	Fri, 10 Mar 2000 17:04:54 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.82.31])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id RAA35136;
	Fri, 10 Mar 2000 17:04:57 -0500
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id RAA23668; Fri, 10 Mar 2000 17:04:39 -0500
Message-Id: <200003102204.RAA23668@rotala.raleigh.ibm.com>
To: Rene Tio <tor@redback.com>
cc: Ajoy Singh <ASINGH1@email.mot.com>, Gopal Dommety <gdommety@cisco.com>,
        MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, gre@ops.ietf.org,
        l2tp@ipsec.org
Reply-To: gre@ops.ietf.org
Subject: Re: [MOBILE-IP] New GRE Draft Extensions 
In-Reply-To: Message from Rene Tio <tor@redback.com> 
   of "Fri, 10 Mar 2000 11:08:26 PST." <20000310110826.B16343@redback.com> 
Date: Fri, 10 Mar 2000 17:04:39 -0500
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Folks,

I'm redirecting followups to the gre list. To join:

    majordomo@ops.ietf.org
    subscribe gre

Note: there are folks interested in gre outside of mobile-ip. The UDLR
WG has also expressed an interest in this area.

> I do not know if the IESG figures into this since GRE is
> informational. However I would like to know the reason behind the
> updates because draft-meyer + draft-dommety looks pretty close to
> RFC 1701.  The changes appear to be the semantics of the key field,
> which was somewhat semantic free before since its use as an
> authenticator was always suspect, and the split sequence number
> field.  What's the use of deprecating some fields in one draft and
> extending it with the same deprecated fields in another draft?

RFC 1701 is informational. It cannot be referenced by standards track
documents in a normative way.

draft-meyer-gre-update-03.txt has been approved as a Proposed Standard
by the IESG an will be out as an RFC any day now. This document is
backwards compatable with 1701 in the sense that existing
implementations of 1701 are already compliant with the new
standard. However, draft-meyer-gre-update does not include some of the
more exotic extensions that 1701 has. Thus, the new GRE document isn't
for everyone, as it doesn't include the key and sequence
fields. meyer-gre-update is just the basics, no fluff.

The purpose of draft-dommety is to define some new options to GRE that
may in fact look suprisingly like some of the fields in 1701 that
don't appear in draft-meyer-gre-update. One problem with 1701's
definition of those fields is that they are underspecified (you can't
implement them from 1701) and its not even clear whether everyone
would agree on what semantics those fields should have. draft-dommety
is intended to find consensus on what those other fields should be (at
least from the perspectives of mobile IP).

Questions like should GRE extensions use a new version number, etc.,
need to hashed out on the gre list. 

Thomas



From owner-l2tp@ipsec.org  Mon Mar 13 17:37:40 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06347
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 17:37:38 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id MAA28548; Mon, 13 Mar 2000 12:42:48 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA28544 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 12:42:30 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id NAA16808;
	Mon, 13 Mar 2000 13:44:56 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id NAA15299; Mon, 13 Mar 2000 13:44:55 -0800 (PST)
Date: Mon, 13 Mar 2000 13:44:55 -0800
From: Rene Tio <tor@redback.com>
To: Gopal Dommety <gdommety@cisco.com>
Cc: David Meyer <dmm@cisco.com>, Ajoy Singh <ASINGH1@email.mot.com>,
        MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, gre@ops.ietf.org,
        l2tp@ipsec.org
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
Message-ID: <20000313134455.C14355@redback.com>
References: <200003130724.XAA13355@omega.cisco.com> <200003131443.GAA12264@sigma.cisco.com> <200003131737.JAA25646@omega.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200003131737.JAA25646@omega.cisco.com>; from gdommety@cisco.com on Mon, Mar 13, 2000 at 09:50:03AM -0800
Sender: owner-l2tp@sailpix.com
Precedence: bulk

On Mon, Mar 13, 2000 at 09:50:03AM -0800, Gopal Dommety wrote:
> At 06:43 AM 13/03/00 -0800, David Meyer wrote:
> >
> >> This is an addendum to the draft-meyers. Using a different version
> >> number will definetly make it easy. If the version number is 
> >> to be changed then we have to change it in  draft-meyers. 
> >
> >	We've been through this and decided not to change the
> >	version number.
> 
> I am not suggesting we change the version number. I was clarifying that we
> cannot change the version no in draft-dommety. If at all it is done
> it has to be done in draft-meyers.
> 

I don't see why this has to be so.  draft-meyer is pretty much completely
backward compatible to 1701, whereas draft-dommety isn't.  Thus draft-meyer
doesn't require a version number bump but draft-dommety in its original form
did.

However, if the Sequence Number field were changed to 32 bits, as Gopal
recently suggested, and the only change was to better define the behaviour
of the Sequence Number field, then the need for bumping GRE versions I feel
would be unnecessary.

If, however, you are going to add an Ack sequence number, *and* use the Key
field as some form of tunnel demux, then it's beginning to look a whole lot
like PPTP and I'd probably suggest splitting out the PPTP GRE portions into
a separate draft and making draft-dommety look like it (and bump the version
numbers, eck).

This discussion is sounding very circular at the moment.

Cheers,
Rene


From owner-l2tp@ipsec.org  Mon Mar 13 18:23:34 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22028
	for <l2tpext-archive@odin.ietf.org>; Mon, 13 Mar 2000 18:23:30 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id NAA28643; Mon, 13 Mar 2000 13:31:18 -0800 (PST)
Received: from sigma.cisco.com (sigma.cisco.com [171.69.63.142]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA28639 for <l2tp@ipsec.org>; Mon, 13 Mar 2000 13:31:05 -0800 (PST)
Received: (from dmm@localhost)
	by sigma.cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA25511;
	Mon, 13 Mar 2000 14:32:54 -0800 (PST)
From: David Meyer <dmm@cisco.com>
Message-Id: <200003132232.OAA25511@sigma.cisco.com>
Subject: Re: [MOBILE-IP] New GRE Draft  Extensions
To: tor@redback.com (Rene Tio)
Date: Mon, 13 Mar 2000 14:32:54 -0800 (PST)
Cc: gdommety@cisco.com (Gopal Dommety), dmm@cisco.com (David Meyer),
        ASINGH1@email.mot.com (Ajoy Singh),
        MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, gre@ops.ietf.org,
        l2tp@ipsec.org
In-Reply-To: <20000313134455.C14355@redback.com> from "Rene Tio" at Mar 13, 2000 01:44:55 PM
X-Mailer: ELM [version 2.5 PL1]
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

> However, if the Sequence Number field were changed to 32 bits, as Gopal
> recently suggested, and the only change was to better define the behaviour
> of the Sequence Number field, then the need for bumping GRE versions I feel
> would be unnecessary.

	This is my feeling as well.
> 
> If, however, you are going to add an Ack sequence number, *and* use the Key
> field as some form of tunnel demux, then it's beginning to look a whole lot
> like PPTP and I'd probably suggest splitting out the PPTP GRE portions into
> a separate draft and making draft-dommety look like it (and bump the version
> numbers, eck).

	Ditto.


	Dave


From owner-l2tp@ipsec.org  Tue Mar 14 22:14:51 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22608
	for <l2tpext-archive@odin.ietf.org>; Tue, 14 Mar 2000 22:14:50 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id RAA01080; Tue, 14 Mar 2000 17:51:45 -0800 (PST)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA01069 for <l2tp@ipsec.org>; Tue, 14 Mar 2000 17:51:26 -0800 (PST)
Received: from cwc.nus.edu.sg ([172.16.172.16])
	by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with ESMTP id JAA03207
	for <l2tp@ipsec.org>; Wed, 15 Mar 2000 09:50:53 +0800 (SGT)
Message-ID: <38CEED17.6EB89B46@cwc.nus.edu.sg>
Date: Wed, 15 Mar 2000 09:53:27 +0800
From: Wang Xiangqian <wangxq@cwc.nus.edu.sg>
Organization: National University of Singpaore
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en,zh-TW,zh-CN,zh
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: free l2tp implementation for linux?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Is there any free l2tp implementation for linux besides Mark Spenser's
found at http://www.marko.net/l2tp/ ?

Thanks a lot

Wang Xiangqian



From owner-l2tp@ipsec.org  Fri Mar 17 05:58:58 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27921
	for <l2tpext-archive@odin.ietf.org>; Fri, 17 Mar 2000 05:58:56 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id AAA07273; Fri, 17 Mar 2000 00:57:17 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id AAA07268 for <l2tp@ipsec.org>; Fri, 17 Mar 2000 00:55:54 -0800 (PST)
Received: from gdommety-pc2 (gdommety-dsl4.cisco.com [10.19.17.141])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id AAA15902;
	Fri, 17 Mar 2000 00:53:37 -0800 (PST)
Message-Id: <200003170853.AAA15902@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Fri, 17 Mar 2000 01:06:27 -0800
To: gre@ops.ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: GRE Extensions (Modified)
Cc: udlr@sophia.inria.fr, msdp@antc.uoregon.edu, ipsec@lists.tislabs.com,
        MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, l2tp@ipsec.org, tsgp@3gpp2.org,
        tsga@3gpp2.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hello:

I have changed the sequence no  to be 4 bytes.  The changes request by
most have been made.

A remining issue is regarding  the behaviour when both sequence no and
the Key are present. There are two options:

1. Have sequence no  per Key.  This will give  better granularity with
   added complexity of implementation.

2. Sequence no for the tunnel irrespective of the Key. 

Let me know your opinion.

Thanks
Gopal


Network Working Group				      Gopal Dommety
INTERNET DRAFT                                        cisco Systems
Category: Standards Track                             March 2000  
Title:  draft-dommety-gre-ext-01.txt                  

Expires October 2000

		Key and Sequence Number Extensions to GRE
		    draft-dommety-gre-ext-01.txt

Status of this Memo

   This document is a submission by the Network Working Group of the
   Internet Engineering Task Force (IETF).  Comments should be submitted
   to the gre@ops.ietf.org mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet Draft and is in full conformance with
   all provisions of Section 10 of RFC2026. Internet Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and working groups. Note that other groups may also distribute
   working documents as Internet Drafts.

   Internet Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.
   
Abstract
   
   This  document describes extensions  by which  two fields,  Key and
Sequence Number, can be optionally carried in the GRE (Generic Routing
Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
of an arbitrary network  layer protocol over another arbitrary network
layer  protocol. 

Dommety		                                                  [Page 1]

Internet Draft  Key and Sequence Number Extensions to GRE  February 2000

1. Introduction

   Current specification of Generic Routing Encapsulation [1] specifies
a protocol  for encapsulation of  an arbitrary network  layer protocol
over another arbitrary network layer protocol. This document describes
enhancements  by which  two fields,  Key and  Sequence Number,  can be
optionally carried  in the GRE  Header [1]. The  Key field is  used to
create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
is used to maintain sequence of packets within a GRE Tunnel.

1.1. Specification Language

   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC 2119 [3].

   In addition, the following words are used to signify the 
   requirements of the specification.  

   Silently discard
              The implementation discards the datagram without
              further processing, and without indicating an error
              to the sender.  The implementation SHOULD provide the
              capability of logging the error, including the contents
              of the discarded datagram, and SHOULD record the event
              in a statistics counter.

2. Extensions to GRE Header

   The GRE packet header[1] has the following format:

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |C|       Reserved0       | Ver |         Protocol Type         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      Checksum (optional)      |       Reserved1 (Optional)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


    The proposed GRE header will have the following format:

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |C| |K|S| Reserved0       | Ver |         Protocol Type         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      Checksum (optional)      |       Reserved1 (Optional)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         Key (optional)                        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                 Sequence Number (Optional)                    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      

      Key Present (bit 2)

      If the Key Present bit is set to 1, then it indicates that the Key
      field is present in the GRE header.  Otherwise, the Key field is
      not present in the GRE header.

      Sequence Number Present (bit 3)

      If the Sequence Number Present bit is set to 1, then it indicates
      that the Sequence Number field is present.  Otherwise, the
      Sequence Number field is not present in the GRE header.

      The  Key and Sequence Present bits are chosen to be  compatible 
      with RFC 1701 [2].
 
2.1. Key Field (4 octets)

     The Key field contains a  four octet number which was inserted by
     the encapsulator. The actual method by which this Key is obtained
     is beyond the scope of this document.  Key field is intended to be
     used for  creating separate sub-tunnels within a  GRE Tunnel and the
     Key field identifies the sub-tunnel. 

2.2. Sequence Number (4 octets)
 
    The Sequence Number field is a  four byte feild and is inserted by
    the  encapsulator when  Sequence Number  Present Bit  is set. The
    Sequence  Number MUST  be used  by the  receiver to  establish the
    order in which packets have been transmitted from the encapsulator
    to the receiver.  The intended use  of the Sequence Field is to
    provide unreliable and in-order  delivery.  If the Key present bit
    (bit 2) is set, the  sequence number is specific to the sub-tunnel
    identified by the Key field. Note that packets without the sequence
     bit set can be sent in between packets with the sequence bit set.

    The  sequence number  value ranges from 1 to  2**32-1. The first 
    datagram is sent with a sequence number of 1. The  sequence 
    number is thus a free running counter represented modulo 2**32, 
    with the exception that 1 is used when modulo 2**32 results in 0 
    (i.e., rollover to 1 instead of 0). 

    When the decapsulator receives an out-of sequence packet it SHOULD
    be silently discarded. Additionally, reordering of out-of sequence
    packets  MAY  be  performed   by  the  decapsulator  for  improved
    performance and  tolerance to reordering in the  network (since the
    state of the stateful compression or encryption is reset by packet
    loss, it  might help the  performance to tolerate some  amount of
    packet reordering in the network by buffering). Exact buffering 
    schemes are outside the scope of  this  document. Note that the  
    sequence number is used to detect
    lost packets and/or restore  the original sequence of packets that
    may have been reordered during transport.

   A packet  is considered an out-of-sequence packet  if the  sequence
   number  of  the  received packet  is  lesser than or equal to  the 
   sequence  number   of last  successfully  decapsulated
   packet. The  sequence number  of a received message is considered
   less than or equal to the last successfully received  sequence number 
   if its value lies in the range of the last received  sequence number 
   and the preceding 65534 values, inclusive. 


    If  the   received  packet  is   an  in-sequence  packet,   it  is
    successfully decapsulated.  Note that  the sequence number is used
    to  detect lost packets  and/or restore  the original  sequence of
    packets  (with  buffering) that  may  have  been reordered  during
    transport.   Use of  the  sequence number  option  should be  used
    appropriately; in particular, it is a good idea a avoid using when
    tunneling  protocols  that  have  higher layer  in-order  delivery
    mechanisms or are tolerant to out-of-order delivery. If only at certain 
    instances the protocol being carried in the GRE tunnel requires
    in-sequence delivery, only the corresponding packets encapsulated 
    in a GRE header can be sent with the sequence bit set. Mechanisims 
    to determine which packets need to be sent in-sequence and the 
    signaling mechanisims are outside the scope of this document.




3. IANA Considerations

4. Acknowledgments

 
5. References

   [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
   "Generic           Routing           Encapsulation          (GRE),"
   draft-meyer-gre-update-03.txt, January 2000.

   [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
   Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems, 
   October 1994.

   [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
       Levels", RFC 2119, March 1997.
  

Dommety                                                 [Page 4]

Internet Draft   Key and Sequence Number extensions to GRE   February 2000

Author Information

   Gopal Dommety
   Cisco Systems, Inc.
   170 West Tasman Drive
   San Jose, CA 95134
   e-mail: gdommety@cisco.com

Dommety





Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Fri Mar 17 11:34:14 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09228
	for <l2tpext-archive@odin.ietf.org>; Fri, 17 Mar 2000 11:34:12 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id GAA00249; Fri, 17 Mar 2000 06:41:30 -0800 (PST)
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id GAA00245 for <l2tp@ipsec.org>; Fri, 17 Mar 2000 06:41:15 -0800 (PST)
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by crufty; Fri Mar 17 10:16:39 EST 2000
Received: from king.research.bell-labs.com ([135.1.152.1]) by scummy; Fri Mar 17 10:16:37 EST 2000
Received: from notmafia.research.bell-labs.com.research.bell-labs.com (notmafia [135.1.152.230])
	by king.research.bell-labs.com (Postfix) with SMTP
	id 74DB757042; Fri, 17 Mar 2000 09:16:36 -0600 (CST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Pete McCann <mccap@research.bell-labs.com>
To: Gopal Dommety <gdommety@cisco.com>
Cc: gre@ops.ietf.org, udlr@sophia.inria.fr, msdp@antc.uoregon.edu,
        ipsec@lists.tislabs.com, MOBILE-IP@STANDARDS.NORTELNETWORKS.COM,
        l2tp@ipsec.org, tsgp@3gpp2.org, tsga@3gpp2.org
Subject: GRE Extensions (Modified)
In-Reply-To: <200003170853.AAA15902@omega.cisco.com>
References: <200003170853.AAA15902@omega.cisco.com>
X-Mailer: VM 6.33 under Emacs 19.34.2
Message-Id: <20000317151636.74DB757042@king.research.bell-labs.com>
Date: Fri, 17 Mar 2000 09:16:36 -0600 (CST)
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


The sequence number should definitely be per key!  That way we can
tunnel multiple streams, one per key.  Each needs its own sequencing.

-Pete

Gopal Dommety <gdommety@cisco.com> (GD) writes:

GD> Hello:
GD> I have changed the sequence no  to be 4 bytes.  The changes request by
GD> most have been made.

GD> A remining issue is regarding  the behaviour when both sequence no and
GD> the Key are present. There are two options:

GD> 1. Have sequence no  per Key.  This will give  better granularity with
GD>    added complexity of implementation.

GD> 2. Sequence no for the tunnel irrespective of the Key. 




From owner-l2tp@ipsec.org  Fri Mar 17 12:42:10 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06722
	for <l2tpext-archive@odin.ietf.org>; Fri, 17 Mar 2000 12:42:09 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id HAA00345; Fri, 17 Mar 2000 07:37:07 -0800 (PST)
Received: from jittlov.qualcomm.com (jittlov.qualcomm.com [129.46.50.79]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA00341 for <l2tp@ipsec.org>; Fri, 17 Mar 2000 07:35:35 -0800 (PST)
Received: from rhsu4.qualcomm.com (annex2-p23.qualcomm.com [129.46.85.113]) by jittlov.qualcomm.com (8.9.3/8.9.3/1.0) with SMTP id IAA17317; Fri, 17 Mar 2000 08:11:47 -0800 (PST)
Message-Id: <200003171611.IAA17317@jittlov.qualcomm.com>
X-Sender: rhsu@fezik.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
Date: Fri, 17 Mar 2000 08:12:08 -0800
To: Gopal Dommety <gdommety@cisco.com>, tsgp@3gpp2.org
From: Raymond Hsu <rhsu@qualcomm.com>
Subject: Re: GRE Extensions (Modified)
Cc: udlr@sophia.inria.fr, msdp@antc.uoregon.edu, ipsec@lists.tislabs.com,
        MOBILE-IP@standards.nortelnetworks.com, l2tp@ipsec.org, tsgp@3gpp2.org,
        tsga@3gpp2.org
In-Reply-To: <LYR1158584-196913-2000.03.17-00.58.48--rhsu#qualcomm.com@3
 gpp2.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hi Gopal:

In TR-45.6's R-P interface (aka A10 interface), we may use the first option
in the direction
from the PDSN to the PCF.  In this direction, we've identified scenarios
where some mobiles 
require in-sequence delivery and some don't.  Since each mobile is
identified by the Key field 
over the R-P interface, we need option 1.  However, in the direction from
the PCF to the PDSN, 
we don't have a strong requirement per mobile basis; thus, option 2 is
adequate.  Therefore, 
my recommendation is that both options should be allowed in the GRE draft.

Regards,

Raymond Hsu

At 01:06 AM 3/17/00 -0800, Gopal Dommety wrote:
>Hello:
>
>I have changed the sequence no  to be 4 bytes.  The changes request by
>most have been made.
>
>A remining issue is regarding  the behaviour when both sequence no and
>the Key are present. There are two options:
>
>1. Have sequence no  per Key.  This will give  better granularity with
>   added complexity of implementation.
>
>2. Sequence no for the tunnel irrespective of the Key. 
>
>Let me know your opinion.
>
>Thanks
>Gopal
>
>
>Network Working Group				      Gopal Dommety
>INTERNET DRAFT                                        cisco Systems
>Category: Standards Track                             March 2000  
>Title:  draft-dommety-gre-ext-01.txt                  
>
>Expires October 2000
>
>		Key and Sequence Number Extensions to GRE
>		    draft-dommety-gre-ext-01.txt
>
>Status of this Memo
>
>   This document is a submission by the Network Working Group of the
>   Internet Engineering Task Force (IETF).  Comments should be submitted
>   to the gre@ops.ietf.org mailing list.
>
>   Distribution of this memo is unlimited.
>
>   This document is an Internet Draft and is in full conformance with
>   all provisions of Section 10 of RFC2026. Internet Drafts are working
>   documents of the Internet Engineering Task Force (IETF), its areas,
>   and working groups. Note that other groups may also distribute
>   working documents as Internet Drafts.
>
>   Internet Drafts are draft documents valid for a maximum of six months
>   and may be updated, replaced, or obsoleted by other documents at any
>   time. It is inappropriate to use Internet Drafts as reference
>   material or to cite them other than as "work in progress."
>
>   The list of current Internet-Drafts can be accessed at
>   http://www.ietf.org/ietf/1id-abstracts.txt.
>
>   The list of Internet-Draft Shadow Directories can be accessed at
>   http://www.ietf.org/shadow.html.
>   
>Abstract
>   
>   This  document describes extensions  by which  two fields,  Key and
>Sequence Number, can be optionally carried in the GRE (Generic Routing
>Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
>of an arbitrary network  layer protocol over another arbitrary network
>layer  protocol. 
>
>Dommety		                                                  [Page 1]
>
>Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
>
>1. Introduction
>
>   Current specification of Generic Routing Encapsulation [1] specifies
>a protocol  for encapsulation of  an arbitrary network  layer protocol
>over another arbitrary network layer protocol. This document describes
>enhancements  by which  two fields,  Key and  Sequence Number,  can be
>optionally carried  in the GRE  Header [1]. The  Key field is  used to
>create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
>is used to maintain sequence of packets within a GRE Tunnel.
>
>1.1. Specification Language
>
>   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>   this document are to be interpreted as described in RFC 2119 [3].
>
>   In addition, the following words are used to signify the 
>   requirements of the specification.  
>
>   Silently discard
>              The implementation discards the datagram without
>              further processing, and without indicating an error
>              to the sender.  The implementation SHOULD provide the
>              capability of logging the error, including the contents
>              of the discarded datagram, and SHOULD record the event
>              in a statistics counter.
>
>2. Extensions to GRE Header
>
>   The GRE packet header[1] has the following format:
>
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |C|       Reserved0       | Ver |         Protocol Type         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      Checksum (optional)      |       Reserved1 (Optional)    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>    The proposed GRE header will have the following format:
>
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |C| |K|S| Reserved0       | Ver |         Protocol Type         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      Checksum (optional)      |       Reserved1 (Optional)    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         Key (optional)                        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                 Sequence Number (Optional)                    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      
>
>      Key Present (bit 2)
>
>      If the Key Present bit is set to 1, then it indicates that the Key
>      field is present in the GRE header.  Otherwise, the Key field is
>      not present in the GRE header.
>
>      Sequence Number Present (bit 3)
>
>      If the Sequence Number Present bit is set to 1, then it indicates
>      that the Sequence Number field is present.  Otherwise, the
>      Sequence Number field is not present in the GRE header.
>
>      The  Key and Sequence Present bits are chosen to be  compatible 
>      with RFC 1701 [2].
> 
>2.1. Key Field (4 octets)
>
>     The Key field contains a  four octet number which was inserted by
>     the encapsulator. The actual method by which this Key is obtained
>     is beyond the scope of this document.  Key field is intended to be
>     used for  creating separate sub-tunnels within a  GRE Tunnel and the
>     Key field identifies the sub-tunnel. 
>
>2.2. Sequence Number (4 octets)
> 
>    The Sequence Number field is a  four byte feild and is inserted by
>    the  encapsulator when  Sequence Number  Present Bit  is set. The
>    Sequence  Number MUST  be used  by the  receiver to  establish the
>    order in which packets have been transmitted from the encapsulator
>    to the receiver.  The intended use  of the Sequence Field is to
>    provide unreliable and in-order  delivery.  If the Key present bit
>    (bit 2) is set, the  sequence number is specific to the sub-tunnel
>    identified by the Key field. Note that packets without the sequence
>     bit set can be sent in between packets with the sequence bit set.
>
>    The  sequence number  value ranges from 1 to  2**32-1. The first 
>    datagram is sent with a sequence number of 1. The  sequence 
>    number is thus a free running counter represented modulo 2**32, 
>    with the exception that 1 is used when modulo 2**32 results in 0 
>    (i.e., rollover to 1 instead of 0). 
>
>    When the decapsulator receives an out-of sequence packet it SHOULD
>    be silently discarded. Additionally, reordering of out-of sequence
>    packets  MAY  be  performed   by  the  decapsulator  for  improved
>    performance and  tolerance to reordering in the  network (since the
>    state of the stateful compression or encryption is reset by packet
>    loss, it  might help the  performance to tolerate some  amount of
>    packet reordering in the network by buffering). Exact buffering 
>    schemes are outside the scope of  this  document. Note that the  
>    sequence number is used to detect
>    lost packets and/or restore  the original sequence of packets that
>    may have been reordered during transport.
>
>   A packet  is considered an out-of-sequence packet  if the  sequence
>   number  of  the  received packet  is  lesser than or equal to  the 
>   sequence  number   of last  successfully  decapsulated
>   packet. The  sequence number  of a received message is considered
>   less than or equal to the last successfully received  sequence number 
>   if its value lies in the range of the last received  sequence number 
>   and the preceding 65534 values, inclusive. 
>
>
>    If  the   received  packet  is   an  in-sequence  packet,   it  is
>    successfully decapsulated.  Note that  the sequence number is used
>    to  detect lost packets  and/or restore  the original  sequence of
>    packets  (with  buffering) that  may  have  been reordered  during
>    transport.   Use of  the  sequence number  option  should be  used
>    appropriately; in particular, it is a good idea a avoid using when
>    tunneling  protocols  that  have  higher layer  in-order  delivery
>    mechanisms or are tolerant to out-of-order delivery. If only at certain 
>    instances the protocol being carried in the GRE tunnel requires
>    in-sequence delivery, only the corresponding packets encapsulated 
>    in a GRE header can be sent with the sequence bit set. Mechanisims 
>    to determine which packets need to be sent in-sequence and the 
>    signaling mechanisims are outside the scope of this document.
>
>
>
>
>3. IANA Considerations
>
>4. Acknowledgments
>
> 
>5. References
>
>   [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
>   "Generic           Routing           Encapsulation          (GRE),"
>   draft-meyer-gre-update-03.txt, January 2000.
>
>   [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
>   Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems, 
>   October 1994.
>
>   [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
>       Levels", RFC 2119, March 1997.
>  
>
>Dommety                                                 [Page 4]
>
>Internet Draft   Key and Sequence Number extensions to GRE   February 2000
>
>Author Information
>
>   Gopal Dommety
>   Cisco Systems, Inc.
>   170 West Tasman Drive
>   San Jose, CA 95134
>   e-mail: gdommety@cisco.com
>
>Dommety
>
>
>
>
>
>Thank You.
>Regards,
>Gopal
>---------------------------------------------------------------------------
----------------------------------
>
>Gopal Dommety
>408 525 1404 
>gdommety@cisco.com
>Cisco Systems, San Jose, CA, 95051
>
>---
>You are currently subscribed to tsgp as: rhsu@qualcomm.com
> 



From owner-l2tp@ipsec.org  Fri Mar 17 12:44:18 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07650
	for <l2tpext-archive@odin.ietf.org>; Fri, 17 Mar 2000 12:44:18 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id IAA00420; Fri, 17 Mar 2000 08:05:20 -0800 (PST)
Received: from mizar.ftl.telematics.com (mizar.ftl.telematics.com [147.137.1.7]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA00416 for <l2tp@ipsec.org>; Fri, 17 Mar 2000 08:05:12 -0800 (PST)
From: Glynn.Roche@uk.ecitele.com
Received: from ftlnotes01.ftl.telematics.com (ftlnotes01 [147.137.21.216])
	by mizar.ftl.telematics.com (8.9.1/8.9.1) with ESMTP id LAA09276;
	Fri, 17 Mar 2000 11:40:07 -0500 (EST)
Subject: Remove
To: gre@ops.ietf.org, ipsec@lists.tislabs.com,
        MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, l2tp@ipsec.org, tsgp@3gpp2.org,
        tsga@3gpp2.org
Date: Fri, 17 Mar 2000 16:31:07 +0000
Message-ID: <OF902A47D9.43C6F470-ON802568A5.005AAA83@ftl.telematics.com>
X-MIMETrack: Serialize by Router on ftlnotes01/ECI Telecom(Release 5.0.2b (Intl)|16
 December 1999) at 03/17/2000 11:42:50 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-l2tp@sailpix.com
Precedence: bulk


Remove



From owner-l2tp@ipsec.org  Fri Mar 17 15:36:16 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19136
	for <l2tpext-archive@odin.ietf.org>; Fri, 17 Mar 2000 15:36:15 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id KAA00643; Fri, 17 Mar 2000 10:36:12 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA00639 for <l2tp@ipsec.org>; Fri, 17 Mar 2000 10:34:35 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id LAA07185;
	Fri, 17 Mar 2000 11:10:51 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id LAA01237; Fri, 17 Mar 2000 11:10:50 -0800 (PST)
Date: Fri, 17 Mar 2000 11:10:50 -0800
From: Rene Tio <tor@redback.com>
To: Raymond Hsu <rhsu@qualcomm.com>
Cc: Gopal Dommety <gdommety@cisco.com>, tsgp@3gpp2.org, udlr@sophia.inria.fr,
        msdp@antc.uoregon.edu, ipsec@lists.tislabs.com,
        MOBILE-IP@standards.nortelnetworks.com, l2tp@ipsec.org, tsga@3gpp2.org
Subject: Re: GRE Extensions (Modified)
Message-ID: <20000317111050.B1078@redback.com>
References: <LYR1158584-196913-2000.03.17-00.58.48--rhsu#qualcomm.com@3 <200003171611.IAA17317@jittlov.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200003171611.IAA17317@jittlov.qualcomm.com>; from rhsu@qualcomm.com on Fri, Mar 17, 2000 at 08:12:08AM -0800
Sender: owner-l2tp@sailpix.com
Precedence: bulk

On Fri, Mar 17, 2000 at 08:12:08AM -0800, Raymond Hsu wrote:
> Hi Gopal:
> 
> In TR-45.6's R-P interface (aka A10 interface), we may use the first option
> in the direction
> from the PDSN to the PCF.  In this direction, we've identified scenarios
> where some mobiles 
> require in-sequence delivery and some don't.  Since each mobile is
> identified by the Key field 
> over the R-P interface, we need option 1.  However, in the direction from
> the PCF to the PDSN, 
> we don't have a strong requirement per mobile basis; thus, option 2 is
> adequate.  Therefore, 
> my recommendation is that both options should be allowed in the GRE draft.


I think if we plan the most limiting case (option 1, which we have at
least a few opinions is necessary) and allow for the not-so-limiting, both
cases will be covered.

IMHO the C, K, and S fields are a request for the other end to check, not a
requirement that the other end should send, i.e., if you configure a tunnel
to have checksums, you send checksums but don't require the other end to
send checksums (it's part of the "be liberal in what you receive" paradigm).
Thus in the PCF to PDSN direction you just don't configure sequence numbers
and everything Should Just Work.

Cheers,
Rene

ps/ Funny how the PPTP draft is vague on this as well, or at least my quick
    glance did not find any statement on this matter.  I don't think it
    would work if you didn't have a sequence number per key though, as one
    missed packet may cause you to turf packets across many PPP sessions.


> Regards,
> 
> Raymond Hsu
> 
> At 01:06 AM 3/17/00 -0800, Gopal Dommety wrote:
> >Hello:
> >
> >I have changed the sequence no  to be 4 bytes.  The changes request by
> >most have been made.
> >
> >A remining issue is regarding  the behaviour when both sequence no and
> >the Key are present. There are two options:
> >
> >1. Have sequence no  per Key.  This will give  better granularity with
> >   added complexity of implementation.
> >
> >2. Sequence no for the tunnel irrespective of the Key. 
> >
> >Let me know your opinion.
> >
> >Thanks
> >Gopal
> >
> >
> >Network Working Group				      Gopal Dommety
> >INTERNET DRAFT                                        cisco Systems
> >Category: Standards Track                             March 2000  
> >Title:  draft-dommety-gre-ext-01.txt                  
> >
> >Expires October 2000
> >
> >		Key and Sequence Number Extensions to GRE
> >		    draft-dommety-gre-ext-01.txt
> >
> >Status of this Memo
> >
> >   This document is a submission by the Network Working Group of the
> >   Internet Engineering Task Force (IETF).  Comments should be submitted
> >   to the gre@ops.ietf.org mailing list.
> >
> >   Distribution of this memo is unlimited.
> >
> >   This document is an Internet Draft and is in full conformance with
> >   all provisions of Section 10 of RFC2026. Internet Drafts are working
> >   documents of the Internet Engineering Task Force (IETF), its areas,
> >   and working groups. Note that other groups may also distribute
> >   working documents as Internet Drafts.
> >
> >   Internet Drafts are draft documents valid for a maximum of six months
> >   and may be updated, replaced, or obsoleted by other documents at any
> >   time. It is inappropriate to use Internet Drafts as reference
> >   material or to cite them other than as "work in progress."
> >
> >   The list of current Internet-Drafts can be accessed at
> >   http://www.ietf.org/ietf/1id-abstracts.txt.
> >
> >   The list of Internet-Draft Shadow Directories can be accessed at
> >   http://www.ietf.org/shadow.html.
> >   
> >Abstract
> >   
> >   This  document describes extensions  by which  two fields,  Key and
> >Sequence Number, can be optionally carried in the GRE (Generic Routing
> >Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
> >of an arbitrary network  layer protocol over another arbitrary network
> >layer  protocol. 
> >
> >Dommety		                                                  [Page 1]
> >
> >Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
> >
> >1. Introduction
> >
> >   Current specification of Generic Routing Encapsulation [1] specifies
> >a protocol  for encapsulation of  an arbitrary network  layer protocol
> >over another arbitrary network layer protocol. This document describes
> >enhancements  by which  two fields,  Key and  Sequence Number,  can be
> >optionally carried  in the GRE  Header [1]. The  Key field is  used to
> >create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
> >is used to maintain sequence of packets within a GRE Tunnel.
> >
> >1.1. Specification Language
> >
> >   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
> >   this document are to be interpreted as described in RFC 2119 [3].
> >
> >   In addition, the following words are used to signify the 
> >   requirements of the specification.  
> >
> >   Silently discard
> >              The implementation discards the datagram without
> >              further processing, and without indicating an error
> >              to the sender.  The implementation SHOULD provide the
> >              capability of logging the error, including the contents
> >              of the discarded datagram, and SHOULD record the event
> >              in a statistics counter.
> >
> >2. Extensions to GRE Header
> >
> >   The GRE packet header[1] has the following format:
> >
> >    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |C|       Reserved0       | Ver |         Protocol Type         |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |      Checksum (optional)      |       Reserved1 (Optional)    |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >
> >    The proposed GRE header will have the following format:
> >
> >    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |C| |K|S| Reserved0       | Ver |         Protocol Type         |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |      Checksum (optional)      |       Reserved1 (Optional)    |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                         Key (optional)                        |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                 Sequence Number (Optional)                    |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >      
> >
> >      Key Present (bit 2)
> >
> >      If the Key Present bit is set to 1, then it indicates that the Key
> >      field is present in the GRE header.  Otherwise, the Key field is
> >      not present in the GRE header.
> >
> >      Sequence Number Present (bit 3)
> >
> >      If the Sequence Number Present bit is set to 1, then it indicates
> >      that the Sequence Number field is present.  Otherwise, the
> >      Sequence Number field is not present in the GRE header.
> >
> >      The  Key and Sequence Present bits are chosen to be  compatible 
> >      with RFC 1701 [2].
> > 
> >2.1. Key Field (4 octets)
> >
> >     The Key field contains a  four octet number which was inserted by
> >     the encapsulator. The actual method by which this Key is obtained
> >     is beyond the scope of this document.  Key field is intended to be
> >     used for  creating separate sub-tunnels within a  GRE Tunnel and the
> >     Key field identifies the sub-tunnel. 
> >
> >2.2. Sequence Number (4 octets)
> > 
> >    The Sequence Number field is a  four byte feild and is inserted by
> >    the  encapsulator when  Sequence Number  Present Bit  is set. The
> >    Sequence  Number MUST  be used  by the  receiver to  establish the
> >    order in which packets have been transmitted from the encapsulator
> >    to the receiver.  The intended use  of the Sequence Field is to
> >    provide unreliable and in-order  delivery.  If the Key present bit
> >    (bit 2) is set, the  sequence number is specific to the sub-tunnel
> >    identified by the Key field. Note that packets without the sequence
> >     bit set can be sent in between packets with the sequence bit set.
> >
> >    The  sequence number  value ranges from 1 to  2**32-1. The first 
> >    datagram is sent with a sequence number of 1. The  sequence 
> >    number is thus a free running counter represented modulo 2**32, 
> >    with the exception that 1 is used when modulo 2**32 results in 0 
> >    (i.e., rollover to 1 instead of 0). 
> >
> >    When the decapsulator receives an out-of sequence packet it SHOULD
> >    be silently discarded. Additionally, reordering of out-of sequence
> >    packets  MAY  be  performed   by  the  decapsulator  for  improved
> >    performance and  tolerance to reordering in the  network (since the
> >    state of the stateful compression or encryption is reset by packet
> >    loss, it  might help the  performance to tolerate some  amount of
> >    packet reordering in the network by buffering). Exact buffering 
> >    schemes are outside the scope of  this  document. Note that the  
> >    sequence number is used to detect
> >    lost packets and/or restore  the original sequence of packets that
> >    may have been reordered during transport.
> >
> >   A packet  is considered an out-of-sequence packet  if the  sequence
> >   number  of  the  received packet  is  lesser than or equal to  the 
> >   sequence  number   of last  successfully  decapsulated
> >   packet. The  sequence number  of a received message is considered
> >   less than or equal to the last successfully received  sequence number 
> >   if its value lies in the range of the last received  sequence number 
> >   and the preceding 65534 values, inclusive. 
> >
> >
> >    If  the   received  packet  is   an  in-sequence  packet,   it  is
> >    successfully decapsulated.  Note that  the sequence number is used
> >    to  detect lost packets  and/or restore  the original  sequence of
> >    packets  (with  buffering) that  may  have  been reordered  during
> >    transport.   Use of  the  sequence number  option  should be  used
> >    appropriately; in particular, it is a good idea a avoid using when
> >    tunneling  protocols  that  have  higher layer  in-order  delivery
> >    mechanisms or are tolerant to out-of-order delivery. If only at certain 
> >    instances the protocol being carried in the GRE tunnel requires
> >    in-sequence delivery, only the corresponding packets encapsulated 
> >    in a GRE header can be sent with the sequence bit set. Mechanisims 
> >    to determine which packets need to be sent in-sequence and the 
> >    signaling mechanisims are outside the scope of this document.
> >
> >
> >
> >
> >3. IANA Considerations
> >
> >4. Acknowledgments
> >
> > 
> >5. References
> >
> >   [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
> >   "Generic           Routing           Encapsulation          (GRE),"
> >   draft-meyer-gre-update-03.txt, January 2000.
> >
> >   [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
> >   Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems, 
> >   October 1994.
> >
> >   [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
> >       Levels", RFC 2119, March 1997.
> >  
> >
> >Dommety                                                 [Page 4]
> >
> >Internet Draft   Key and Sequence Number extensions to GRE   February 2000
> >
> >Author Information
> >
> >   Gopal Dommety
> >   Cisco Systems, Inc.
> >   170 West Tasman Drive
> >   San Jose, CA 95134
> >   e-mail: gdommety@cisco.com
> >
> >Dommety
> >
> >
> >
> >
> >
> >Thank You.
> >Regards,
> >Gopal
> >---------------------------------------------------------------------------
> ----------------------------------
> >
> >Gopal Dommety
> >408 525 1404 
> >gdommety@cisco.com
> >Cisco Systems, San Jose, CA, 95051
> >
> >---
> >You are currently subscribed to tsgp as: rhsu@qualcomm.com
> > 
> 


From owner-l2tp@ipsec.org  Fri Mar 17 17:36:41 2000
Received: from www.sailpix.com ([155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06676
	for <l2tpext-archive@odin.ietf.org>; Fri, 17 Mar 2000 17:36:40 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id MAA00763; Fri, 17 Mar 2000 12:03:05 -0800 (PST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA00759 for <l2tp@ipsec.org>; Fri, 17 Mar 2000 12:01:23 -0800 (PST)
Received: from gdommety-pc2 (dhcp-sjc9-233-199.cisco.com [171.71.233.199])
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id MAA03129;
	Fri, 17 Mar 2000 12:36:05 -0800 (PST)
Message-Id: <200003172036.MAA03129@omega.cisco.com>
X-Sender: gdommety@omega.cisco.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Fri, 17 Mar 2000 12:49:00 -0800
To: Raymond Hsu <rhsu@qualcomm.com>, tsgp@3gpp2.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: GRE Extensions (Modified)
Cc: udlr@sophia.inria.fr, msdp@antc.uoregon.edu, ipsec@lists.tislabs.com,
        MOBILE-IP@standards.nortelnetworks.com, l2tp@ipsec.org, tsgp@3gpp2.org,
        tsga@3gpp2.org
In-Reply-To: <200003171611.IAA17317@jittlov.qualcomm.com>
References: <LYR1158584-196913-2000.03.17-00.58.48--rhsu#qualcomm.com@3 gpp2.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk


Ray and Pete:

Thanks. I agree with both of you. That is why the current version has this description. 
There was comment on the performance and that it might not be good to couple Key and sequence.
 So, I wanted to get opinion. 

Ray, even in the PCF to PDSN direction, we don't absolutely need it. We can do with option 2, but the 
performance may effected.  If you want to do some sort of buffering and reodering, not having a sequence no
will hurt performance (basically the sequence no will not have per session significance).

In the draft, we have option 1 as of now. Unless there is a major objections let us leave it as it is.

thanks
Gopal


At 08:12 AM 17/03/00 -0800, Raymond Hsu wrote:
>Hi Gopal:
>
>In TR-45.6's R-P interface (aka A10 interface), we may use the first option
>in the direction
>from the PDSN to the PCF.  In this direction, we've identified scenarios
>where some mobiles 
>require in-sequence delivery and some don't.  Since each mobile is
>identified by the Key field 
>over the R-P interface, we need option 1.  However, in the direction from
>the PCF to the PDSN, 
>we don't have a strong requirement per mobile basis; thus, option 2 is
>adequate.  Therefore, 
>my recommendation is that both options should be allowed in the GRE draft.
>
>Regards,
>
>Raymond Hsu
>
>At 01:06 AM 3/17/00 -0800, Gopal Dommety wrote:
>>Hello:
>>
>>I have changed the sequence no  to be 4 bytes.  The changes request by
>>most have been made.
>>
>>A remining issue is regarding  the behaviour when both sequence no and
>>the Key are present. There are two options:
>>
>>1. Have sequence no  per Key.  This will give  better granularity with
>>   added complexity of implementation.
>>
>>2. Sequence no for the tunnel irrespective of the Key. 
>>
>>Let me know your opinion.
>>
>>Thanks
>>Gopal
>>
>>
>>Network Working Group				      Gopal Dommety
>>INTERNET DRAFT                                        cisco Systems
>>Category: Standards Track                             March 2000  
>>Title:  draft-dommety-gre-ext-01.txt                  
>>
>>Expires October 2000
>>
>>		Key and Sequence Number Extensions to GRE
>>		    draft-dommety-gre-ext-01.txt
>>
>>Status of this Memo
>>
>>   This document is a submission by the Network Working Group of the
>>   Internet Engineering Task Force (IETF).  Comments should be submitted
>>   to the gre@ops.ietf.org mailing list.
>>
>>   Distribution of this memo is unlimited.
>>
>>   This document is an Internet Draft and is in full conformance with
>>   all provisions of Section 10 of RFC2026. Internet Drafts are working
>>   documents of the Internet Engineering Task Force (IETF), its areas,
>>   and working groups. Note that other groups may also distribute
>>   working documents as Internet Drafts.
>>
>>   Internet Drafts are draft documents valid for a maximum of six months
>>   and may be updated, replaced, or obsoleted by other documents at any
>>   time. It is inappropriate to use Internet Drafts as reference
>>   material or to cite them other than as "work in progress."
>>
>>   The list of current Internet-Drafts can be accessed at
>>   http://www.ietf.org/ietf/1id-abstracts.txt.
>>
>>   The list of Internet-Draft Shadow Directories can be accessed at
>>   http://www.ietf.org/shadow.html.
>>   
>>Abstract
>>   
>>   This  document describes extensions  by which  two fields,  Key and
>>Sequence Number, can be optionally carried in the GRE (Generic Routing
>>Encapsulation) Header  [1]. GRE specifies a  protocol for encapsulation
>>of an arbitrary network  layer protocol over another arbitrary network
>>layer  protocol. 
>>
>>Dommety		                                                  [Page 1]
>>
>>Internet Draft  Key and Sequence Number Extensions to GRE  February 2000
>>
>>1. Introduction
>>
>>   Current specification of Generic Routing Encapsulation [1] specifies
>>a protocol  for encapsulation of  an arbitrary network  layer protocol
>>over another arbitrary network layer protocol. This document describes
>>enhancements  by which  two fields,  Key and  Sequence Number,  can be
>>optionally carried  in the GRE  Header [1]. The  Key field is  used to
>>create separate sub-tunnels within  a GRE Tunnel. Sequence Number field
>>is used to maintain sequence of packets within a GRE Tunnel.
>>
>>1.1. Specification Language
>>
>>   The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>>   this document are to be interpreted as described in RFC 2119 [3].
>>
>>   In addition, the following words are used to signify the 
>>   requirements of the specification.  
>>
>>   Silently discard
>>              The implementation discards the datagram without
>>              further processing, and without indicating an error
>>              to the sender.  The implementation SHOULD provide the
>>              capability of logging the error, including the contents
>>              of the discarded datagram, and SHOULD record the event
>>              in a statistics counter.
>>
>>2. Extensions to GRE Header
>>
>>   The GRE packet header[1] has the following format:
>>
>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |C|       Reserved0       | Ver |         Protocol Type         |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |      Checksum (optional)      |       Reserved1 (Optional)    |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>>
>>    The proposed GRE header will have the following format:
>>
>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |C| |K|S| Reserved0       | Ver |         Protocol Type         |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |      Checksum (optional)      |       Reserved1 (Optional)    |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |                         Key (optional)                        |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>    |                 Sequence Number (Optional)                    |
>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      
>>
>>      Key Present (bit 2)
>>
>>      If the Key Present bit is set to 1, then it indicates that the Key
>>      field is present in the GRE header.  Otherwise, the Key field is
>>      not present in the GRE header.
>>
>>      Sequence Number Present (bit 3)
>>
>>      If the Sequence Number Present bit is set to 1, then it indicates
>>      that the Sequence Number field is present.  Otherwise, the
>>      Sequence Number field is not present in the GRE header.
>>
>>      The  Key and Sequence Present bits are chosen to be  compatible 
>>      with RFC 1701 [2].
>> 
>>2.1. Key Field (4 octets)
>>
>>     The Key field contains a  four octet number which was inserted by
>>     the encapsulator. The actual method by which this Key is obtained
>>     is beyond the scope of this document.  Key field is intended to be
>>     used for  creating separate sub-tunnels within a  GRE Tunnel and the
>>     Key field identifies the sub-tunnel. 
>>
>>2.2. Sequence Number (4 octets)
>> 
>>    The Sequence Number field is a  four byte feild and is inserted by
>>    the  encapsulator when  Sequence Number  Present Bit  is set. The
>>    Sequence  Number MUST  be used  by the  receiver to  establish the
>>    order in which packets have been transmitted from the encapsulator
>>    to the receiver.  The intended use  of the Sequence Field is to
>>    provide unreliable and in-order  delivery.  If the Key present bit
>>    (bit 2) is set, the  sequence number is specific to the sub-tunnel
>>    identified by the Key field. Note that packets without the sequence
>>     bit set can be sent in between packets with the sequence bit set.
>>
>>    The  sequence number  value ranges from 1 to  2**32-1. The first 
>>    datagram is sent with a sequence number of 1. The  sequence 
>>    number is thus a free running counter represented modulo 2**32, 
>>    with the exception that 1 is used when modulo 2**32 results in 0 
>>    (i.e., rollover to 1 instead of 0). 
>>
>>    When the decapsulator receives an out-of sequence packet it SHOULD
>>    be silently discarded. Additionally, reordering of out-of sequence
>>    packets  MAY  be  performed   by  the  decapsulator  for  improved
>>    performance and  tolerance to reordering in the  network (since the
>>    state of the stateful compression or encryption is reset by packet
>>    loss, it  might help the  performance to tolerate some  amount of
>>    packet reordering in the network by buffering). Exact buffering 
>>    schemes are outside the scope of  this  document. Note that the  
>>    sequence number is used to detect
>>    lost packets and/or restore  the original sequence of packets that
>>    may have been reordered during transport.
>>
>>   A packet  is considered an out-of-sequence packet  if the  sequence
>>   number  of  the  received packet  is  lesser than or equal to  the 
>>   sequence  number   of last  successfully  decapsulated
>>   packet. The  sequence number  of a received message is considered
>>   less than or equal to the last successfully received  sequence number 
>>   if its value lies in the range of the last received  sequence number 
>>   and the preceding 65534 values, inclusive. 
>>
>>
>>    If  the   received  packet  is   an  in-sequence  packet,   it  is
>>    successfully decapsulated.  Note that  the sequence number is used
>>    to  detect lost packets  and/or restore  the original  sequence of
>>    packets  (with  buffering) that  may  have  been reordered  during
>>    transport.   Use of  the  sequence number  option  should be  used
>>    appropriately; in particular, it is a good idea a avoid using when
>>    tunneling  protocols  that  have  higher layer  in-order  delivery
>>    mechanisms or are tolerant to out-of-order delivery. If only at certain 
>>    instances the protocol being carried in the GRE tunnel requires
>>    in-sequence delivery, only the corresponding packets encapsulated 
>>    in a GRE header can be sent with the sequence bit set. Mechanisims 
>>    to determine which packets need to be sent in-sequence and the 
>>    signaling mechanisims are outside the scope of this document.
>>
>>
>>
>>
>>3. IANA Considerations
>>
>>4. Acknowledgments
>>
>> 
>>5. References
>>
>>   [1] Farinacci,  D., Li,  T., Hnaks, S.,  Meyer, D. and  Traina, P.,
>>   "Generic           Routing           Encapsulation          (GRE),"
>>   draft-meyer-gre-update-03.txt, January 2000.
>>
>>   [2]  Hanks, S.,  Li,  T,  Farinacci, D.,  and  P. Traina,  "Generic
>>   Routing Encapsulation",  RFC 1701, NetSmiths,  Ltd., and cisco Systems, 
>>   October 1994.
>>
>>   [3] Bradner S., "Key words for use in RFCs to Indicate Requirement
>>       Levels", RFC 2119, March 1997.
>>  
>>
>>Dommety                                                 [Page 4]
>>
>>Internet Draft   Key and Sequence Number extensions to GRE   February 2000
>>
>>Author Information
>>
>>   Gopal Dommety
>>   Cisco Systems, Inc.
>>   170 West Tasman Drive
>>   San Jose, CA 95134
>>   e-mail: gdommety@cisco.com
>>
>>Dommety
>>
>>
>>
>>
>>
>>Thank You.
>>Regards,
>>Gopal
>>---------------------------------------------------------------------------
>----------------------------------
>>
>>Gopal Dommety
>>408 525 1404 
>>gdommety@cisco.com
>>Cisco Systems, San Jose, CA, 95051
>>
>>---
>>You are currently subscribed to tsgp as: rhsu@qualcomm.com
>> 
> 
Thank You.
Regards,
Gopal
-------------------------------------------------------------------------------------------------------------

Gopal Dommety
408 525 1404 
gdommety@cisco.com
Cisco Systems, San Jose, CA, 95051


From owner-l2tp@ipsec.org  Mon Mar 20 17:57:44 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15135
	for <l2tpext-archive@odin.ietf.org>; Mon, 20 Mar 2000 17:57:43 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id NAA07675; Mon, 20 Mar 2000 13:01:58 -0800 (PST)
Received: from celoxcom.com (mail.celoxcom.com [199.217.151.231]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA07671 for <l2tp-digest@ipsec.org>; Mon, 20 Mar 2000 13:01:42 -0800 (PST)
Received: (from johnson@localhost)
	by celoxcom.com (8.9.3/8.9.3) id PAA29591
	for l2tp-digest@ipsec.org; Mon, 20 Mar 2000 15:37:50 -0600 (CST)
Date: Mon, 20 Mar 2000 15:37:50 -0600
From: Ken Johnson <johnson@celoxcom.com>
To: l2tp-digest@ipsec.org
Subject: Current archive of the list?
Message-ID: <20000320153749.A29509@maxwell.celoxcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0us
Sender: owner-l2tp@sailpix.com
Precedence: bulk


The archives of this list at http://www.ipsec.org/email/l2tp.html
only run through Thu 11 Nov 1999 - 07:04:33 PST.  Is there a more
current archive available?

Is there a FAQ associated with this list?

-- 

Ken Johnson
Celox Networks
314 615 6369
johnson@celoxcom.com



From owner-l2tp@ipsec.org  Wed Mar 22 00:42:09 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16495
	for <l2tpext-archive@odin.ietf.org>; Wed, 22 Mar 2000 00:42:08 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id TAA10830; Tue, 21 Mar 2000 19:53:39 -0800 (PST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA10826 for <l2tp@ipsec.org>; Tue, 21 Mar 2000 19:53:22 -0800 (PST)
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 UAA19552
	for <l2tp@ipsec.org>; Tue, 21 Mar 2000 20:16:44 -0800 (PST)
Received: from cisco.com (networkers-dhcp-162.cisco.com [144.254.137.162]) by townsley-ultra.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id XAA05861 for <l2tp@ipsec.org>; Tue, 21 Mar 2000 23:29:41 -0500 (EST)
Message-ID: <38D84C24.1151B273@cisco.com>
Date: Tue, 21 Mar 2000 23:29:25 -0500
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: [Fwd: 47th IETF: DRAFT AGENDA]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


Our time slot got changed. Same day, new time. The agenda within the WG
remains as I last posted.

Thanks,

- Mark


WEDNESDAY, March 29, 2000

1130-1300  Break
1300-1500  Afternoon Sessions I
        APP  b2bxml     Business to Business XML Data Communication
Strategies BOF
        APP  trade      Internet Open Trading Protocol WG
	INT  ipfc	IP Over Fibre Channel WG
	INT  l2tpext	Layer Two Tunneling Protocol Extensions WG
	OPS  ngtrans	Next Generation Transition WG
	OPS  policy	Policy Framework WG *
	RTG  msdp	Multicast Source Discovery Protocol WG *
	TSV  ecm	Endpoint Congestion Management WG


From owner-l2tp@ipsec.org  Thu Mar 23 22:18:06 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27338
	for <l2tpext-archive@odin.ietf.org>; Thu, 23 Mar 2000 22:18:05 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id KAA00363; Thu, 23 Mar 2000 10:59:33 -0800 (PST)
Received: from ns2.accesscom.com (root@ns2.accesscom.com [205.226.156.3]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA00359 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 10:59:23 -0800 (PST)
Received: from shell.accesscom.com (root@shell.accesscom.com [205.226.156.10])
	by ns2.accesscom.com (8.9.3/8.9.3/Debian/GNU) with ESMTP id HAA25891
	for <l2tp@ipsec.org>; Thu, 23 Mar 2000 07:19:54 -0800
Received: (from sabrina@localhost)
	by shell.accesscom.com (8.9.3/8.9.3/Debian/GNU) id HAA30618
	for l2tp@ipsec.org; Thu, 23 Mar 2000 07:19:53 -0800
From: Sabrina Minshall <sabrina@accesscom.com>
Message-Id: <200003231519.HAA30618@shell.accesscom.com>
Subject: Couple of questions
To: l2tp@ipsec.org
Date: Thu, 23 Mar 2000 07:19:53 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

1. When a control packet is received with a bad hdr options but with correct
   nr and ns, do we need update our local state?

   I assume we just drop it (even without sending and zlb)?

2. When a control packet received is that's within the current window 
   but is not the next packet in seq (that the FSM is expecting),
   should a ZLB be sent?

   Thanks.

   Sabrina


From owner-l2tp@ipsec.org  Thu Mar 23 23:22:21 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18399
	for <l2tpext-archive@odin.ietf.org>; Thu, 23 Mar 2000 23:22:20 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id LAA00504; Thu, 23 Mar 2000 11:44:06 -0800 (PST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA00500 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 11:43:50 -0800 (PST)
From: kyork@cisco.com
Received: from deep-freeze.cisco.com (deep-freeze.cisco.com [171.71.68.21])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA12261
	for <l2tp@ipsec.org>; Thu, 23 Mar 2000 11:43:20 -0800 (PST)
Received: from cisco.com (dhcp-171-71-66-165.cisco.com [171.71.66.165]) by deep-freeze.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id LAA27241 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 11:43:19 -0800 (PST)
Message-ID: <38DA73D5.90A9203C@cisco.com>
Date: Thu, 23 Mar 2000 11:43:17 -0800
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
CC: l2tp@ipsec.org
Subject: Re: Couple of questions
References: <200003231519.HAA30618@shell.accesscom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,

Sabrina Minshall wrote:
> 
> 1. When a control packet is received with a bad hdr options but with correct
>    nr and ns, do we need update our local state?
> 
>    I assume we just drop it (even without sending and zlb)?
> 

I generally think of the control packet as two layers : delivery & data.
If it's in the delivery window, I schedule a ZLB and pass it up to the
data layer. So, yes, update the local state.

> 2. When a control packet received is that's within the current window
>    but is not the next packet in seq (that the FSM is expecting),
>    should a ZLB be sent?
> 

Yes. Assume that the last ZLB was lost & the host is retransmitting. If
you don't acknowlege it, you'll never sync back up.


>    Thanks.
> 
>    Sabrina

-- 
Kyle A. York
Subordinate Grunt
CLOB


From owner-l2tp@ipsec.org  Fri Mar 24 01:20:01 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02711
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 01:20:01 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id VAA00768; Thu, 23 Mar 2000 21:17:40 -0800 (PST)
Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id VAA00764 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 21:17:26 -0800 (PST)
From: Barney Wolff <barney@databus.com>
To: l2tp@ipsec.org
Date: Fri, 24 Mar 2000 00:05 EST
Subject: Re: Couple of questions
Content-Type: text/plain
Message-ID: <38dafa620.3d0c@databus.databus.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

This is correct for a packet with Ns lower than you're expecting,
but misleadingly wrong for a packet with Ns higher than you're
expecting.  Either save it until you get the intervening packet(s),
or toss it, depending on how hard you want to work.  But a ZLB is
not going to elicit a quicker retransmission than the sender's
timeout - this is not TCP with fast-retransmit.

Barney Wolff  <barney@databus.com>

> From: kyork@cisco.com
> Date: Thu, 23 Mar 2000 11:43:17 -0800
> 
> > 2. When a control packet received is that's within the current window
> >    but is not the next packet in seq (that the FSM is expecting),
> >    should a ZLB be sent?
> 
> Yes. Assume that the last ZLB was lost & the host is retransmitting. If
> you don't acknowlege it, you'll never sync back up.


From owner-l2tp@ipsec.org  Fri Mar 24 01:51:34 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17957
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 01:51:33 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id UAA00696; Thu, 23 Mar 2000 20:47:36 -0800 (PST)
Received: from blue.cosinecom.com (proxy4.cosinecom.com [208.248.148.132]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id UAA00692 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 20:47:22 -0800 (PST)
Received: from cosinecom.com by blue.cosinecom.com (8.8.8+Sun/SMI-SVR4)
	id UAA01986; Thu, 23 Mar 2000 20:46:51 -0800 (PST)
Message-ID: <38DAF33A.2345BA37@cosinecom.com>
Date: Thu, 23 Mar 2000 20:46:50 -0800
From: Srinivasan Chakravarthy <cs@cosinecom.com>
Organization: CoSine Communications Inc.
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: L2TP tunnel authentication in Win2000.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have a question about enabling L2TP tunnel authentication in Windows2000. By
default, Win2000 doesnot do tunnel authentication. I went to msdn.microsoft.com
to find the info but i am not able to locate the tunnel authentication enabling
there. I would be grateful if you could me know where i can get the info.

Thanks & Regards,

Srinivasan.





From owner-l2tp@ipsec.org  Fri Mar 24 02:43:55 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12951
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 02:43:54 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id WAA00959; Thu, 23 Mar 2000 22:03:01 -0800 (PST)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id WAA00948 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 22:02:28 -0800 (PST)
Received: by ans2-pub.dttus.com id AAA04837
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Fri, 24 Mar 2000 00:02:16 -0600
Received: by ans2-pub.dttus.com (Internal Mail Agent-3);
  Fri, 24 Mar 2000 00:02:16 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Fri, 24 Mar 2000 00:02:16 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Fri, 24 Mar 2000 00:02:16 -0600
X400-Mts-Identifier: [/c=US/admd=TeleMail/prmd=Deloitte/; 0311D38DB04AB005-MTAUSBNA1DT]
Content-Identifier: 0311D38DB04AB005
Content-Return: Allowed
X400-Content-Type: P2-1988 ( 22 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Disclose-Recipients: Prohibited
Alternate-Recipient: Allowed
X400-Originator: rverma@dttus.com
X400-Recipients: non-disclosure;
Message-Id: 
  <0311D38DB04AB005*/c=US/admd=TeleMail/prmd=Deloitte/o=ccMailGW/s=rverma/@MHS>
Date: 24 Mar 2000 00:01:15 -0600
From: Rohit Verma <rverma@dttus.com>
To: kyork@cisco.com, sabrina@accesscom.com, l2tp@ipsec.org
Subject: Re[2]: Couple of questions
Sender: owner-l2tp@sailpix.com
Precedence: bulk


     A clarification to Part 2 if the received packet sequence number is 
     less than the highest received sequence number then you ack otherwise 
     you discard it.
     
     
     
     Ns=1 Action=Ack
     Ns=2 Action=Ack
     Ns=4 Action=Ignore
     Ns=3 Action=Ack
     Ns=2 Action=Ack
     
     If u ack Ns=4 then the peer will think that you have acked pkt 3 as 
     well.
     
     Hope this helps
     
     Regards
     Rohit Verma
     


______________________________ Reply Separator _________________________________
Subject: Re: Couple of questions
Author:  kyork@cisco.com at Internet-USA
Date:    3/23/00 10:18 PM


Greetings,
     
Sabrina Minshall wrote:
>
> 1. When a control packet is received with a bad hdr options but with correct 
>    nr and ns, do we need update our local state?
>
>    I assume we just drop it (even without sending and zlb)? 
>
     
I generally think of the control packet as two layers : delivery & data. 
If it's in the delivery window, I schedule a ZLB and pass it up to the 
data layer. So, yes, update the local state.
     
> 2. When a control packet received is that's within the current window 
>    but is not the next packet in seq (that the FSM is expecting),
>    should a ZLB be sent?
>
     
Yes. Assume that the last ZLB was lost & the host is retransmitting. If 
you don't acknowlege it, you'll never sync back up.
     
     
>    Thanks.
>
>    Sabrina
     
--
Kyle A. York
Subordinate Grunt
CLOB


From owner-l2tp@ipsec.org  Fri Mar 24 03:16:11 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25161
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 03:16:10 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id WAA01077; Thu, 23 Mar 2000 22:58:35 -0800 (PST)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA01073 for <l2tp@ipsec.org>; Thu, 23 Mar 2000 22:58:14 -0800 (PST)
Received: from gwz (oz-syd-dial1-29.cisco.com [144.254.157.30]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id WAA03094; Thu, 23 Mar 2000 22:57:41 -0800 (PST)
From: "Glen Zorn" <gwz@cisco.com>
To: "Srinivasan Chakravarthy" <cs@cosinecom.com>, <l2tp@ipsec.org>
Subject: RE: L2TP tunnel authentication in Win2000.
Date: Thu, 23 Mar 2000 22:57:29 -0800
Message-ID: <NDBBIHMPILAAGDHPCIOPOENLCAAA.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: <38DAF33A.2345BA37@cosinecom.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Srinivasan Chakravarthy [mailto::cs@cosinecom.com] writes:

>
> Hi,
>
> I have a question about enabling L2TP tunnel authentication in
> Windows2000. By
> default, Win2000 doesnot do tunnel authentication. I went to
> msdn.microsoft.com
> to find the info but i am not able to locate the tunnel
> authentication enabling
> there. I would be grateful if you could me know where i can get the info.

Try this:

Turning on L2TP Tunnel Auth
Registry key:
  HKLM/SYSTEM/CurrentControlSet/Control/Class
Look for a GUID, the first component of which ends in 72 (e.g.,
4D36E972-E325-11CE-BFC1-08002BE10318.  Under this key, find the key with
DriverDesc=WAN Miniport (L2TP).  Add a REG_SZ value called Password and set
the value to the desired shared secret.  The same secret is used for all
connections and the L2TP driver will always negotiate tunnel authentication
if this value exists.

>
> Thanks & Regards,
>
> Srinivasan.
>
>
>
>
>



From owner-l2tp@ipsec.org  Fri Mar 24 10:14:08 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20253
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 10:14:07 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id FAA02832; Fri, 24 Mar 2000 05:40:57 -0800 (PST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA02828 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 05:40:41 -0800 (PST)
From: kyork@cisco.com
Received: from deep-freeze.cisco.com (deep-freeze.cisco.com [171.71.68.21])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id FAA14778
	for <l2tp@ipsec.org>; Fri, 24 Mar 2000 05:26:42 -0800 (PST)
Received: from cisco.com ([171.71.72.75]) by deep-freeze.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id FAA07312 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 05:39:13 -0800 (PST)
Message-ID: <38DB6FFB.17A8AB3F@cisco.com>
Date: Fri, 24 Mar 2000 05:39:07 -0800
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
CC: l2tp@ipsec.org
Subject: Re: Couple of questions
References: <38dafa620.3d0c@databus.databus.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,

Barney Wolff wrote:
> 
> This is correct for a packet with Ns lower than you're expecting,

Oops. Yes. I was assuming lower (missed) Ns. Don't know why. Thanks for
the correction.

> but misleadingly wrong for a packet with Ns higher than you're
> expecting.  Either save it until you get the intervening packet(s),
> or toss it, depending on how hard you want to work.  But a ZLB is
> not going to elicit a quicker retransmission than the sender's
> timeout - this is not TCP with fast-retransmit.
> 
> Barney Wolff  <barney@databus.com>
> 
> > From: kyork@cisco.com
> > Date: Thu, 23 Mar 2000 11:43:17 -0800
> >
> > > 2. When a control packet received is that's within the current window
> > >    but is not the next packet in seq (that the FSM is expecting),
> > >    should a ZLB be sent?
> >
> > Yes. Assume that the last ZLB was lost & the host is retransmitting. If
> > you don't acknowlege it, you'll never sync back up.

-- 
Kyle A. York
Subordinate Grunt
CLOB


From owner-l2tp@ipsec.org  Fri Mar 24 10:27:47 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24691
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 10:27:46 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id EAA02770; Fri, 24 Mar 2000 04:58:19 -0800 (PST)
Received: from io.note.iri.co.jp (ns.note.iri.co.jp [210.231.221.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA02766 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 04:57:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by io.note.iri.co.jp (8.9.3/3.7Wpl2-2000-Jan-20-1337) with ESMTP id VAA10681;
	Fri, 24 Mar 2000 21:57:31 +0900 (JST)
From: nat@certworks.net
To: gwz@cisco.com
Cc: cs@cosinecom.com, l2tp@ipsec.org
Subject: RE: L2TP tunnel authentication in Win2000.
In-Reply-To: <NDBBIHMPILAAGDHPCIOPOENLCAAA.gwz@cisco.com>
References: <38DAF33A.2345BA37@cosinecom.com>
	<NDBBIHMPILAAGDHPCIOPOENLCAAA.gwz@cisco.com>
X-Mailer: Mew version 1.94b47 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000324215730T.not@iri.co.jp>
Date: Fri, 24 Mar 2000 21:57:30 +0900 (JST)
X-Dispatcher: imput version 990731(IM118)
Lines: 52
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


  Hi,

From: "Glen Zorn" <gwz@cisco.com>
Subject: RE: L2TP tunnel authentication in Win2000.
Date: Thu, 23 Mar 2000 22:57:29 -0800

> Try this:
> 
> Turning on L2TP Tunnel Auth
> Registry key:
>   HKLM/SYSTEM/CurrentControlSet/Control/Class
> Look for a GUID, the first component of which ends in 72 (e.g.,
> 4D36E972-E325-11CE-BFC1-08002BE10318.  Under this key, find the key with
> DriverDesc=WAN Miniport (L2TP).  Add a REG_SZ value called Password and set
> the value to the desired shared secret.  The same secret is used for all
> connections and the L2TP driver will always negotiate tunnel authentication
> if this value exists.

  Is this Windows 2000(server/professional) LAC Client or LNS ?

  I'm try W2K Pro following setting, but it was not work ...

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001]
"MaxVcs"=dword:000003e8
"MinWanEndpoints"=dword:00000000
"MaxWanEndpoints"=dword:000003e8
"WanEndpoints"=dword:00000002
"Characteristics"=dword:00000029
"ComponentId"="ms_l2tpminiport"
"InfPath"="netrasa.inf"
"InfSection"="Ndi-Mp-L2tp"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,40,4b,de,e9,27,bf,01
"DriverDate"="11-6-1999"
"DriverVersion"="5.0.2175.1"
"MatchingDeviceId"="ms_l2tpminiport"
"DriverDesc"="WAN Mini Port (L2TP)"
"NetCfgInstanceId"="{2A515228-EC05-421C-AE4E-6E3FA1763DA6}"
"EnableForRas"=dword:00000001
"EnableForRouting"=dword:00000000
"Password"="TEST-L2TP-TEST"
^^^^^^^^^^^^^^^^^ Added this value.

  BTW, The W2K LAC Client have LNS name?

  I'm not found Register value on W2K.

  Thanks,

====
Naoto "nat" MATSUMOTO <nat@certworks.net>


From owner-l2tp@ipsec.org  Fri Mar 24 12:59:01 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18236
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 12:59:00 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id HAA02979; Fri, 24 Mar 2000 07:32:41 -0800 (PST)
Received: from ns2.accesscom.com (root@ns2.accesscom.com [205.226.156.3]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA02975 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 07:32:27 -0800 (PST)
Received: from shell.accesscom.com (root@shell.accesscom.com [205.226.156.10])
	by ns2.accesscom.com (8.9.3/8.9.3/Debian/GNU) with ESMTP id HAA07918;
	Fri, 24 Mar 2000 07:32:26 -0800
Received: (from sabrina@localhost)
	by shell.accesscom.com (8.9.3/8.9.3/Debian/GNU) id HAA06324;
	Fri, 24 Mar 2000 07:32:26 -0800
From: Sabrina Minshall <sabrina@accesscom.com>
Message-Id: <200003241532.HAA06324@shell.accesscom.com>
Subject: Re: Re[2]: Couple of questions
In-Reply-To: From Rohit Verma at "Mar 24, 2000 00:01:15 am"
To: l2tp@ipsec.org
Date: Fri, 24 Mar 2000 07:32:26 -0800 (PST)
CC: sabrina@accesscom.com
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

  Thanks for those replies.

  Yet another question.

  A                         B
  SCCRQ        ->           
		(lost) <-           SCCRP

  StopCCN      ->           


  Now the StopCCN, had a tunnel/session id of 0/0. If the AVP's
  in the StopCCN is hidden (Assigned Tunnel Id), there's no way
  B can process it. It's also true in the CDN case where and 
  SCRP is lost and A sends a CDN.

  I guess you just let the tunnel/session created by B for A,
  timeout?

  Am I correct?


  Sabrina


From owner-l2tp@ipsec.org  Fri Mar 24 15:08:08 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06158
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 15:08:07 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id KAA03265; Fri, 24 Mar 2000 10:14:59 -0800 (PST)
Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id KAA03261 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 10:14:37 -0800 (PST)
From: Barney Wolff <barney@databus.com>
To: l2tp@ipsec.org
Cc: sabrina@accesscom.com
Date: Fri, 24 Mar 2000 12:51 EST
Subject: Re: Re[2]: Couple of questions
Content-Type: text/plain
Message-ID: <38dbaded0.4475@databus.databus.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

No, you know which peer sent you the StopCCN (for example with l2tp/udp
by the IP address of the sender) so you know what the shared secret
is, so you can decode the hidden avp.  Hidden or not, you need a way
to look up the tunnel/session by the peer's id rather than your own,
because you need to handle a retransmitted SCCRQ as well as the StopCCN.
Without that, you're likely to set up two tunnels, and things will
not go well.

The table is a little unusual because you do 1 add and 1 delete per
tunnel/session, but rarely do a lookup.

Barney Wolff  <barney@databus.com>

> From: Sabrina Minshall <sabrina@accesscom.com>
> Date: Fri, 24 Mar 2000 07:32:26 -0800 (PST)
> 
>   A                         B
>   SCCRQ        ->           
> 		(lost) <-           SCCRP
> 
>   StopCCN      ->           
> 
> 
>   Now the StopCCN, had a tunnel/session id of 0/0. If the AVP's
>   in the StopCCN is hidden (Assigned Tunnel Id), there's no way
>   B can process it. It's also true in the CDN case where and 
>   SCRP is lost and A sends a CDN.
> 
>   I guess you just let the tunnel/session created by B for A,
>   timeout?


From owner-l2tp@ipsec.org  Fri Mar 24 16:04:45 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27588
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 16:04:44 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id LAA03420; Fri, 24 Mar 2000 11:33:13 -0800 (PST)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id LAA03416 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 11:32:51 -0800 (PST)
Received: by ans2-pub.dttus.com id NAA02697
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Fri, 24 Mar 2000 13:32:45 -0600
Received: by ans2-pub.dttus.com (Internal Mail Agent-3);
  Fri, 24 Mar 2000 13:32:45 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Fri, 24 Mar 2000 13:32:45 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Fri, 24 Mar 2000 13:32:45 -0600
X400-Mts-Identifier: [/c=US/admd=TeleMail/prmd=Deloitte/; 070A038DBC1300D0-MTAUSBNA1DT]
Content-Identifier: 070A038DBC1300D0
Content-Return: Allowed
X400-Content-Type: P2-1988 ( 22 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Disclose-Recipients: Prohibited
Alternate-Recipient: Allowed
X400-Originator: rverma@dttus.com
X400-Recipients: non-disclosure;
Message-Id: 
  <070A038DBC1300D0*/c=US/admd=TeleMail/prmd=Deloitte/o=ccMailGW/s=rverma/@MHS>
Date: 24 Mar 2000 13:25:36 -0600
From: Rohit Verma <rverma@dttus.com>
To: l2tp@ipsec.org
Cc: sabrina@accesscom.com
Subject: Re[4]: Couple of questions
Sender: owner-l2tp@sailpix.com
Precedence: bulk


     Technically there should be retransmissions because the Control 
     Channel is reliable. If the SCCRP still does not make it then it will 
     hit the max retransmissions limit and timeout.
     
     Regards
     Rohit Verma 


______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: Couple of questions
Author:  sabrina@accesscom.com at Internet-USA
Date:    3/24/00 11:42 AM


  Thanks for those replies.
     
  Yet another question.
     
  A                         B
  SCCRQ        ->
          (lost) <-           SCCRP
     
  StopCCN      ->
     
     
  Now the StopCCN, had a tunnel/session id of 0/0. If the AVP's 
  in the StopCCN is hidden (Assigned Tunnel Id), there's no way 
  B can process it. It's also true in the CDN case where and 
  SCRP is lost and A sends a CDN.
     
  I guess you just let the tunnel/session created by B for A, 
  timeout?
     
  Am I correct?
     
     
  Sabrina


From owner-l2tp@ipsec.org  Fri Mar 24 17:20:06 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23213
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 17:20:03 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id MAA03594; Fri, 24 Mar 2000 12:53:33 -0800 (PST)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id MAA03590 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 12:53:17 -0800 (PST)
Received: by ans2-pub.dttus.com id OAA02906
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Fri, 24 Mar 2000 14:53:15 -0600
Received: by ans2-pub.dttus.com (Internal Mail Agent-3);
  Fri, 24 Mar 2000 14:53:15 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Fri, 24 Mar 2000 14:53:15 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Fri, 24 Mar 2000 14:53:15 -0600
X400-Mts-Identifier: [/c=US/admd=TeleMail/prmd=Deloitte/; 0097138DBD5831C3-MTAUSBNA1DT]
Content-Identifier: 0097138DBD5831C3
Content-Return: Allowed
X400-Content-Type: P2-1988 ( 22 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Disclose-Recipients: Prohibited
Alternate-Recipient: Allowed
X400-Originator: rverma@dttus.com
X400-Recipients: non-disclosure;
Message-Id: 
  <0097138DBD5831C3*/c=US/admd=TeleMail/prmd=Deloitte/o=ccMailGW/s=rverma/@MHS>
Date: 24 Mar 2000 14:52:19 -0600
From: Rohit Verma <rverma@dttus.com>
To: sabrina@accesscom.com
Cc: l2tp@ipsec.org
Subject: Re[6]: Couple of questions
Sender: owner-l2tp@sailpix.com
Precedence: bulk


     Hi Sabrina
        I always like to talk in terms of Call Id and the Tunnel Id. And 
     yes you are right that the Call Id must be 0 in the ZLB.
      A good implementation in my personal opinion should not be too fussy 
     about it.
     
     Regards
     Rohit Verma


______________________________ Reply Separator _________________________________
Subject: Re: Re[4]: Couple of questions
Author:  sabrina@accesscom.com at Internet-USA
Date:    3/24/00 2:12 PM


Hi Rohit,
     
   Thanks. Should the session id on an ZLB be 0 always?
     
     
   Thanks,
     
     
   Sabrina


From owner-l2tp@ipsec.org  Fri Mar 24 19:24:55 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07951
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 19:24:54 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id OAA03890; Fri, 24 Mar 2000 14:57:08 -0800 (PST)
Received: from blue.cosinecom.com (proxy4.cosinecom.com [208.248.148.132]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA03886 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 14:56:32 -0800 (PST)
Received: from cosinecom.com by blue.cosinecom.com (8.8.8+Sun/SMI-SVR4)
	id OAA08885; Fri, 24 Mar 2000 14:54:52 -0800 (PST)
Message-ID: <38DBF26A.C916D73C@cosinecom.com>
Date: Fri, 24 Mar 2000 14:55:38 -0800
From: Srinivasan Chakravarthy <cs@cosinecom.com>
Organization: CoSine Communications Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: nat@certworks.net, l2tp@ipsec.org
Subject: [Fwd: L2TP tunnel authentication in Win2000.]
Content-Type: multipart/mixed; boundary="------------E6DF51EDC90AD93320245531"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

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

Oops, it is my mistake - i didnt see properly that you have added a value and
NOT a key in the registery.

--------------E6DF51EDC90AD93320245531
Content-Type: message/rfc822
Content-Disposition: inline

Message-ID: <38DBF014.2010DC33@cosinecom.com>
Date: Fri, 24 Mar 2000 14:45:41 -0800
From: Srinivasan Chakravarthy <cs@cosinecom.com>
Organization: CoSine Communications Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: gwz@cisco.com
CC: nat@certworks.net, l2tp@ipsec.org
Subject: Re: L2TP tunnel authentication in Win2000.
References: <38DAF33A.2345BA37@cosinecom.com>
		<NDBBIHMPILAAGDHPCIOPOENLCAAA.gwz@cisco.com> <20000324215730T.not@iri.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Glen Zorn,

L2TP tunnel authentication is enabled in W2K after i made the changes you suggested. Thanks for your help.

Hi Nat,

I am using W2K prof LAC client to dial. I could see the W2K sending the challenge AVP. Do you still see the
problem ? Are you adding the Key in the registery or a value ?

Thanks & Regards,

Srinivasan.


nat@certworks.net wrote:

>   Hi,
>
> From: "Glen Zorn" <gwz@cisco.com>
> Subject: RE: L2TP tunnel authentication in Win2000.
> Date: Thu, 23 Mar 2000 22:57:29 -0800
>
> > Try this:
> >
> > Turning on L2TP Tunnel Auth
> > Registry key:
> >   HKLM/SYSTEM/CurrentControlSet/Control/Class
> > Look for a GUID, the first component of which ends in 72 (e.g.,
> > 4D36E972-E325-11CE-BFC1-08002BE10318.  Under this key, find the key with
> > DriverDesc=WAN Miniport (L2TP).  Add a REG_SZ value called Password and set
> > the value to the desired shared secret.  The same secret is used for all
> > connections and the L2TP driver will always negotiate tunnel authentication
> > if this value exists.
>
>   Is this Windows 2000(server/professional) LAC Client or LNS ?
>
>   I'm try W2K Pro following setting, but it was not work ...
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001]
> "MaxVcs"=dword:000003e8
> "MinWanEndpoints"=dword:00000000
> "MaxWanEndpoints"=dword:000003e8
> "WanEndpoints"=dword:00000002
> "Characteristics"=dword:00000029
> "ComponentId"="ms_l2tpminiport"
> "InfPath"="netrasa.inf"
> "InfSection"="Ndi-Mp-L2tp"
> "ProviderName"="Microsoft"
> "DriverDateData"=hex:00,40,4b,de,e9,27,bf,01
> "DriverDate"="11-6-1999"
> "DriverVersion"="5.0.2175.1"
> "MatchingDeviceId"="ms_l2tpminiport"
> "DriverDesc"="WAN Mini Port (L2TP)"
> "NetCfgInstanceId"="{2A515228-EC05-421C-AE4E-6E3FA1763DA6}"
> "EnableForRas"=dword:00000001
> "EnableForRouting"=dword:00000000
> "Password"="TEST-L2TP-TEST"
> ^^^^^^^^^^^^^^^^^ Added this value.
>
>   BTW, The W2K LAC Client have LNS name?
>
>   I'm not found Register value on W2K.
>
>   Thanks,
>
> ====
> Naoto "nat" MATSUMOTO <nat@certworks.net>


--------------E6DF51EDC90AD93320245531--



From owner-l2tp@ipsec.org  Fri Mar 24 20:11:18 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22762
	for <l2tpext-archive@odin.ietf.org>; Fri, 24 Mar 2000 20:11:15 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA03866; Fri, 24 Mar 2000 14:47:39 -0800 (PST)
Received: from blue.cosinecom.com (proxy4.cosinecom.com [208.248.148.132]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA03862 for <l2tp@ipsec.org>; Fri, 24 Mar 2000 14:47:10 -0800 (PST)
Received: from cosinecom.com by blue.cosinecom.com (8.8.8+Sun/SMI-SVR4)
	id OAA08368; Fri, 24 Mar 2000 14:44:55 -0800 (PST)
Message-ID: <38DBF014.2010DC33@cosinecom.com>
Date: Fri, 24 Mar 2000 14:45:41 -0800
From: Srinivasan Chakravarthy <cs@cosinecom.com>
Organization: CoSine Communications Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: gwz@cisco.com
CC: nat@certworks.net, l2tp@ipsec.org
Subject: Re: L2TP tunnel authentication in Win2000.
References: <38DAF33A.2345BA37@cosinecom.com>
		<NDBBIHMPILAAGDHPCIOPOENLCAAA.gwz@cisco.com> <20000324215730T.not@iri.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Glen Zorn,

L2TP tunnel authentication is enabled in W2K after i made the changes you suggested. Thanks for your help.

Hi Nat,

I am using W2K prof LAC client to dial. I could see the W2K sending the challenge AVP. Do you still see the
problem ? Are you adding the Key in the registery or a value ?

Thanks & Regards,

Srinivasan.


nat@certworks.net wrote:

>   Hi,
>
> From: "Glen Zorn" <gwz@cisco.com>
> Subject: RE: L2TP tunnel authentication in Win2000.
> Date: Thu, 23 Mar 2000 22:57:29 -0800
>
> > Try this:
> >
> > Turning on L2TP Tunnel Auth
> > Registry key:
> >   HKLM/SYSTEM/CurrentControlSet/Control/Class
> > Look for a GUID, the first component of which ends in 72 (e.g.,
> > 4D36E972-E325-11CE-BFC1-08002BE10318.  Under this key, find the key with
> > DriverDesc=WAN Miniport (L2TP).  Add a REG_SZ value called Password and set
> > the value to the desired shared secret.  The same secret is used for all
> > connections and the L2TP driver will always negotiate tunnel authentication
> > if this value exists.
>
>   Is this Windows 2000(server/professional) LAC Client or LNS ?
>
>   I'm try W2K Pro following setting, but it was not work ...
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001]
> "MaxVcs"=dword:000003e8
> "MinWanEndpoints"=dword:00000000
> "MaxWanEndpoints"=dword:000003e8
> "WanEndpoints"=dword:00000002
> "Characteristics"=dword:00000029
> "ComponentId"="ms_l2tpminiport"
> "InfPath"="netrasa.inf"
> "InfSection"="Ndi-Mp-L2tp"
> "ProviderName"="Microsoft"
> "DriverDateData"=hex:00,40,4b,de,e9,27,bf,01
> "DriverDate"="11-6-1999"
> "DriverVersion"="5.0.2175.1"
> "MatchingDeviceId"="ms_l2tpminiport"
> "DriverDesc"="WAN Mini Port (L2TP)"
> "NetCfgInstanceId"="{2A515228-EC05-421C-AE4E-6E3FA1763DA6}"
> "EnableForRas"=dword:00000001
> "EnableForRouting"=dword:00000000
> "Password"="TEST-L2TP-TEST"
> ^^^^^^^^^^^^^^^^^ Added this value.
>
>   BTW, The W2K LAC Client have LNS name?
>
>   I'm not found Register value on W2K.
>
>   Thanks,
>
> ====
> Naoto "nat" MATSUMOTO <nat@certworks.net>



From owner-l2tp@ipsec.org  Sat Mar 25 22:29:05 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22561
	for <l2tpext-archive@odin.ietf.org>; Sat, 25 Mar 2000 22:29:00 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id SAA06696; Sat, 25 Mar 2000 18:03:00 -0800 (PST)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA06692 for <l2tp@ipsec.org>; Sat, 25 Mar 2000 18:02:31 -0800 (PST)
Received: from gwz (oz-syd-dial1-54.cisco.com [144.254.157.55]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id SAA26007; Sat, 25 Mar 2000 18:01:08 -0800 (PST)
From: "Glen Zorn" <gwz@cisco.com>
To: <nat@certworks.net>
Cc: <cs@cosinecom.com>, <l2tp@ipsec.org>
Subject: RE: L2TP tunnel authentication in Win2000.
Date: Sat, 25 Mar 2000 18:00:56 -0800
Message-ID: <NDBBIHMPILAAGDHPCIOPEEONCAAA.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: <20000324215730T.not@iri.co.jp>
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

nat@certworks.net writes:

>
>   Hi,
>
> From: "Glen Zorn" <gwz@cisco.com>
> Subject: RE: L2TP tunnel authentication in Win2000.
> Date: Thu, 23 Mar 2000 22:57:29 -0800
>
> > Try this:
> >
> > Turning on L2TP Tunnel Auth
> > Registry key:
> >   HKLM/SYSTEM/CurrentControlSet/Control/Class
> > Look for a GUID, the first component of which ends in 72 (e.g.,
> > 4D36E972-E325-11CE-BFC1-08002BE10318.  Under this key, find the key with
> > DriverDesc=WAN Miniport (L2TP).  Add a REG_SZ value called
> Password and set
> > the value to the desired shared secret.  The same secret is used for all
> > connections and the L2TP driver will always negotiate tunnel
> authentication
> > if this value exists.
>
>   Is this Windows 2000(server/professional) LAC Client or LNS ?

As I recall, the same setting works on all versions, LAC or LNS; however,
it's been at least 6 months since I dealt with this, and I don't have a copy
of Win2K handy to play with.  It's also possible (though unlikely) that a
last minute change was made after I left MSFT.  There must be someone on
this list from Microsoft, though, so I'll defer to their expertise. Sorry.

>
>   I'm try W2K Pro following setting, but it was not work ...
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E9
> 72-E325-11CE-BFC1-08002BE10318}\0001]
> "MaxVcs"=dword:000003e8
> "MinWanEndpoints"=dword:00000000
> "MaxWanEndpoints"=dword:000003e8
> "WanEndpoints"=dword:00000002
> "Characteristics"=dword:00000029
> "ComponentId"="ms_l2tpminiport"
> "InfPath"="netrasa.inf"
> "InfSection"="Ndi-Mp-L2tp"
> "ProviderName"="Microsoft"
> "DriverDateData"=hex:00,40,4b,de,e9,27,bf,01
> "DriverDate"="11-6-1999"
> "DriverVersion"="5.0.2175.1"
> "MatchingDeviceId"="ms_l2tpminiport"
> "DriverDesc"="WAN Mini Port (L2TP)"
> "NetCfgInstanceId"="{2A515228-EC05-421C-AE4E-6E3FA1763DA6}"
> "EnableForRas"=dword:00000001
> "EnableForRouting"=dword:00000000
> "Password"="TEST-L2TP-TEST"
> ^^^^^^^^^^^^^^^^^ Added this value.
>
>   BTW, The W2K LAC Client have LNS name?
>
>   I'm not found Register value on W2K.
>
>   Thanks,
>
> ====
> Naoto "nat" MATSUMOTO <nat@certworks.net>
>
>



From owner-l2tp@ipsec.org  Tue Mar 28 14:06:45 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25096
	for <l2tpext-archive@odin.ietf.org>; Tue, 28 Mar 2000 14:06:39 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id JAA14655; Tue, 28 Mar 2000 09:27:34 -0800 (PST)
Received: from fsnt.future.futusoft.com ([203.197.140.35]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA14649 for <l2tp@ipsec.org>; Tue, 28 Mar 2000 09:27:16 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000335552@fsnt.future.futusoft.com> for <l2tp@ipsec.org>;
 Tue, 28 Mar 2000 23:05:38 +0530
Received: from himalaya.future.futsoft.com (himalaya.future.futsoft.com [10.0.10.15]) by kailash.future.futsoft.com (8.7.1/8.7.1) with ESMTP id WAA16997 for <l2tp@ipsec.org>; Tue, 28 Mar 2000 22:46:04 +0530
Received: from laxmanb.future.futsoft.com ([10.0.12.128]) by himalaya.future.futsoft.com (8.6.11/8.6.9) with SMTP id WAA20126 for <l2tp@ipsec.org>; Tue, 28 Mar 2000 22:59:00 +0530
Received: by localhost with Microsoft MAPI; Tue, 28 Mar 2000 22:55:18 +0530
Message-Id: <01BF9908.B0333FC0.laxmanb@future.futsoft.com>
From: LAXMANA RAO <laxmanb@future.futsoft.com>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: I need confirmation.................
Date: Tue, 28 Mar 2000 22:55:17 +0530
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
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,
      For tunnel authentication we have to configure the common 
secret(challenge string)  with the remote host name on both sides(LNS and 
LAC).is it right?
How to handle ppp control packets in l2tp if both l2tp and PPP are running 
as two seperate tasks?is it by using event ids?
How to map session interfaces and PPP interfaces?
What is the info required for configuring PPP interfaces, if RADIUS is used 
for authentication?
I may use PPP also for authentication sometimes.
i need confirmation on the above questions.
Thanks and regards
laxman

LAXMANA RAO B
SOFTWARE ENGINEER
FUTURE SOFTWARE PVT.LTD.
CHENNAI,INDIA
PH.NO:91-44-4330550
E-MAIL:laxmanb@future.futsoft.com




From owner-l2tp@ipsec.org  Tue Mar 28 16:39:53 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26986
	for <l2tpext-archive@odin.ietf.org>; Tue, 28 Mar 2000 16:39:50 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id LAA14880; Tue, 28 Mar 2000 11:37:06 -0800 (PST)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id LAA14876 for <l2tp@ipsec.org>; Tue, 28 Mar 2000 11:36:39 -0800 (PST)
Received: by ans2-pub.dttus.com id NAA01508
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Tue, 28 Mar 2000 13:36:31 -0600
Received: by ans2-pub.dttus.com (Internal Mail Agent-3);
  Tue, 28 Mar 2000 13:36:31 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Tue, 28 Mar 2000 13:36:31 -0600
X400-Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Tue, 28 Mar 2000 13:36:31 -0600
X400-Mts-Identifier: [/c=US/admd=TeleMail/prmd=Deloitte/; 0587638E107BD149-MTAUSBNA1DT]
Content-Identifier: 0587638E107BD149
Content-Return: Allowed
X400-Content-Type: P2-1988 ( 22 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Disclose-Recipients: Prohibited
Alternate-Recipient: Allowed
X400-Originator: rverma@dttus.com
X400-Recipients: non-disclosure;
Message-Id: 
  <0587638E107BD149*/c=US/admd=TeleMail/prmd=Deloitte/o=ccMailGW/s=rverma/@MHS>
Date: 28 Mar 2000 13:27:57 -0600
From: Rohit Verma <rverma@dttus.com>
To: l2tp@ipsec.org, laxmanb@future.futsoft.com
Subject: Re: I need confirmation.................
Sender: owner-l2tp@sailpix.com
Precedence: bulk


     
     The questions that you are asking are extremely implementation 
     specific and there may be more than one possible way to do.
     
     >For tunnel authentication we have to configure the common
     >secret(challenge string)  with the remote host name on both sides(LNS 
     >and LAC).is it right?
     The LAC selects the challenge to use based on the LNS specified in the 
     user profile and the LNS searches on the hostname in the SCCRQ.
     
     >How to handle ppp control packets in l2tp if both l2tp and PPP are 
     >running as two seperate tasks?is it by using event ids?
     
     L2TP should be used as a mere transport protocol for PPP. And the way 
     PPP control packets are handled should be no different than data. 
     
     >How to map session interfaces and PPP interfaces?
     
     Each L2TP session maps to a PPP interface. There is some good 
     description about this stuff in the L2TP Mib documentation
     
     >What is the info required for configuring PPP interfaces, if RADIUS 
     >is used for authentication?
     The two things should be mutually exclusive. 
     
>I may use PPP also for authentication sometimes. 
Should not matter.

Regards
Rohit Verma

______________________________ Reply Separator _________________________________
Subject: I need confirmation.................
Author:  laxmanb@future.futsoft.com at Internet-USA
Date:    3/28/00 1:01 PM


Hi,
      For tunnel authentication we have to configure the common
secret(challenge string)  with the remote host name on both sides(LNS and 
LAC).is it right?

How to map session interfaces and PPP interfaces?
What is the info required for configuring PPP interfaces, if RADIUS is used 
for authentication?
I may use PPP also for authentication sometimes. 
i need confirmation on the above questions. 
Thanks and regards
laxman
     
LAXMANA RAO B
SOFTWARE ENGINEER
FUTURE SOFTWARE PVT.LTD.
CHENNAI,INDIA
PH.NO:91-44-4330550
E-MAIL:laxmanb@future.futsoft.com


From owner-l2tp@ipsec.org  Tue Mar 28 23:08:32 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03865
	for <l2tpext-archive@odin.ietf.org>; Tue, 28 Mar 2000 23:08:29 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id SAA15426; Tue, 28 Mar 2000 18:17:07 -0800 (PST)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id SAA15421 for <l2tp@ipsec.org>; Tue, 28 Mar 2000 18:16:35 -0800 (PST)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 28 Mar 2000 14:27:01 -0800 (Pacific Standard Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <H6DTSDC1>; Tue, 28 Mar 2000 14:25:42 -0800
Message-ID: <19398D273324D3118A2B0008C7E9A5690AEC307A@SIT.platinum.corp.microsoft.com>
From: Rob Trace <robt@Exchange.Microsoft.com>
To: "'nat@certworks.net'" <nat@certworks.net>
Cc: "'cs@cosinecom.com'" <cs@cosinecom.com>,
        "'l2tp@ipsec.org'"
	 <l2tp@ipsec.org>,
        "'gwz@cisco.com'" <gwz@cisco.com>
Subject: RE: L2TP tunnel authentication in Win2000.
Date: Tue, 28 Mar 2000 14:25:39 -0800
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

Hi All,

Glen is correct.  This has not changed since he left <g>.

Thanks!!

-Robt

-----Original Message-----
From: Glen Zorn [mailto:gwz@cisco.com]
Sent: Saturday, March 25, 2000 6:01 PM
To: nat@certworks.net
Cc: cs@cosinecom.com; l2tp@ipsec.org
Subject: RE: L2TP tunnel authentication in Win2000.


nat@certworks.net writes:

>
>   Hi,
>
> From: "Glen Zorn" <gwz@cisco.com>
> Subject: RE: L2TP tunnel authentication in Win2000.
> Date: Thu, 23 Mar 2000 22:57:29 -0800
>
> > Try this:
> >
> > Turning on L2TP Tunnel Auth
> > Registry key:
> >   HKLM/SYSTEM/CurrentControlSet/Control/Class
> > Look for a GUID, the first component of which ends in 72 (e.g.,
> > 4D36E972-E325-11CE-BFC1-08002BE10318.  Under this key, find the key with
> > DriverDesc=WAN Miniport (L2TP).  Add a REG_SZ value called
> Password and set
> > the value to the desired shared secret.  The same secret is used for all
> > connections and the L2TP driver will always negotiate tunnel
> authentication
> > if this value exists.
>
>   Is this Windows 2000(server/professional) LAC Client or LNS ?

As I recall, the same setting works on all versions, LAC or LNS; however,
it's been at least 6 months since I dealt with this, and I don't have a copy
of Win2K handy to play with.  It's also possible (though unlikely) that a
last minute change was made after I left MSFT.  There must be someone on
this list from Microsoft, though, so I'll defer to their expertise. Sorry.

>
>   I'm try W2K Pro following setting, but it was not work ...
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E9
> 72-E325-11CE-BFC1-08002BE10318}\0001]
> "MaxVcs"=dword:000003e8
> "MinWanEndpoints"=dword:00000000
> "MaxWanEndpoints"=dword:000003e8
> "WanEndpoints"=dword:00000002
> "Characteristics"=dword:00000029
> "ComponentId"="ms_l2tpminiport"
> "InfPath"="netrasa.inf"
> "InfSection"="Ndi-Mp-L2tp"
> "ProviderName"="Microsoft"
> "DriverDateData"=hex:00,40,4b,de,e9,27,bf,01
> "DriverDate"="11-6-1999"
> "DriverVersion"="5.0.2175.1"
> "MatchingDeviceId"="ms_l2tpminiport"
> "DriverDesc"="WAN Mini Port (L2TP)"
> "NetCfgInstanceId"="{2A515228-EC05-421C-AE4E-6E3FA1763DA6}"
> "EnableForRas"=dword:00000001
> "EnableForRouting"=dword:00000000
> "Password"="TEST-L2TP-TEST"
> ^^^^^^^^^^^^^^^^^ Added this value.
>
>   BTW, The W2K LAC Client have LNS name?
>
>   I'm not found Register value on W2K.
>
>   Thanks,
>
> ====
> Naoto "nat" MATSUMOTO <nat@certworks.net>
>
>


From owner-l2tp@ipsec.org  Fri Mar 31 18:06:30 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19131
	for <l2tpext-archive@odin.ietf.org>; Fri, 31 Mar 2000 18:06:24 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id NAA00754; Fri, 31 Mar 2000 13:07:41 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA00738 for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:25 -0800 (PST)
From: Chris_Cormier@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 NAA00869
	for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:13 -0800 (PST)
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 NAA26690
	for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:08 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568B3.0073DD5D ; Fri, 31 Mar 2000 13:05:33 -0800
X-Lotus-FromDomain: 3COM
To: "'L2TP'" <l2tp@ipsec.org>
Message-ID: <882568B3.007310BE.00@hqoutbound.ops.3com.com>
Date: Fri, 31 Mar 2000 12:57:11 -0800
Subject: Protocol Number 115
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk





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


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




From owner-l2tp@ipsec.org  Fri Mar 31 18:08:01 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19142
	for <l2tpext-archive@odin.ietf.org>; Fri, 31 Mar 2000 18:07:55 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id NAA00728; Fri, 31 Mar 2000 13:01:31 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA00723 for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:00:54 -0800 (PST)
From: Chris_Cormier@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 NAA27346;
	Fri, 31 Mar 2000 13:00:43 -0800 (PST)
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 NAA22397;
	Fri, 31 Mar 2000 13:00:43 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568B3.00735EFD ; Fri, 31 Mar 2000 13:00:09 -0800
X-Lotus-FromDomain: 3COM
To: "Leone, Guido" <guido.leone@eds.com>
cc: "'L2TP'" <l2tp@ipsec.org>
Message-ID: <882568B3.007311E1.00@hqoutbound.ops.3com.com>
Date: Fri, 31 Mar 2000 12:57:16 -0800
Subject: Re: Protocol Number 115
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk






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

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

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




From owner-l2tp@ipsec.org  Fri Mar 31 18:08:13 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19154
	for <l2tpext-archive@odin.ietf.org>; Fri, 31 Mar 2000 18:08:11 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id NAA00757; Fri, 31 Mar 2000 13:07:58 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA00740 for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:27 -0800 (PST)
From: Chris_Cormier@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 NAA00900;
	Fri, 31 Mar 2000 13:06:15 -0800 (PST)
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 NAA26751;
	Fri, 31 Mar 2000 13:06:10 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568B3.0073DE4E ; Fri, 31 Mar 2000 13:05:35 -0800
X-Lotus-FromDomain: 3COM
To: Andy Valencia <vandys@zendo.com>
cc: l2tp@ipsec.org
Message-ID: <882568B3.007311E1.00@hqoutbound.ops.3com.com>
Date: Fri, 31 Mar 2000 12:57:17 -0800
Subject: Re: L2TP header compression, link-by-link?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk







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

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

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

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

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




From owner-l2tp@ipsec.org  Fri Mar 31 18:08:17 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19172
	for <l2tpext-archive@odin.ietf.org>; Fri, 31 Mar 2000 18:08:15 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id NAA00722; Fri, 31 Mar 2000 13:00:52 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA00714 for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:00:13 -0800 (PST)
From: Chris_Cormier@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 NAA27140
	for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:00:03 -0800 (PST)
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 NAA22061
	for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:00:02 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568B3.00734DE5 ; Fri, 31 Mar 2000 12:59:25 -0800
X-Lotus-FromDomain: 3COM
Reply-To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
To: "l2tp@ipsec.org" <l2tp@ipsec.org>
Message-ID: <882568B3.00730648.00@hqoutbound.ops.3com.com>
Date: Fri, 31 Mar 2000 12:56:43 -0800
Subject: L2TP with FR access network
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk





Hi,

  Is there any draft for L2TP with FR access network.

Thanks in advance.

Regards,
Arul.






From owner-l2tp@ipsec.org  Fri Mar 31 18:10:28 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19155
	for <l2tpext-archive@odin.ietf.org>; Fri, 31 Mar 2000 18:08:12 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id NAA00756; Fri, 31 Mar 2000 13:07:55 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA00741 for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:27 -0800 (PST)
From: Chris_Cormier@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 NAA00938
	for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:17 -0800 (PST)
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 NAA26830
	for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:16 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568B3.0073DE01 ; Fri, 31 Mar 2000 13:05:34 -0800
X-Lotus-FromDomain: 3COM
To: l2tp@ipsec.org
Message-ID: <882568B3.00731151.00@hqoutbound.ops.3com.com>
Date: Fri, 31 Mar 2000 12:57:16 -0800
Subject: L2TP header compression, link-by-link?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk





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

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

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

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

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

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

Thanks,
Andy Valencia
vandys@zendo.com




From owner-l2tp@ipsec.org  Fri Mar 31 18:22:04 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19273
	for <l2tpext-archive@odin.ietf.org>; Fri, 31 Mar 2000 18:22:02 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id NAA00755; Fri, 31 Mar 2000 13:07:46 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA00739 for <l2tp@ipsec.org>; Fri, 31 Mar 2000 13:06:25 -0800 (PST)
From: Chris_Cormier@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 NAA00896;
	Fri, 31 Mar 2000 13:06:14 -0800 (PST)
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 NAA26754;
	Fri, 31 Mar 2000 13:06:10 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568B3.0073DEA5 ; Fri, 31 Mar 2000 13:05:36 -0800
X-Lotus-FromDomain: 3COM
To: "W. Mark Townsley" <townsley@cisco.com>
cc: l2tp@ipsec.org
Message-ID: <882568B3.007312AA.00@hqoutbound.ops.3com.com>
Date: Fri, 31 Mar 2000 12:57:17 -0800
Subject: Re: L2TP header compression, link-by-link? 
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk





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

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

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

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

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

Andy




