From mailman-admin@ietf.org  Wed Jan  1 09:29:59 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05463
	for <l2tpext-archive@lists.ietf.org>; Wed, 1 Jan 2003 09:29:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h01EblJ16787
	for <l2tpext-archive@lists.ietf.org>; Wed, 1 Jan 2003 09:37:47 -0500
Date: Wed, 01 Jan 2003 09:37:47 -0500
Message-ID: <20030101143747.32165.56959.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: l2tpext-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, l2tpext-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

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


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for l2tpext-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
l2tpext@ietf.org                         ruNF      
https://www1.ietf.org/mailman/options/l2tpext/l2tpext-archive%40lists.ietf.org


From l2tpext-admin@ietf.org  Tue Jan 14 07:54:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22877
	for <l2tpext-archive@lists.ietf.org>; Tue, 14 Jan 2003 07:54:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED5KJ25998;
	Tue, 14 Jan 2003 08:05:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED3qJ25949
	for <l2tpext@optimus.ietf.org>; Tue, 14 Jan 2003 08:03:52 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22818
	for <l2tpext@ietf.org>; Tue, 14 Jan 2003 07:49:13 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0ECp4ZA018113
	for <l2tpext@ietf.org>; Tue, 14 Jan 2003 13:51:04 +0100 (MET)
Received: from cisco.com (stealth-10-32-255-6.cisco.com [10.32.255.6])
	by cisco.com (8.8.8+Sun/8.8.8) with SMTP id NAA22261
	for <l2tpext@ietf.org>; Tue, 14 Jan 2003 13:52:31 +0100 (MET)
Message-ID: <3E2406E2.7070603@cisco.com>
Date: Tue, 14 Jan 2003 13:47:30 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] L2TPEXT Last call for draft-ietf-l2tpext-l2tp-base-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


I will advise the Area Directors on January 28, 2003, to take 
draft-ietf-l2tpext-l2tp-base-05.txt to Proposed Standard unless there is 
substantive comment raised on this list.

Thanks,

- Mark Townsley

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Tue Jan 14 07:55:22 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22911
	for <l2tpext-archive@odin.ietf.org>; Tue, 14 Jan 2003 07:55:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0ED9UG26800
	for l2tpext-archive@odin.ietf.org; Tue, 14 Jan 2003 08:09:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED9UJ26797
	for <l2tpext-web-archive@optimus.ietf.org>; Tue, 14 Jan 2003 08:09:30 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22903
	for <l2tpext-web-archive@ietf.org>; Tue, 14 Jan 2003 07:54:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED5KJ25998;
	Tue, 14 Jan 2003 08:05:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0ED3qJ25949
	for <l2tpext@optimus.ietf.org>; Tue, 14 Jan 2003 08:03:52 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22818
	for <l2tpext@ietf.org>; Tue, 14 Jan 2003 07:49:13 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0ECp4ZA018113
	for <l2tpext@ietf.org>; Tue, 14 Jan 2003 13:51:04 +0100 (MET)
Received: from cisco.com (stealth-10-32-255-6.cisco.com [10.32.255.6])
	by cisco.com (8.8.8+Sun/8.8.8) with SMTP id NAA22261
	for <l2tpext@ietf.org>; Tue, 14 Jan 2003 13:52:31 +0100 (MET)
Message-ID: <3E2406E2.7070603@cisco.com>
Date: Tue, 14 Jan 2003 13:47:30 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] L2TPEXT Last call for draft-ietf-l2tpext-l2tp-base-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I will advise the Area Directors on January 28, 2003, to take 
draft-ietf-l2tpext-l2tp-base-05.txt to Proposed Standard unless there is 
substantive comment raised on this list.

Thanks,

- Mark Townsley

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Tue Jan 14 10:43:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28384
	for <l2tpext-archive@lists.ietf.org>; Tue, 14 Jan 2003 10:43:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFtgJ06096;
	Tue, 14 Jan 2003 10:55:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFSaJ03734
	for <l2tpext@optimus.ietf.org>; Tue, 14 Jan 2003 10:28:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26658;
	Tue, 14 Jan 2003 10:13:56 -0500 (EST)
Message-Id: <200301141513.KAA26658@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org, pwe3@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 14 Jan 2003 10:13:55 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--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 (Version 3)'L2TPv3'
	Author(s)	: J. Laurence, W. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-05.txt
	Pages		: 80
	Date		: 2003-1-13
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the extensions to RFC2661 (L2TPv2)
necessary to provide a basis for tunneling a variety of layer 2 data
link types across a packet switched network (such as an IP network).

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-base-05.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-base-05.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:	<2003-1-13142132.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-l2tp-base-05.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Tue Jan 14 10:44:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28424
	for <l2tpext-archive@odin.ietf.org>; Tue, 14 Jan 2003 10:44:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0EFwIr06488
	for l2tpext-archive@odin.ietf.org; Tue, 14 Jan 2003 10:58:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFwIJ06485
	for <l2tpext-web-archive@optimus.ietf.org>; Tue, 14 Jan 2003 10:58:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28412
	for <l2tpext-web-archive@ietf.org>; Tue, 14 Jan 2003 10:43:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFtgJ06096;
	Tue, 14 Jan 2003 10:55:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EFSaJ03734
	for <l2tpext@optimus.ietf.org>; Tue, 14 Jan 2003 10:28:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26658;
	Tue, 14 Jan 2003 10:13:56 -0500 (EST)
Message-Id: <200301141513.KAA26658@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org, pwe3@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 14 Jan 2003 10:13:55 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--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 (Version 3)'L2TPv3'
	Author(s)	: J. Laurence, W. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-05.txt
	Pages		: 80
	Date		: 2003-1-13
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the extensions to RFC2661 (L2TPv2)
necessary to provide a basis for tunneling a variety of layer 2 data
link types across a packet switched network (such as an IP network).

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-base-05.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-base-05.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:	<2003-1-13142132.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-l2tp-base-05.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Jan 15 09:48:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28788
	for <l2tpext-archive@lists.ietf.org>; Wed, 15 Jan 2003 09:48:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FExjJ15217;
	Wed, 15 Jan 2003 09:59:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FEwNJ15176
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 09:58:23 -0500
Received: from gore.nocrew.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28726
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 09:43:12 -0500 (EST)
Received: from gore.nocrew.org (magnus@localhost [127.0.0.1])
	by gore.nocrew.org (8.12.4/8.12.4) with ESMTP id h0FEmp2F025121
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 15:48:51 +0100
Received: from localhost (magnus@localhost)
	by gore.nocrew.org (8.12.4/8.12.4/Submit) with ESMTP id h0FEmpwH025118
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 15:48:51 +0100
X-Authentication-Warning: gore.nocrew.org: magnus owned process doing -bs
Date: Wed, 15 Jan 2003 15:48:51 +0100 (CET)
From: =?iso-8859-1?Q?Magnus_Lundstr=F6m?= <magnus@detached.net>
X-Sender: magnus@gore.nocrew.org
To: l2tpext@ietf.org
Message-ID: <Pine.LNX.4.21.0301151543500.16284-100000@gore.nocrew.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [L2tpext] AVP type values are TBA
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>


Hello

I feel really stupid asking this, but how is one supposed to implement L2TPv3
according to the draft when some mandatory AVPs dont have the attribe type assigned?

After all, Cisco somehow managed to implement it.

Regards,
Magnus



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Jan 15 09:49:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28806
	for <l2tpext-archive@odin.ietf.org>; Wed, 15 Jan 2003 09:49:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FF3ur15419
	for l2tpext-archive@odin.ietf.org; Wed, 15 Jan 2003 10:03:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FF3uJ15416
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 15 Jan 2003 10:03:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28802
	for <l2tpext-web-archive@ietf.org>; Wed, 15 Jan 2003 09:48:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FExjJ15217;
	Wed, 15 Jan 2003 09:59:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FEwNJ15176
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 09:58:23 -0500
Received: from gore.nocrew.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28726
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 09:43:12 -0500 (EST)
Received: from gore.nocrew.org (magnus@localhost [127.0.0.1])
	by gore.nocrew.org (8.12.4/8.12.4) with ESMTP id h0FEmp2F025121
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 15:48:51 +0100
Received: from localhost (magnus@localhost)
	by gore.nocrew.org (8.12.4/8.12.4/Submit) with ESMTP id h0FEmpwH025118
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 15:48:51 +0100
X-Authentication-Warning: gore.nocrew.org: magnus owned process doing -bs
Date: Wed, 15 Jan 2003 15:48:51 +0100 (CET)
From: =?iso-8859-1?Q?Magnus_Lundstr=F6m?= <magnus@detached.net>
X-Sender: magnus@gore.nocrew.org
To: l2tpext@ietf.org
Message-ID: <Pine.LNX.4.21.0301151543500.16284-100000@gore.nocrew.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [L2tpext] AVP type values are TBA
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>


Hello

I feel really stupid asking this, but how is one supposed to implement L2TPv3
according to the draft when some mandatory AVPs dont have the attribe type assigned?

After all, Cisco somehow managed to implement it.

Regards,
Magnus



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Jan 15 09:56:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29027
	for <l2tpext-archive@lists.ietf.org>; Wed, 15 Jan 2003 09:56:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FF8hJ16376;
	Wed, 15 Jan 2003 10:08:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FF7nJ16315
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 10:07:49 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28923
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 09:52:38 -0500 (EST)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0FEuaj6019391;
	Wed, 15 Jan 2003 09:56:37 -0500 (EST)
Received: from dhcp-64-102-60-179.cisco.com (dhcp-64-102-60-179.cisco.com [64.102.60.179])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABD93800;
	Wed, 15 Jan 2003 09:55:51 -0500 (EST)
Date: Wed, 15 Jan 2003 09:55:51 -0500 (Eastern Standard Time)
From: Skip Booth <ebooth@cisco.com>
To: =?iso-8859-1?Q?Magnus_Lundstr=F6m?= <magnus@detached.net>
cc: l2tpext@ietf.org
Subject: Re: [L2tpext] AVP type values are TBA
In-Reply-To: <Pine.LNX.4.21.0301151543500.16284-100000@gore.nocrew.org>
Message-ID: <Pine.WNT.4.44.0301150952150.1888-100000@EBOOTH-W2K.amer.cisco.com>
X-Warning: UNAuthenticated Sender
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0FF7nJ16316
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit



On Wed, 15 Jan 2003, [iso-8859-1] Magnus Lundström wrote:

>
> Hello
>
> I feel really stupid asking this, but how is one supposed to implement L2TPv3
> according to the draft when some mandatory AVPs dont have the attribe type
> assigned?

You would implement it using vendor specific AVPs.  Obviously you can't
interoperate with other vendors using that method, but you can talk to yourself
:)

>
> After all, Cisco somehow managed to implement it.

Our current implementation is using Cisco AVPs.  As soon as the AVP numbers are
allocated by IANA, we plan to cut over immediately.

I believe Mark is just waiting for last call to finish and then he'll issue the
request for the AVP numbers.

-Skip

>
> Regards,
> Magnus
>
>
>
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
>

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Jan 15 09:57:45 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29057
	for <l2tpext-archive@odin.ietf.org>; Wed, 15 Jan 2003 09:57:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FFCPa16529
	for l2tpext-archive@odin.ietf.org; Wed, 15 Jan 2003 10:12:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFCPJ16526
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 15 Jan 2003 10:12:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29054
	for <l2tpext-web-archive@ietf.org>; Wed, 15 Jan 2003 09:57:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FF8hJ16376;
	Wed, 15 Jan 2003 10:08:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FF7nJ16315
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 10:07:49 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28923
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 09:52:38 -0500 (EST)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0FEuaj6019391;
	Wed, 15 Jan 2003 09:56:37 -0500 (EST)
Received: from dhcp-64-102-60-179.cisco.com (dhcp-64-102-60-179.cisco.com [64.102.60.179])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ABD93800;
	Wed, 15 Jan 2003 09:55:51 -0500 (EST)
Date: Wed, 15 Jan 2003 09:55:51 -0500 (Eastern Standard Time)
From: Skip Booth <ebooth@cisco.com>
To: =?iso-8859-1?Q?Magnus_Lundstr=F6m?= <magnus@detached.net>
cc: l2tpext@ietf.org
Subject: Re: [L2tpext] AVP type values are TBA
In-Reply-To: <Pine.LNX.4.21.0301151543500.16284-100000@gore.nocrew.org>
Message-ID: <Pine.WNT.4.44.0301150952150.1888-100000@EBOOTH-W2K.amer.cisco.com>
X-Warning: UNAuthenticated Sender
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id h0FF7nJ16316
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



On Wed, 15 Jan 2003, [iso-8859-1] Magnus Lundström wrote:

>
> Hello
>
> I feel really stupid asking this, but how is one supposed to implement L2TPv3
> according to the draft when some mandatory AVPs dont have the attribe type
> assigned?

You would implement it using vendor specific AVPs.  Obviously you can't
interoperate with other vendors using that method, but you can talk to yourself
:)

>
> After all, Cisco somehow managed to implement it.

Our current implementation is using Cisco AVPs.  As soon as the AVP numbers are
allocated by IANA, we plan to cut over immediately.

I believe Mark is just waiting for last call to finish and then he'll issue the
request for the AVP numbers.

-Skip

>
> Regards,
> Magnus
>
>
>
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
>

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Jan 15 10:11:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29332
	for <l2tpext-archive@lists.ietf.org>; Wed, 15 Jan 2003 10:11:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFPBJ17064;
	Wed, 15 Jan 2003 10:25:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFIUJ16769
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 10:18:30 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29205
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 10:03:19 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0FF55uK005403;
	Wed, 15 Jan 2003 16:05:05 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp129.cisco.com [10.61.64.129])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA07956;
	Wed, 15 Jan 2003 16:06:32 +0100 (MET)
Message-ID: <3E2577CA.4000100@cisco.com>
Date: Wed, 15 Jan 2003 16:01:30 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Magnus_Lundstr=F6m?= <magnus@detached.net>
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] AVP type values are TBA
References: <Pine.LNX.4.21.0301151543500.16284-100000@gore.nocrew.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit


Magnus Lundström wrote:
> Hello
> 
> I feel really stupid asking this, but how is one supposed to implement L2TPv3
> according to the draft when some mandatory AVPs dont have the attribe type assigned?

Before RFC3438, which was just published last month, L2TP AVP numbers could only 
be assigned by the RFC Editor upon publication of the RFC itself (see the IANA 
Considerations of RFC2661). The restrictions are now a bit more loose, and if we 
pass WG last call, I personally think we can safely request AVPs from the IANA 
controlled IETF Vendor ID number space.

> 
> After all, Cisco somehow managed to implement it.

Cisco's current pre-rfc implementation uses Vendor-Specific AVPs which follow 
the draft very closely, but with numbers defined within the Cisco Vendor ID 
number space for the new AVPs. As soon as we have IANA numbers, we will move to 
the numbers assigned (likely supporting both indefinitely).

Thanks,

- Mark

> 
> Regards,
> Magnus
> 
> 
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
> 


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Jan 15 10:17:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29519
	for <l2tpext-archive@odin.ietf.org>; Wed, 15 Jan 2003 10:17:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FFVl317562
	for l2tpext-archive@odin.ietf.org; Wed, 15 Jan 2003 10:31:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFVlJ17559
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 15 Jan 2003 10:31:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29513
	for <l2tpext-web-archive@ietf.org>; Wed, 15 Jan 2003 10:16:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFPBJ17064;
	Wed, 15 Jan 2003 10:25:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFIUJ16769
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 10:18:30 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29205
	for <l2tpext@ietf.org>; Wed, 15 Jan 2003 10:03:19 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0FF55uK005403;
	Wed, 15 Jan 2003 16:05:05 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp129.cisco.com [10.61.64.129])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA07956;
	Wed, 15 Jan 2003 16:06:32 +0100 (MET)
Message-ID: <3E2577CA.4000100@cisco.com>
Date: Wed, 15 Jan 2003 16:01:30 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Magnus_Lundstr=F6m?= <magnus@detached.net>
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] AVP type values are TBA
References: <Pine.LNX.4.21.0301151543500.16284-100000@gore.nocrew.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Magnus Lundström wrote:
> Hello
> 
> I feel really stupid asking this, but how is one supposed to implement L2TPv3
> according to the draft when some mandatory AVPs dont have the attribe type assigned?

Before RFC3438, which was just published last month, L2TP AVP numbers could only 
be assigned by the RFC Editor upon publication of the RFC itself (see the IANA 
Considerations of RFC2661). The restrictions are now a bit more loose, and if we 
pass WG last call, I personally think we can safely request AVPs from the IANA 
controlled IETF Vendor ID number space.

> 
> After all, Cisco somehow managed to implement it.

Cisco's current pre-rfc implementation uses Vendor-Specific AVPs which follow 
the draft very closely, but with numbers defined within the Cisco Vendor ID 
number space for the new AVPs. As soon as we have IANA numbers, we will move to 
the numbers assigned (likely supporting both indefinitely).

Thanks,

- Mark

> 
> Regards,
> Magnus
> 
> 
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
> 


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Jan 15 12:27:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04196
	for <l2tpext-archive@lists.ietf.org>; Wed, 15 Jan 2003 12:27:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FHcVJ28587;
	Wed, 15 Jan 2003 12:38:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FGmSJ24347
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 11:48:28 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02525;
	Wed, 15 Jan 2003 11:33:17 -0500 (EST)
Message-Id: <200301151633.LAA02525@ietf.org>
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Date: Wed, 15 Jan 2003 11:33:17 -0500
Subject: [L2tpext] Last Call: L2TP Active Discovery Relay for PPPoE to Proposed
 Standard
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>


The IESG has received a request from the Layer Two Tunneling Protocol 
Extensions Working Group to consider L2TP Active Discovery Relay for 
PPPoE <draft-dasilva-l2tp-relaysvc-04.txt> as a Proposed Standard.  

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-29.

Files can be obtained via http://www.ietf.org/internet-drafts/draft-dasilva-l2tp-relaysvc-04.txt



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Jan 15 12:33:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04432
	for <l2tpext-archive@odin.ietf.org>; Wed, 15 Jan 2003 12:33:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FHli929000
	for l2tpext-archive@odin.ietf.org; Wed, 15 Jan 2003 12:47:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FHlhJ28997
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 15 Jan 2003 12:47:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04412
	for <l2tpext-web-archive@ietf.org>; Wed, 15 Jan 2003 12:32:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FHcVJ28587;
	Wed, 15 Jan 2003 12:38:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FGmSJ24347
	for <l2tpext@optimus.ietf.org>; Wed, 15 Jan 2003 11:48:28 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02525;
	Wed, 15 Jan 2003 11:33:17 -0500 (EST)
Message-Id: <200301151633.LAA02525@ietf.org>
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Date: Wed, 15 Jan 2003 11:33:17 -0500
Subject: [L2tpext] Last Call: L2TP Active Discovery Relay for PPPoE to Proposed
 Standard
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>


The IESG has received a request from the Layer Two Tunneling Protocol 
Extensions Working Group to consider L2TP Active Discovery Relay for 
PPPoE <draft-dasilva-l2tp-relaysvc-04.txt> as a Proposed Standard.  

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by 2003-1-29.

Files can be obtained via http://www.ietf.org/internet-drafts/draft-dasilva-l2tp-relaysvc-04.txt



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Thu Jan 16 10:35:58 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13962
	for <l2tpext-archive@lists.ietf.org>; Thu, 16 Jan 2003 10:35:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GFo6J31664;
	Thu, 16 Jan 2003 10:50:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GFmJJ31596
	for <l2tpext@optimus.ietf.org>; Thu, 16 Jan 2003 10:48:19 -0500
Received: from LONMSW03.uk.eu.colt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13861
	for <l2tpext@ietf.org>; Thu, 16 Jan 2003 10:32:37 -0500 (EST)
From: Andreas.Waibel@colt.de
Message-ID: <4403667CFF70F84283D8521D50CF4CF3036E2E54@franoa03.de.eu.colt>
To: l2tpext@ietf.org
Date: Thu, 16 Jan 2003 15:35:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0GFmJJ31597
Subject: [L2tpext] result code for disconnect in the case of L2TP dialout
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Colleagues,

we are currently discussing a special L2TP dialout 
implementation with a big RAS vendor. The szenario 
includes dialout connection initated from a L2TP client.

LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
 
Generally we found RFC 2661 well applicable, however
now we have a problem with the CDN result codes:
 
     Defined Result Code values for the CDN message are:

         0 - Reserved
         1 - Call disconnected due to loss of carrier
         2 - Call disconnected for the reason indicated
             in error code
         3 - Call disconnected for administrative reasons
         4 - Call failed due to lack of appropriate facilities
             being available (temporary condition)
         5 - Call failed due to lack of appropriate facilities being
             available (permanent condition)
         6 - Invalid destination
         7 - Call failed due to no carrier detected
         8 - Call failed due to detection of a busy signal
         9 - Call failed due to lack of a dial tone
         10 - Call was not established within time allotted by LAC
         11 - Call was connected but no appropriate framing was
              detected

What should we return, if 
- the session is terminated because the L2TP session, which had 
initiated it, was normally terminated by the dialin client?
- or if even the corresponding tunnel was lost (in this case we cannot
return anything however would like to store a local code for diagnostics)? 

thank You for Your advice!

best regards

Andreas 

--------------------
Andreas Waibel
COLT Telecom GmbH
Herriotstraße 4
60528 Frankfurt am Main
Tel.: ++49 69 56606 6570
Fax: ++49 69 56606 6350
email: andreas.waibel@colt.de

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Thu Jan 16 10:36:51 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13996
	for <l2tpext-archive@odin.ietf.org>; Thu, 16 Jan 2003 10:36:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0GFq1B31758
	for l2tpext-archive@odin.ietf.org; Thu, 16 Jan 2003 10:52:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GFq1J31755
	for <l2tpext-web-archive@optimus.ietf.org>; Thu, 16 Jan 2003 10:52:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13985
	for <l2tpext-web-archive@ietf.org>; Thu, 16 Jan 2003 10:36:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GFo6J31664;
	Thu, 16 Jan 2003 10:50:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GFmJJ31596
	for <l2tpext@optimus.ietf.org>; Thu, 16 Jan 2003 10:48:19 -0500
Received: from LONMSW03.uk.eu.colt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13861
	for <l2tpext@ietf.org>; Thu, 16 Jan 2003 10:32:37 -0500 (EST)
From: Andreas.Waibel@colt.de
Message-ID: <4403667CFF70F84283D8521D50CF4CF3036E2E54@franoa03.de.eu.colt>
To: l2tpext@ietf.org
Date: Thu, 16 Jan 2003 15:35:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0GFmJJ31597
Subject: [L2tpext] result code for disconnect in the case of L2TP dialout
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Colleagues,

we are currently discussing a special L2TP dialout 
implementation with a big RAS vendor. The szenario 
includes dialout connection initated from a L2TP client.

LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
 
Generally we found RFC 2661 well applicable, however
now we have a problem with the CDN result codes:
 
     Defined Result Code values for the CDN message are:

         0 - Reserved
         1 - Call disconnected due to loss of carrier
         2 - Call disconnected for the reason indicated
             in error code
         3 - Call disconnected for administrative reasons
         4 - Call failed due to lack of appropriate facilities
             being available (temporary condition)
         5 - Call failed due to lack of appropriate facilities being
             available (permanent condition)
         6 - Invalid destination
         7 - Call failed due to no carrier detected
         8 - Call failed due to detection of a busy signal
         9 - Call failed due to lack of a dial tone
         10 - Call was not established within time allotted by LAC
         11 - Call was connected but no appropriate framing was
              detected

What should we return, if 
- the session is terminated because the L2TP session, which had 
initiated it, was normally terminated by the dialin client?
- or if even the corresponding tunnel was lost (in this case we cannot
return anything however would like to store a local code for diagnostics)? 

thank You for Your advice!

best regards

Andreas 

--------------------
Andreas Waibel
COLT Telecom GmbH
Herriotstraße 4
60528 Frankfurt am Main
Tel.: ++49 69 56606 6570
Fax: ++49 69 56606 6350
email: andreas.waibel@colt.de

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Mon Jan 20 21:02:38 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06932
	for <l2tpext-archive@lists.ietf.org>; Mon, 20 Jan 2003 21:02:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0L2IoJ32705;
	Mon, 20 Jan 2003 21:18:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0L2HtJ32683
	for <l2tpext@optimus.ietf.org>; Mon, 20 Jan 2003 21:17:55 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06882
	for <l2tpext@ietf.org>; Mon, 20 Jan 2003 21:00:04 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0L21wqC025195;
	Tue, 21 Jan 2003 03:01:58 +0100 (MET)
Received: from cisco.com (dhcp-128-107-165-88.cisco.com [128.107.165.88])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id DAA29552;
	Tue, 21 Jan 2003 03:03:28 +0100 (MET)
Message-ID: <3E2CA933.8050103@cisco.com>
Date: Tue, 21 Jan 2003 02:58:11 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andreas.Waibel@colt.de
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] result code for disconnect in the case of L2TP dialout
References: <4403667CFF70F84283D8521D50CF4CF3036E2E54@franoa03.de.eu.colt>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit



Andreas.Waibel@colt.de wrote:
> Colleagues,
> 
> we are currently discussing a special L2TP dialout 
> implementation with a big RAS vendor. The szenario 
> includes dialout connection initated from a L2TP client.
> 
> LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
>  
> Generally we found RFC 2661 well applicable, however
> now we have a problem with the CDN result codes:
>  
>      Defined Result Code values for the CDN message are:
> 
>          0 - Reserved
>          1 - Call disconnected due to loss of carrier
>          2 - Call disconnected for the reason indicated
>              in error code
>          3 - Call disconnected for administrative reasons
>          4 - Call failed due to lack of appropriate facilities
>              being available (temporary condition)
>          5 - Call failed due to lack of appropriate facilities being
>              available (permanent condition)
>          6 - Invalid destination
>          7 - Call failed due to no carrier detected
>          8 - Call failed due to detection of a busy signal
>          9 - Call failed due to lack of a dial tone
>          10 - Call was not established within time allotted by LAC
>          11 - Call was connected but no appropriate framing was
>               detected
> 
> What should we return, if 
> - the session is terminated because the L2TP session, which had 
> initiated it, was normally terminated by the dialin client?

The dialin client may cause the LNS to disconnect by sending a PPP Terminate 
Request, or by "hanging up" the line to the LAC. The latter is a "loss of 
carrier" condition, result code 1, RFC3145 may be consulted for the former.

> - or if even the corresponding tunnel was lost (in this case we cannot
> return anything however would like to store a local code for diagnostics)? 

This is subject to interpretation, but perhaps a result code of 2, pointing to 
an error code of of "1 - No control connection exists yet for this LAC-LNS"

> 
> thank You for Your advice!
> 
> best regards
> 
> Andreas 
> 
> --------------------
> Andreas Waibel
> COLT Telecom GmbH
> Herriotstraße 4
> 60528 Frankfurt am Main
> Tel.: ++49 69 56606 6570
> Fax: ++49 69 56606 6350
> email: andreas.waibel@colt.de
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
> 


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Mon Jan 20 21:04:30 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06961
	for <l2tpext-archive@odin.ietf.org>; Mon, 20 Jan 2003 21:04:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0L2LnK00329
	for l2tpext-archive@odin.ietf.org; Mon, 20 Jan 2003 21:21:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0L2LnJ00326
	for <l2tpext-web-archive@optimus.ietf.org>; Mon, 20 Jan 2003 21:21:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06955
	for <l2tpext-web-archive@ietf.org>; Mon, 20 Jan 2003 21:03:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0L2IoJ32705;
	Mon, 20 Jan 2003 21:18:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0L2HtJ32683
	for <l2tpext@optimus.ietf.org>; Mon, 20 Jan 2003 21:17:55 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06882
	for <l2tpext@ietf.org>; Mon, 20 Jan 2003 21:00:04 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0L21wqC025195;
	Tue, 21 Jan 2003 03:01:58 +0100 (MET)
Received: from cisco.com (dhcp-128-107-165-88.cisco.com [128.107.165.88])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id DAA29552;
	Tue, 21 Jan 2003 03:03:28 +0100 (MET)
Message-ID: <3E2CA933.8050103@cisco.com>
Date: Tue, 21 Jan 2003 02:58:11 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andreas.Waibel@colt.de
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] result code for disconnect in the case of L2TP dialout
References: <4403667CFF70F84283D8521D50CF4CF3036E2E54@franoa03.de.eu.colt>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Andreas.Waibel@colt.de wrote:
> Colleagues,
> 
> we are currently discussing a special L2TP dialout 
> implementation with a big RAS vendor. The szenario 
> includes dialout connection initated from a L2TP client.
> 
> LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
>  
> Generally we found RFC 2661 well applicable, however
> now we have a problem with the CDN result codes:
>  
>      Defined Result Code values for the CDN message are:
> 
>          0 - Reserved
>          1 - Call disconnected due to loss of carrier
>          2 - Call disconnected for the reason indicated
>              in error code
>          3 - Call disconnected for administrative reasons
>          4 - Call failed due to lack of appropriate facilities
>              being available (temporary condition)
>          5 - Call failed due to lack of appropriate facilities being
>              available (permanent condition)
>          6 - Invalid destination
>          7 - Call failed due to no carrier detected
>          8 - Call failed due to detection of a busy signal
>          9 - Call failed due to lack of a dial tone
>          10 - Call was not established within time allotted by LAC
>          11 - Call was connected but no appropriate framing was
>               detected
> 
> What should we return, if 
> - the session is terminated because the L2TP session, which had 
> initiated it, was normally terminated by the dialin client?

The dialin client may cause the LNS to disconnect by sending a PPP Terminate 
Request, or by "hanging up" the line to the LAC. The latter is a "loss of 
carrier" condition, result code 1, RFC3145 may be consulted for the former.

> - or if even the corresponding tunnel was lost (in this case we cannot
> return anything however would like to store a local code for diagnostics)? 

This is subject to interpretation, but perhaps a result code of 2, pointing to 
an error code of of "1 - No control connection exists yet for this LAC-LNS"

> 
> thank You for Your advice!
> 
> best regards
> 
> Andreas 
> 
> --------------------
> Andreas Waibel
> COLT Telecom GmbH
> Herriotstraße 4
> 60528 Frankfurt am Main
> Tel.: ++49 69 56606 6570
> Fax: ++49 69 56606 6350
> email: andreas.waibel@colt.de
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
> 


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Jan 22 04:22:07 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20056
	for <l2tpext-archive@lists.ietf.org>; Wed, 22 Jan 2003 04:22:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M9cwJ07014;
	Wed, 22 Jan 2003 04:38:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M9bsJ06869
	for <l2tpext@optimus.ietf.org>; Wed, 22 Jan 2003 04:37:54 -0500
Received: from LONMSW03.uk.eu.colt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20004
	for <l2tpext@ietf.org>; Wed, 22 Jan 2003 04:19:25 -0500 (EST)
From: Andreas.Waibel@colt.de
Message-ID: <4403667CFF70F84283D8521D50CF4CF3036E2E87@franoa03.de.eu.colt>
To: l2tpext@ietf.org
Subject: AW: [L2tpext] result code for disconnect in the case of L2TP dial
	out
Date: Wed, 22 Jan 2003 09:22:46 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0M9btJ06870
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Mark,

thank You for Your response. 

> > What should we return, if 
> > - the session is terminated because the L2TP session, which had 
> > initiated it, was normally terminated by the dialin client?
> 
> The dialin client may cause the LNS to disconnect by sending 
> a PPP Terminate 
> Request, or by "hanging up" the line to the LAC. The latter 
> is a "loss of 
> carrier" condition, result code 1, RFC3145 may be consulted 
> for the former.

However, in this case there is no dialin client, as it is dialout.
There is a L2TP client who had initiated the dialout via L2TP. He 
requests the RAS to disconnect the phone line session by closing 
the L2TP session. So the carrier was not really lost, but actively 
disconnected by the RAS as a reaction to a termination request by 
the L2TP client. There appears to be no code for an intended disconnect 
from the network side.

> > - or if even the corresponding tunnel was lost (in this 
> case we cannot
> > return anything however would like to store a local code 
> for diagnostics)? 
> 
> This is subject to interpretation, but perhaps a result code 
> of 2, pointing to 
> an error code of of "1 - No control connection exists yet for 
> this LAC-LNS"

I aggree. That's probably the best applicable solution.

best regards

Andreas

> -----Ursprüngliche Nachricht-----
> Von: W. Mark Townsley [mailto:townsley@cisco.com]
> Gesendet am: Dienstag, 21. Januar 2003 02:58
> An: Waibel, Andreas
> Cc: l2tpext@ietf.org
> Betreff: Re: [L2tpext] result code for disconnect in the case of L2TP
> dialout
> 
> 
> 
> Andreas.Waibel@colt.de wrote:
> > Colleagues,
> > 
> > we are currently discussing a special L2TP dialout 
> > implementation with a big RAS vendor. The szenario 
> > includes dialout connection initated from a L2TP client.
> > 
> > LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
> >  
> > Generally we found RFC 2661 well applicable, however
> > now we have a problem with the CDN result codes:
> >  
> >      Defined Result Code values for the CDN message are:
> > 
> >          0 - Reserved
> >          1 - Call disconnected due to loss of carrier
> >          2 - Call disconnected for the reason indicated
> >              in error code
> >          3 - Call disconnected for administrative reasons
> >          4 - Call failed due to lack of appropriate facilities
> >              being available (temporary condition)
> >          5 - Call failed due to lack of appropriate facilities being
> >              available (permanent condition)
> >          6 - Invalid destination
> >          7 - Call failed due to no carrier detected
> >          8 - Call failed due to detection of a busy signal
> >          9 - Call failed due to lack of a dial tone
> >          10 - Call was not established within time allotted by LAC
> >          11 - Call was connected but no appropriate framing was
> >               detected
> > 
> > What should we return, if 
> > - the session is terminated because the L2TP session, which had 
> > initiated it, was normally terminated by the dialin client?
> 
> The dialin client may cause the LNS to disconnect by sending 
> a PPP Terminate 
> Request, or by "hanging up" the line to the LAC. The latter 
> is a "loss of 
> carrier" condition, result code 1, RFC3145 may be consulted 
> for the former.
> 
> > - or if even the corresponding tunnel was lost (in this 
> case we cannot
> > return anything however would like to store a local code 
> for diagnostics)? 
> 
> This is subject to interpretation, but perhaps a result code 
> of 2, pointing to 
> an error code of of "1 - No control connection exists yet for 
> this LAC-LNS"
> 
> > 
> > thank You for Your advice!
> > 
> > best regards
> > 
> > Andreas 
> > 
> > --------------------
> > Andreas Waibel
> > COLT Telecom GmbH
> > Herriotstraße 4
> > 60528 Frankfurt am Main
> > Tel.: ++49 69 56606 6570
> > Fax: ++49 69 56606 6350
> > email: andreas.waibel@colt.de
> > 
> > _______________________________________________
> > L2tpext mailing list
> > L2tpext@ietf.org
> > https://www1.ietf.org/mailman/listinfo/l2tpext
> > 
> 
> 
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Jan 22 04:23:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20080
	for <l2tpext-archive@odin.ietf.org>; Wed, 22 Jan 2003 04:23:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0M9f0M07145
	for l2tpext-archive@odin.ietf.org; Wed, 22 Jan 2003 04:41:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M9f0J07142
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 22 Jan 2003 04:41:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20075
	for <l2tpext-web-archive@ietf.org>; Wed, 22 Jan 2003 04:22:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M9cwJ07014;
	Wed, 22 Jan 2003 04:38:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0M9bsJ06869
	for <l2tpext@optimus.ietf.org>; Wed, 22 Jan 2003 04:37:54 -0500
Received: from LONMSW03.uk.eu.colt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20004
	for <l2tpext@ietf.org>; Wed, 22 Jan 2003 04:19:25 -0500 (EST)
From: Andreas.Waibel@colt.de
Message-ID: <4403667CFF70F84283D8521D50CF4CF3036E2E87@franoa03.de.eu.colt>
To: l2tpext@ietf.org
Subject: AW: [L2tpext] result code for disconnect in the case of L2TP dial
	out
Date: Wed, 22 Jan 2003 09:22:46 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0M9btJ06870
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Mark,

thank You for Your response. 

> > What should we return, if 
> > - the session is terminated because the L2TP session, which had 
> > initiated it, was normally terminated by the dialin client?
> 
> The dialin client may cause the LNS to disconnect by sending 
> a PPP Terminate 
> Request, or by "hanging up" the line to the LAC. The latter 
> is a "loss of 
> carrier" condition, result code 1, RFC3145 may be consulted 
> for the former.

However, in this case there is no dialin client, as it is dialout.
There is a L2TP client who had initiated the dialout via L2TP. He 
requests the RAS to disconnect the phone line session by closing 
the L2TP session. So the carrier was not really lost, but actively 
disconnected by the RAS as a reaction to a termination request by 
the L2TP client. There appears to be no code for an intended disconnect 
from the network side.

> > - or if even the corresponding tunnel was lost (in this 
> case we cannot
> > return anything however would like to store a local code 
> for diagnostics)? 
> 
> This is subject to interpretation, but perhaps a result code 
> of 2, pointing to 
> an error code of of "1 - No control connection exists yet for 
> this LAC-LNS"

I aggree. That's probably the best applicable solution.

best regards

Andreas

> -----Ursprüngliche Nachricht-----
> Von: W. Mark Townsley [mailto:townsley@cisco.com]
> Gesendet am: Dienstag, 21. Januar 2003 02:58
> An: Waibel, Andreas
> Cc: l2tpext@ietf.org
> Betreff: Re: [L2tpext] result code for disconnect in the case of L2TP
> dialout
> 
> 
> 
> Andreas.Waibel@colt.de wrote:
> > Colleagues,
> > 
> > we are currently discussing a special L2TP dialout 
> > implementation with a big RAS vendor. The szenario 
> > includes dialout connection initated from a L2TP client.
> > 
> > LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
> >  
> > Generally we found RFC 2661 well applicable, however
> > now we have a problem with the CDN result codes:
> >  
> >      Defined Result Code values for the CDN message are:
> > 
> >          0 - Reserved
> >          1 - Call disconnected due to loss of carrier
> >          2 - Call disconnected for the reason indicated
> >              in error code
> >          3 - Call disconnected for administrative reasons
> >          4 - Call failed due to lack of appropriate facilities
> >              being available (temporary condition)
> >          5 - Call failed due to lack of appropriate facilities being
> >              available (permanent condition)
> >          6 - Invalid destination
> >          7 - Call failed due to no carrier detected
> >          8 - Call failed due to detection of a busy signal
> >          9 - Call failed due to lack of a dial tone
> >          10 - Call was not established within time allotted by LAC
> >          11 - Call was connected but no appropriate framing was
> >               detected
> > 
> > What should we return, if 
> > - the session is terminated because the L2TP session, which had 
> > initiated it, was normally terminated by the dialin client?
> 
> The dialin client may cause the LNS to disconnect by sending 
> a PPP Terminate 
> Request, or by "hanging up" the line to the LAC. The latter 
> is a "loss of 
> carrier" condition, result code 1, RFC3145 may be consulted 
> for the former.
> 
> > - or if even the corresponding tunnel was lost (in this 
> case we cannot
> > return anything however would like to store a local code 
> for diagnostics)? 
> 
> This is subject to interpretation, but perhaps a result code 
> of 2, pointing to 
> an error code of of "1 - No control connection exists yet for 
> this LAC-LNS"
> 
> > 
> > thank You for Your advice!
> > 
> > best regards
> > 
> > Andreas 
> > 
> > --------------------
> > Andreas Waibel
> > COLT Telecom GmbH
> > Herriotstraße 4
> > 60528 Frankfurt am Main
> > Tel.: ++49 69 56606 6570
> > Fax: ++49 69 56606 6350
> > email: andreas.waibel@colt.de
> > 
> > _______________________________________________
> > L2tpext mailing list
> > L2tpext@ietf.org
> > https://www1.ietf.org/mailman/listinfo/l2tpext
> > 
> 
> 
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Tue Jan 28 00:17:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06096
	for <l2tpext-archive@lists.ietf.org>; Tue, 28 Jan 2003 00:17:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S5axJ12295;
	Tue, 28 Jan 2003 00:37:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S5Z9J12232
	for <l2tpext@optimus.ietf.org>; Tue, 28 Jan 2003 00:35:09 -0500
Received: from mtsslvpngway (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06045
	for <l2tpext@ietf.org>; Tue, 28 Jan 2003 00:13:45 -0500 (EST)
Received: (qmail 24379 invoked from network); 28 Jan 2003 05:20:56 -0000
Received: from unknown (HELO multitech.co.in) (192.168.10.1)
  by 0 with SMTP; 28 Jan 2003 05:20:56 -0000
Received: from multitech.co.in ([192.168.1.76])
	by multitech.co.in (8.12.1/8.12.1) with ESMTP id h0S5EgX4003318
	for <l2tpext@ietf.org>; Tue, 28 Jan 2003 10:44:43 +0530
Message-ID: <3E361382.AC256BFA@multitech.co.in>
Date: Tue, 28 Jan 2003 10:52:10 +0530
From: Adharsh Praveen <adarsh@multitech.co.in>
X-Mailer: Mozilla 4.02 [en] (Win95; I)
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: multipart/mixed; boundary="------------08212B5D4D0D515800A0F896"
Subject: [L2tpext] MSL2TP - Freeswan Problems
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

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

Hai 

I am trying the following set up using freeswan 1.98b and MS-L2TP for
WIN 98 SE.


        192.168.1.77            ----         192.168.1.76
  (freeswan 1.98b and l2tpd-0.69 )        ( MS-L2TP WIN 98 )
          (RH Linux 7.3)

The configuration files are attached and it is similar to that mentioned
in Jacco's
document.

http://www.jacco2.dds.nl/networking/msl2tp.html 

I am trying to set up an IPSec connection using PSK.

When I try to connect,freeswan is complaining like this

Jan 27 14:23:57 localhost pluto[3192]: packet from 192.168.1.76:500:
ignoring Vendor ID payload
Jan 27 14:23:57 localhost last message repeated 2 times
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: responding to Main
Mode
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: ignoring Vendor ID
payload
Jan 27 14:23:57 localhost last message repeated 3 times
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: ignoring
informational payload, type IPSEC_INITIAL_CONTACT
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: sent MR3, ISAKMP
SA established
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: peer client ID
payload ID_IPV4_ADDR specifies protocol 17; we only support 0
Jan 27 14:24:02 localhost pluto[3192]: "L2TP-PSK" #1: Quick Mode I1
message is unacceptable because it uses a previously used Message ID
0x53bbf2f9 (perhaps this is a duplicated packet)


I tried adding the parameters in ipsec.conf

leftprotoport=udp/1701
rightprotoport=udp/1701

When I said ipsec auto --add L2TP-PSK, I got the message

ipsec_auto: fatal error in "L2TP-PSK": (/etc/ipsec.conf, line 5) unknown
parameter name "leftprotoport"

any ideas. Am I missing something? 

I am at present not trying with x.509 certificates.

I have been trying this for more than 2 weeks. My Isakmp.log in
192.168.1.76 shows this


1-27: 14:24:25.920  
 1-27: 14:24:25.920 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:24:27.020 Microsoft IPsec VPN\L2TP/IPsec - Initiating IKE
Phase 2 with Client IDs (message id: AD320028)
 1-27: 14:24:27.020   Initiator = IP ADDR=192.168.1.76, prot = 17 port =
1701
 1-27: 14:24:27.020   Responder = IP ADDR=192.168.1.77, prot = 17 port =
1701
 1-27: 14:24:27.020 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(HASH, SA, NON, ID, ID)
 1-27: 14:24:32.020 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 1
 1-27: 14:24:32.020 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:37.070 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 2
 1-27: 14:24:37.070 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:42.070 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 3
 1-27: 14:24:42.070 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:44.980  
 1-27: 14:24:44.980 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:24:47.120 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 4
 1-27: 14:24:47.120 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:52.120 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 5
 1-27: 14:24:52.120 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:57.120 Microsoft IPsec VPN\L2TP/IPsec - Exceeded 5
re-keying attempts (message id: AD320028)
 1-27: 14:26:27.800 IREIKE Shutting down.
 1-27: 14:26:27.850 Microsoft IPsec VPN\L2TP/IPsec - Deleting IKE SA (IP
ADDR=192.168.1.77)
 1-27: 14:26:27.850    MY COOKIE c7 62 3a 2 d 3 2a cc
 1-27: 14:26:27.850    HIS COOKIE 1b a0 e0 80 5d 21 91 19
 1-27: 14:26:27.850 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK INFO *(HASH, DEL)
 1-27: 14:26:27.910 recvfrom () : 2736
 1-27: 14:26:27.910 recvfrom () : 2736
 1-27: 14:27:37.990 Interface added: 192.168.7.5/255.255.255.0 on LAN
"Compex RE100ATX/WOL PCI (NDIS5) Fast Ethernet Adapter".
 1-27: 14:27:37.990 Interface added: 192.168.1.76/255.255.255.0 on LAN
"D-Link DFE-538TX 10/100 Adapter".
 1-27: 14:28:26.600  
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - Initiating IKE
Phase 1 (IP ADDR=192.168.1.77)
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK MM (SA, VID, VID, VID)
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - RECEIVED<<< ISAKMP
OAK MM (SA)
 1-27: 14:28:26.880 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK MM (KE, NON, VID, VID, VID, VID)
 1-27: 14:28:26.880 Microsoft IPsec VPN\L2TP/IPsec - RECEIVED<<< ISAKMP
OAK MM (KE, NON)
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK MM *(ID, HASH, NOTIFY:STATUS_INITIAL_CONTACT)
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - RECEIVED<<< ISAKMP
OAK MM *(ID, HASH)
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - Established IKE SA
 1-27: 14:28:26.930    MY COOKIE 68 64 be 7c 71 2d 7e 35
 1-27: 14:28:26.930    HIS COOKIE bc ed 81 eb 46 ed 9 64
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - Initiating IKE
Phase 2 with Client IDs (message id: F9F2BB53)
 1-27: 14:28:26.930   Initiator = IP ADDR=192.168.1.76, prot = 17 port =
1701
 1-27: 14:28:26.930   Responder = IP ADDR=192.168.1.77, prot = 17 port =
1701
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(HASH, SA, NON, ID, ID)
 1-27: 14:28:31.980 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 1
 1-27: 14:28:31.980 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:36.980 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 2
 1-27: 14:28:36.980 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:41.980 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 3
 1-27: 14:28:41.980 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:47.030 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 4
 1-27: 14:28:47.030 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:51.700  
 1-27: 14:28:51.700 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:28:52.030 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 5
 1-27: 14:28:52.030 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:57.030 Microsoft IPsec VPN\L2TP/IPsec - Exceeded 5
re-keying attempts (message id: F9F2BB53)


Any ideas. 

regards,

adharsh.


-- 
---------------------
Think big
--------------08212B5D4D0D515800A0F896
Content-Type: application/x-unknown-content-type-conf_auto_file; name="ipsec.conf"
Content-Disposition: inline; filename="ipsec.conf"
Content-Transfer-Encoding: base64

Y29ubiBMMlRQLVBTSw0KCWF1dGhieT1zZWNyZXQNCglsZWZ0PTE5Mi4xNjguMS43Nw0KCWxl
ZnRuZXh0aG9wPSVkZWZhdWx0cm91dGUNCgkjbGVmdHByb3RvcG9ydD11ZHAvMTcwMQ0KCXBm
cz1ubw0KCSMgUmVtb3RlIHVzZXINCglyaWdodD0xOTIuMTY4LjEuNzYNCgkjcmlnaHRwcm90
b3BvcnQ9dWRwLzE3MDENCgkjIEF1dGhvcml6ZSB0aGlzIGNvbm5lY3Rpb24gYW5kIHdhaXQg
Zm9yIGNvbm5lY3Rpb24gZnJvbSB1c2VyLg0KCWF1dG89YWRkDQoJa2V5aW5ndHJpZXM9Mw0K

--------------08212B5D4D0D515800A0F896
Content-Type: application/x-unknown-content-type-secrets_auto_file; name="ipsec.secrets"
Content-Disposition: inline; filename="ipsec.secrets"
Content-Transfer-Encoding: base64

MTkyLjE2OC4xLjc3IDE5Mi4xNjguMS43NiA6IFBTSyAic2hhcmVka2V5Ig0K
--------------08212B5D4D0D515800A0F896
Content-Type: application/x-unknown-content-type-conf_auto_file; name="l2tpd.conf"
Content-Disposition: inline; filename="l2tpd.conf"
Content-Transfer-Encoding: base64

OyBbZ2xvYmFsXQkJCQk7IEdsb2JhbCBwYXJhbWV0ZXJzOg0KDQo7IFtsbnMgZGVmYXVsdF0J
CQkJOyBPdXIgZmFsbHRocm91Z2ggTE5TIGRlZmluaXRpb24NCjsgaXAgcmFuZ2UgPSAxOTIu
MTY4LjEuNzAtMTkyLjE2OC4xLjgwCTsgKiBBbGxvY2F0ZSBmcm9tIHRoaXMgSVAgcmFuZ2UN
CjsgbG9jYWwgaXAgPSAxOTIuMTY4LjEuNzcJCTsgKiBPdXIgbG9jYWwgSVAgdG8gdXNlDQo7
IHJlcXVpcmUgY2hhcCA9IHllcwkJCTsgKiBSZXF1aXJlIENIQVAgYXV0aC4gYnkgcGVlcg0K
OyByZWZ1c2UgcGFwID0geWVzCQkJOyAqIFJlZnVzZSBQQVAgYXV0aGVudGljYXRpb24NCjsg
cmVxdWlyZSBhdXRoZW50aWNhdGlvbiA9IHllcwkJOyAqIFJlcXVpcmUgcGVlciB0byBhdXRo
ZW50aWNhdGUNCjsgbmFtZSA9IGxvY2FsaG9zdAkJCTsgKiBSZXBvcnQgdGhpcyBhcyBvdXIg
aG9zdG5hbWUNCjsgcHBwIGRlYnVnID0geWVzCQkJOyAqIFR1cm4gb24gUFBQIGRlYnVnZ2lu
Zw0KOyBwcHBvcHRmaWxlID0gL2V0Yy9wcHAvb3B0aW9ucy5sMnRwZCAgIDsgKiBwcHAgb3B0
aW9ucyBmaWxlDQo7IGxlbmd0aCBiaXQgPSB5ZXMJCQk7ICogVXNlIGxlbmd0aCBiaXQgaW4g
cGF5bG9hZD8NCg==
--------------08212B5D4D0D515800A0F896--

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Tue Jan 28 00:18:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06128
	for <l2tpext-archive@odin.ietf.org>; Tue, 28 Jan 2003 00:18:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0S5d6m13022
	for l2tpext-archive@odin.ietf.org; Tue, 28 Jan 2003 00:39:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S5d6J13019
	for <l2tpext-web-archive@optimus.ietf.org>; Tue, 28 Jan 2003 00:39:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06116
	for <l2tpext-web-archive@ietf.org>; Tue, 28 Jan 2003 00:17:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S5axJ12295;
	Tue, 28 Jan 2003 00:37:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0S5Z9J12232
	for <l2tpext@optimus.ietf.org>; Tue, 28 Jan 2003 00:35:09 -0500
Received: from mtsslvpngway (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06045
	for <l2tpext@ietf.org>; Tue, 28 Jan 2003 00:13:45 -0500 (EST)
Received: (qmail 24379 invoked from network); 28 Jan 2003 05:20:56 -0000
Received: from unknown (HELO multitech.co.in) (192.168.10.1)
  by 0 with SMTP; 28 Jan 2003 05:20:56 -0000
Received: from multitech.co.in ([192.168.1.76])
	by multitech.co.in (8.12.1/8.12.1) with ESMTP id h0S5EgX4003318
	for <l2tpext@ietf.org>; Tue, 28 Jan 2003 10:44:43 +0530
Message-ID: <3E361382.AC256BFA@multitech.co.in>
Date: Tue, 28 Jan 2003 10:52:10 +0530
From: Adharsh Praveen <adarsh@multitech.co.in>
X-Mailer: Mozilla 4.02 [en] (Win95; I)
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: multipart/mixed; boundary="------------08212B5D4D0D515800A0F896"
Subject: [L2tpext] MSL2TP - Freeswan Problems
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

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

Hai 

I am trying the following set up using freeswan 1.98b and MS-L2TP for
WIN 98 SE.


        192.168.1.77            ----         192.168.1.76
  (freeswan 1.98b and l2tpd-0.69 )        ( MS-L2TP WIN 98 )
          (RH Linux 7.3)

The configuration files are attached and it is similar to that mentioned
in Jacco's
document.

http://www.jacco2.dds.nl/networking/msl2tp.html 

I am trying to set up an IPSec connection using PSK.

When I try to connect,freeswan is complaining like this

Jan 27 14:23:57 localhost pluto[3192]: packet from 192.168.1.76:500:
ignoring Vendor ID payload
Jan 27 14:23:57 localhost last message repeated 2 times
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: responding to Main
Mode
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: ignoring Vendor ID
payload
Jan 27 14:23:57 localhost last message repeated 3 times
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: ignoring
informational payload, type IPSEC_INITIAL_CONTACT
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: sent MR3, ISAKMP
SA established
Jan 27 14:23:57 localhost pluto[3192]: "L2TP-PSK" #1: peer client ID
payload ID_IPV4_ADDR specifies protocol 17; we only support 0
Jan 27 14:24:02 localhost pluto[3192]: "L2TP-PSK" #1: Quick Mode I1
message is unacceptable because it uses a previously used Message ID
0x53bbf2f9 (perhaps this is a duplicated packet)


I tried adding the parameters in ipsec.conf

leftprotoport=udp/1701
rightprotoport=udp/1701

When I said ipsec auto --add L2TP-PSK, I got the message

ipsec_auto: fatal error in "L2TP-PSK": (/etc/ipsec.conf, line 5) unknown
parameter name "leftprotoport"

any ideas. Am I missing something? 

I am at present not trying with x.509 certificates.

I have been trying this for more than 2 weeks. My Isakmp.log in
192.168.1.76 shows this


1-27: 14:24:25.920  
 1-27: 14:24:25.920 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:24:27.020 Microsoft IPsec VPN\L2TP/IPsec - Initiating IKE
Phase 2 with Client IDs (message id: AD320028)
 1-27: 14:24:27.020   Initiator = IP ADDR=192.168.1.76, prot = 17 port =
1701
 1-27: 14:24:27.020   Responder = IP ADDR=192.168.1.77, prot = 17 port =
1701
 1-27: 14:24:27.020 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(HASH, SA, NON, ID, ID)
 1-27: 14:24:32.020 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 1
 1-27: 14:24:32.020 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:37.070 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 2
 1-27: 14:24:37.070 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:42.070 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 3
 1-27: 14:24:42.070 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:44.980  
 1-27: 14:24:44.980 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:24:47.120 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 4
 1-27: 14:24:47.120 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:52.120 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: AD320028). Retry count: 5
 1-27: 14:24:52.120 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:24:57.120 Microsoft IPsec VPN\L2TP/IPsec - Exceeded 5
re-keying attempts (message id: AD320028)
 1-27: 14:26:27.800 IREIKE Shutting down.
 1-27: 14:26:27.850 Microsoft IPsec VPN\L2TP/IPsec - Deleting IKE SA (IP
ADDR=192.168.1.77)
 1-27: 14:26:27.850    MY COOKIE c7 62 3a 2 d 3 2a cc
 1-27: 14:26:27.850    HIS COOKIE 1b a0 e0 80 5d 21 91 19
 1-27: 14:26:27.850 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK INFO *(HASH, DEL)
 1-27: 14:26:27.910 recvfrom () : 2736
 1-27: 14:26:27.910 recvfrom () : 2736
 1-27: 14:27:37.990 Interface added: 192.168.7.5/255.255.255.0 on LAN
"Compex RE100ATX/WOL PCI (NDIS5) Fast Ethernet Adapter".
 1-27: 14:27:37.990 Interface added: 192.168.1.76/255.255.255.0 on LAN
"D-Link DFE-538TX 10/100 Adapter".
 1-27: 14:28:26.600  
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - Initiating IKE
Phase 1 (IP ADDR=192.168.1.77)
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK MM (SA, VID, VID, VID)
 1-27: 14:28:26.820 Microsoft IPsec VPN\L2TP/IPsec - RECEIVED<<< ISAKMP
OAK MM (SA)
 1-27: 14:28:26.880 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK MM (KE, NON, VID, VID, VID, VID)
 1-27: 14:28:26.880 Microsoft IPsec VPN\L2TP/IPsec - RECEIVED<<< ISAKMP
OAK MM (KE, NON)
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK MM *(ID, HASH, NOTIFY:STATUS_INITIAL_CONTACT)
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - RECEIVED<<< ISAKMP
OAK MM *(ID, HASH)
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - Established IKE SA
 1-27: 14:28:26.930    MY COOKIE 68 64 be 7c 71 2d 7e 35
 1-27: 14:28:26.930    HIS COOKIE bc ed 81 eb 46 ed 9 64
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - Initiating IKE
Phase 2 with Client IDs (message id: F9F2BB53)
 1-27: 14:28:26.930   Initiator = IP ADDR=192.168.1.76, prot = 17 port =
1701
 1-27: 14:28:26.930   Responder = IP ADDR=192.168.1.77, prot = 17 port =
1701
 1-27: 14:28:26.930 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(HASH, SA, NON, ID, ID)
 1-27: 14:28:31.980 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 1
 1-27: 14:28:31.980 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:36.980 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 2
 1-27: 14:28:36.980 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:41.980 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 3
 1-27: 14:28:41.980 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:47.030 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 4
 1-27: 14:28:47.030 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:51.700  
 1-27: 14:28:51.700 Microsoft IPsec VPN\L2TP/IPsec - Generic entry match
with remote address 192.168.1.77.
 1-27: 14:28:52.030 Microsoft IPsec VPN\L2TP/IPsec - QM re-keying timed
out (message id: F9F2BB53). Retry count: 5
 1-27: 14:28:52.030 Microsoft IPsec VPN\L2TP/IPsec - SENDING>>>> ISAKMP
OAK QM *(Retransmission)
 1-27: 14:28:57.030 Microsoft IPsec VPN\L2TP/IPsec - Exceeded 5
re-keying attempts (message id: F9F2BB53)


Any ideas. 

regards,

adharsh.


-- 
---------------------
Think big
--------------08212B5D4D0D515800A0F896
Content-Type: application/x-unknown-content-type-conf_auto_file; name="ipsec.conf"
Content-Disposition: inline; filename="ipsec.conf"
Content-Transfer-Encoding: base64

Y29ubiBMMlRQLVBTSw0KCWF1dGhieT1zZWNyZXQNCglsZWZ0PTE5Mi4xNjguMS43Nw0KCWxl
ZnRuZXh0aG9wPSVkZWZhdWx0cm91dGUNCgkjbGVmdHByb3RvcG9ydD11ZHAvMTcwMQ0KCXBm
cz1ubw0KCSMgUmVtb3RlIHVzZXINCglyaWdodD0xOTIuMTY4LjEuNzYNCgkjcmlnaHRwcm90
b3BvcnQ9dWRwLzE3MDENCgkjIEF1dGhvcml6ZSB0aGlzIGNvbm5lY3Rpb24gYW5kIHdhaXQg
Zm9yIGNvbm5lY3Rpb24gZnJvbSB1c2VyLg0KCWF1dG89YWRkDQoJa2V5aW5ndHJpZXM9Mw0K

--------------08212B5D4D0D515800A0F896
Content-Type: application/x-unknown-content-type-secrets_auto_file; name="ipsec.secrets"
Content-Disposition: inline; filename="ipsec.secrets"
Content-Transfer-Encoding: base64

MTkyLjE2OC4xLjc3IDE5Mi4xNjguMS43NiA6IFBTSyAic2hhcmVka2V5Ig0K
--------------08212B5D4D0D515800A0F896
Content-Type: application/x-unknown-content-type-conf_auto_file; name="l2tpd.conf"
Content-Disposition: inline; filename="l2tpd.conf"
Content-Transfer-Encoding: base64

OyBbZ2xvYmFsXQkJCQk7IEdsb2JhbCBwYXJhbWV0ZXJzOg0KDQo7IFtsbnMgZGVmYXVsdF0J
CQkJOyBPdXIgZmFsbHRocm91Z2ggTE5TIGRlZmluaXRpb24NCjsgaXAgcmFuZ2UgPSAxOTIu
MTY4LjEuNzAtMTkyLjE2OC4xLjgwCTsgKiBBbGxvY2F0ZSBmcm9tIHRoaXMgSVAgcmFuZ2UN
CjsgbG9jYWwgaXAgPSAxOTIuMTY4LjEuNzcJCTsgKiBPdXIgbG9jYWwgSVAgdG8gdXNlDQo7
IHJlcXVpcmUgY2hhcCA9IHllcwkJCTsgKiBSZXF1aXJlIENIQVAgYXV0aC4gYnkgcGVlcg0K
OyByZWZ1c2UgcGFwID0geWVzCQkJOyAqIFJlZnVzZSBQQVAgYXV0aGVudGljYXRpb24NCjsg
cmVxdWlyZSBhdXRoZW50aWNhdGlvbiA9IHllcwkJOyAqIFJlcXVpcmUgcGVlciB0byBhdXRo
ZW50aWNhdGUNCjsgbmFtZSA9IGxvY2FsaG9zdAkJCTsgKiBSZXBvcnQgdGhpcyBhcyBvdXIg
aG9zdG5hbWUNCjsgcHBwIGRlYnVnID0geWVzCQkJOyAqIFR1cm4gb24gUFBQIGRlYnVnZ2lu
Zw0KOyBwcHBvcHRmaWxlID0gL2V0Yy9wcHAvb3B0aW9ucy5sMnRwZCAgIDsgKiBwcHAgb3B0
aW9ucyBmaWxlDQo7IGxlbmd0aCBiaXQgPSB5ZXMJCQk7ICogVXNlIGxlbmd0aCBiaXQgaW4g
cGF5bG9hZD8NCg==
--------------08212B5D4D0D515800A0F896--

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



