From mailman-admin@ietf.org  Sun Jun  1 09:52:33 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 JAA09424
	for <l2tpext-archive@lists.ietf.org>; Sun, 1 Jun 2003 09:52:33 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51Dq7B30529
	for <l2tpext-archive@lists.ietf.org>; Sun, 1 Jun 2003 09:52:07 -0400
Date: Sun, 01 Jun 2003 09:52:07 -0400
Message-ID: <20030601135207.11734.17616.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  Sun Jun  1 10:39:27 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 KAA13548
	for <l2tpext-archive@lists.ietf.org>; Sun, 1 Jun 2003 10:39:27 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51EYGB10657;
	Sun, 1 Jun 2003 10:34:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51EVEB09263
	for <l2tpext@optimus.ietf.org>; Sun, 1 Jun 2003 10:31:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12884
	for <l2tpext@ietf.org>; Sun, 1 Jun 2003 10:31:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MTpt-0007Td-00
	for l2tpext@ietf.org; Sun, 01 Jun 2003 10:29:25 -0400
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 19MTpr-0007TF-00
	for l2tpext@ietf.org; Sun, 01 Jun 2003 10:29:24 -0400
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Sun, 01 Jun 2003 17:32:11 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <KCY9SH7F>; Sun, 1 Jun 2003 17:26:42 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085F74@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>, l2tpext@ietf.org
Subject: RE: [L2tpext] Call for L2TPEXT Agenda Items for the 57th IETF - V
	ienna, Austria
Date: Sun, 1 Jun 2003 17:26:34 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
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>

Mark,
I would like to ask for a slot at the Vienna L2TPEXT Session.

Name of presenter: Sharon Galtzur sharon@axerra.com 
It is possible that it will be de-facto presented by 
Sasha Vainshtein (sasha@axerra.com)

Title of presentation: L2TP v3 Graceful Restart

Internet draft:
http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-00.txt

Amount of time: 10 minutes


Thanks,

Sharon Galtzur


-----Original Message-----
From: W. Mark Townsley [mailto:townsley@cisco.com]
Sent: Saturday, May 31, 2003 8:53 AM
To: l2tpext@ietf.org
Subject: [L2tpext] Call for L2TPEXT Agenda Items for the 57th IETF - Vienna,
Austria



Please send me requests to make presentations within the L2TPEXT WG.  Be
sure to include all of the information below. Even if you have already made
a
request off line, please do me the favor of responding (privately, no
need to copy the list) to this email with the following items filled in.
I will provide a digest after receiving time slot requests.

Thanks.

- Mark

1) Name of presenter, including e-mail address
2) Title of presentation
3) Internet draft name, if applicable
4) Amount of time requested
_______________________________________________
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  Sun Jun  1 10:40: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 KAA13669
	for <l2tpext-archive@odin.ietf.org>; Sun, 1 Jun 2003 10:40:19 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h51EdtQ13922
	for l2tpext-archive@odin.ietf.org; Sun, 1 Jun 2003 10:39:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51EdtB13919
	for <l2tpext-web-archive@optimus.ietf.org>; Sun, 1 Jun 2003 10:39:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13635
	for <l2tpext-web-archive@ietf.org>; Sun, 1 Jun 2003 10:39:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MTyH-0007gr-00
	for l2tpext-web-archive@ietf.org; Sun, 01 Jun 2003 10:38:06 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19MTyG-0007gf-00
	for l2tpext-web-archive@ietf.org; Sun, 01 Jun 2003 10:38:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51EYGB10657;
	Sun, 1 Jun 2003 10:34:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51EVEB09263
	for <l2tpext@optimus.ietf.org>; Sun, 1 Jun 2003 10:31:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12884
	for <l2tpext@ietf.org>; Sun, 1 Jun 2003 10:31:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19MTpt-0007Td-00
	for l2tpext@ietf.org; Sun, 01 Jun 2003 10:29:25 -0400
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 19MTpr-0007TF-00
	for l2tpext@ietf.org; Sun, 01 Jun 2003 10:29:24 -0400
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Sun, 01 Jun 2003 17:32:11 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <KCY9SH7F>; Sun, 1 Jun 2003 17:26:42 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085F74@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>, l2tpext@ietf.org
Subject: RE: [L2tpext] Call for L2TPEXT Agenda Items for the 57th IETF - V
	ienna, Austria
Date: Sun, 1 Jun 2003 17:26:34 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
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>

Mark,
I would like to ask for a slot at the Vienna L2TPEXT Session.

Name of presenter: Sharon Galtzur sharon@axerra.com 
It is possible that it will be de-facto presented by 
Sasha Vainshtein (sasha@axerra.com)

Title of presentation: L2TP v3 Graceful Restart

Internet draft:
http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-00.txt

Amount of time: 10 minutes


Thanks,

Sharon Galtzur


-----Original Message-----
From: W. Mark Townsley [mailto:townsley@cisco.com]
Sent: Saturday, May 31, 2003 8:53 AM
To: l2tpext@ietf.org
Subject: [L2tpext] Call for L2TPEXT Agenda Items for the 57th IETF - Vienna,
Austria



Please send me requests to make presentations within the L2TPEXT WG.  Be
sure to include all of the information below. Even if you have already made
a
request off line, please do me the favor of responding (privately, no
need to copy the list) to this email with the following items filled in.
I will provide a digest after receiving time slot requests.

Thanks.

- Mark

1) Name of presenter, including e-mail address
2) Title of presentation
3) Internet draft name, if applicable
4) Amount of time requested
_______________________________________________
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 Jun  4 08:33:27 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 IAA14662
	for <l2tpext-archive@lists.ietf.org>; Wed, 4 Jun 2003 08:33:27 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54CQVB10589;
	Wed, 4 Jun 2003 08:26:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54BvoB08121
	for <l2tpext@optimus.ietf.org>; Wed, 4 Jun 2003 07:57:50 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12971;
	Wed, 4 Jun 2003 07:57:43 -0400 (EDT)
Message-Id: <200306041157.HAA12971@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: l2tpext@ietf.org, ppvpn@nortelnetworks.com, pwe3@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 04 Jun 2003 07:57:43 -0400
Subject: [L2tpext] I-D ACTION:draft-luo-l2tpext-l2vpn-signaling-02.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.


	Title		: L2VPN Signaling Using L2TPv3
	Author(s)	: W. Luo
	Filename	: draft-luo-l2tpext-l2vpn-signaling-02.txt
	Pages		: 20
	Date		: 2003-6-3
	
The Layer 2 Tunneling Protocol (L2TPv3) provides a standard method
for setting up and managing L2TP sessions to tunnel a variety of L2
protocols.  One of the reference models supported by L2TPv3 describes
the use of an L2TP session to cross-connect two Layer 2 circuits
attached to a pair of peering LACs.  A cross-connect is a basic form
of Layer 2 Virtual Private Networks (L2VPNs).  This document
describes mechanisms which utilize the building blocks that L2TP
provides to construct different types of L2VPNs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-luo-l2tpext-l2vpn-signaling-02.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-luo-l2tpext-l2vpn-signaling-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-luo-l2tpext-l2vpn-signaling-02.txt

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

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

--OtherAccess--

--NextPart--


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


From mailnull@www1.ietf.org  Wed Jun  4 08:34:25 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 IAA14779
	for <l2tpext-archive@odin.ietf.org>; Wed, 4 Jun 2003 08:34:24 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h54CXvk11047
	for l2tpext-archive@odin.ietf.org; Wed, 4 Jun 2003 08:33:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54CXvB11044
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 4 Jun 2003 08:33:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14718
	for <l2tpext-web-archive@ietf.org>; Wed, 4 Jun 2003 08:33:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXQz-0001XC-00
	for l2tpext-web-archive@ietf.org; Wed, 04 Jun 2003 08:32:05 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19NXQy-0001X8-00
	for l2tpext-web-archive@ietf.org; Wed, 04 Jun 2003 08:32:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54CQVB10589;
	Wed, 4 Jun 2003 08:26:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54BvoB08121
	for <l2tpext@optimus.ietf.org>; Wed, 4 Jun 2003 07:57:50 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12971;
	Wed, 4 Jun 2003 07:57:43 -0400 (EDT)
Message-Id: <200306041157.HAA12971@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: l2tpext@ietf.org, ppvpn@nortelnetworks.com, pwe3@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 04 Jun 2003 07:57:43 -0400
Subject: [L2tpext] I-D ACTION:draft-luo-l2tpext-l2vpn-signaling-02.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.


	Title		: L2VPN Signaling Using L2TPv3
	Author(s)	: W. Luo
	Filename	: draft-luo-l2tpext-l2vpn-signaling-02.txt
	Pages		: 20
	Date		: 2003-6-3
	
The Layer 2 Tunneling Protocol (L2TPv3) provides a standard method
for setting up and managing L2TP sessions to tunnel a variety of L2
protocols.  One of the reference models supported by L2TPv3 describes
the use of an L2TP session to cross-connect two Layer 2 circuits
attached to a pair of peering LACs.  A cross-connect is a basic form
of Layer 2 Virtual Private Networks (L2VPNs).  This document
describes mechanisms which utilize the building blocks that L2TP
provides to construct different types of L2VPNs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-luo-l2tpext-l2vpn-signaling-02.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-luo-l2tpext-l2vpn-signaling-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-luo-l2tpext-l2vpn-signaling-02.txt

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

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

--OtherAccess--

--NextPart--


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



From l2tpext-admin@ietf.org  Tue Jun 10 11:38:26 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 LAA05842
	for <l2tpext-archive@lists.ietf.org>; Tue, 10 Jun 2003 11:38:26 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFUtB31654;
	Tue, 10 Jun 2003 11:30:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFMmB31265
	for <l2tpext@optimus.ietf.org>; Tue, 10 Jun 2003 11:22:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05281
	for <l2tpext@ietf.org>; Tue, 10 Jun 2003 11:22:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PkvT-0007N3-00
	for l2tpext@ietf.org; Tue, 10 Jun 2003 11:20:43 -0400
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 19PkvS-0007Mt-00
	for l2tpext@ietf.org; Tue, 10 Jun 2003 11:20:43 -0400
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Tue, 10 Jun 2003 18:24:15 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <KCY9SQVM>; Tue, 10 Jun 2003 18:18:43 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085F79@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: l2tpext@ietf.org
Date: Tue, 10 Jun 2003 18:18:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
Subject: [L2tpext] Question regarding L2TP sub layer AVP
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 all,
 
I have a question regarding L2TP sub layer. 
 
In <draft-ietf-l2tpext-l2tp-base-07.txt>  the specific sub layer AVP has 2
possible values:
 
0 - There is no L2-Specific Sub layer present.
1 - The default L2-Specific Sub layer (defined in Section 4.6) is used.
 
My question is this:
 
What should this AVP contain for a service with a non-standard sub layer
(RTP for example)
There are 2 possibilities:
a. add a new value - 3,4 etc. that will represent the non-standard sub
layer.
b. send the AVP with 0. which means that from the L2TP machine there is no
sub 
   layer and it is up to me to indicate to the other side (maybe via other 
   private AVP) what kind of header I would like to receive if at all.

Thanks,
Sharon Galtzur
sharon@axerrra.com
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Tue Jun 10 11:39:09 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 LAA05927
	for <l2tpext-archive@odin.ietf.org>; Tue, 10 Jun 2003 11:39:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5AFcff00569
	for l2tpext-archive@odin.ietf.org; Tue, 10 Jun 2003 11:38:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFcfB00566
	for <l2tpext-web-archive@optimus.ietf.org>; Tue, 10 Jun 2003 11:38:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05880
	for <l2tpext-web-archive@ietf.org>; Tue, 10 Jun 2003 11:38:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PlAr-0007UZ-00
	for l2tpext-web-archive@ietf.org; Tue, 10 Jun 2003 11:36:37 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19PlAq-0007UV-00
	for l2tpext-web-archive@ietf.org; Tue, 10 Jun 2003 11:36:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFUtB31654;
	Tue, 10 Jun 2003 11:30:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AFMmB31265
	for <l2tpext@optimus.ietf.org>; Tue, 10 Jun 2003 11:22:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05281
	for <l2tpext@ietf.org>; Tue, 10 Jun 2003 11:22:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19PkvT-0007N3-00
	for l2tpext@ietf.org; Tue, 10 Jun 2003 11:20:43 -0400
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 19PkvS-0007Mt-00
	for l2tpext@ietf.org; Tue, 10 Jun 2003 11:20:43 -0400
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Tue, 10 Jun 2003 18:24:15 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <KCY9SQVM>; Tue, 10 Jun 2003 18:18:43 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085F79@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: l2tpext@ietf.org
Date: Tue, 10 Jun 2003 18:18:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
Subject: [L2tpext] Question regarding L2TP sub layer AVP
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 all,
 
I have a question regarding L2TP sub layer. 
 
In <draft-ietf-l2tpext-l2tp-base-07.txt>  the specific sub layer AVP has 2
possible values:
 
0 - There is no L2-Specific Sub layer present.
1 - The default L2-Specific Sub layer (defined in Section 4.6) is used.
 
My question is this:
 
What should this AVP contain for a service with a non-standard sub layer
(RTP for example)
There are 2 possibilities:
a. add a new value - 3,4 etc. that will represent the non-standard sub
layer.
b. send the AVP with 0. which means that from the L2TP machine there is no
sub 
   layer and it is up to me to indicate to the other side (maybe via other 
   private AVP) what kind of header I would like to receive if at all.

Thanks,
Sharon Galtzur
sharon@axerrra.com
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Jun 11 23:29:47 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 XAA13195
	for <l2tpext-archive@lists.ietf.org>; Wed, 11 Jun 2003 23:29:47 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C3STm31551;
	Wed, 11 Jun 2003 23:28:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C3Pem31483
	for <l2tpext@optimus.ietf.org>; Wed, 11 Jun 2003 23:25:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13148
	for <L2tpext@ietf.org>; Wed, 11 Jun 2003 23:25:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QIgX-0006EX-00
	for L2tpext@ietf.org; Wed, 11 Jun 2003 23:23:33 -0400
Received: from web41302.mail.yahoo.com ([66.218.93.51])
	by ietf-mx with smtp (Exim 4.12)
	id 19QIgW-0006EK-00
	for L2tpext@ietf.org; Wed, 11 Jun 2003 23:23:32 -0400
Message-ID: <20030612032508.21349.qmail@web41302.mail.yahoo.com>
Received: from [64.95.122.13] by web41302.mail.yahoo.com via HTTP; Wed, 11 Jun 2003 20:25:08 PDT
Date: Wed, 11 Jun 2003 20:25:08 -0700 (PDT)
From: Vipin Jain <vipinietf@yahoo.com>
To: kchen <kchen@seu.edu.cn>
Cc: l2tp ietflist <L2tpext@ietf.org>
In-Reply-To: <002701c33085$7896acb0$c90b77ca@kchen>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [L2tpext] Re: a question
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>

kchen,

I'd encourage your to send L2TP tunnel switching related questions to L2TP
list, because this is the right forum for such discussions. my response
inline..

--- kchen <kchen@seu.edu.cn> wrote:
> Hi,I have a question to ask you.
> [L2] <--- PPP ---> [LAC] <---L2TP --> [ TSA ] <--- PPTP---> [LNS]
> In such a example,the TSA should dencrypt the packet from LAC and encrypt it
> to LNS,is it?if this is true,I think the TSA is a bottleneck.
you are correct, TSA would be bottleneck specially if encryption and decription
is done in software;
In general, if one uses TSA that can't handle traffic (control as well as data)
from multiple LACs then there is some problem in the network delpoyment.

> [L2] <--- PPP ---> [LAC] <---L2TP --> [ TSA ] <--- L2TP---> [LNS]
> In this situation,the tunnel beside the TSA are both L2TP.The packet is
> forward to LNS directly.Is it true?
nope.. the packet needs to switch the session and tunnel so it can't be
forwarded directo to the LNS; It must be destined to TSA's tunnel IP address,
which could decide to tunnel the session or drop it depending on configured
policies.

thanks,
-- vipin

> Thank you fore you help.
> 


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Jun 11 23:30:35 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 XAA13218
	for <l2tpext-archive@odin.ietf.org>; Wed, 11 Jun 2003 23:30:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5C3U7w31653
	for l2tpext-archive@odin.ietf.org; Wed, 11 Jun 2003 23:30:07 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C3U7m31650
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 11 Jun 2003 23:30:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13213
	for <l2tpext-web-archive@ietf.org>; Wed, 11 Jun 2003 23:30:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QIkq-0006Fd-00
	for l2tpext-web-archive@ietf.org; Wed, 11 Jun 2003 23:28:00 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19QIkq-0006FZ-00
	for l2tpext-web-archive@ietf.org; Wed, 11 Jun 2003 23:28:00 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C3STm31551;
	Wed, 11 Jun 2003 23:28:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5C3Pem31483
	for <l2tpext@optimus.ietf.org>; Wed, 11 Jun 2003 23:25:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13148
	for <L2tpext@ietf.org>; Wed, 11 Jun 2003 23:25:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19QIgX-0006EX-00
	for L2tpext@ietf.org; Wed, 11 Jun 2003 23:23:33 -0400
Received: from web41302.mail.yahoo.com ([66.218.93.51])
	by ietf-mx with smtp (Exim 4.12)
	id 19QIgW-0006EK-00
	for L2tpext@ietf.org; Wed, 11 Jun 2003 23:23:32 -0400
Message-ID: <20030612032508.21349.qmail@web41302.mail.yahoo.com>
Received: from [64.95.122.13] by web41302.mail.yahoo.com via HTTP; Wed, 11 Jun 2003 20:25:08 PDT
Date: Wed, 11 Jun 2003 20:25:08 -0700 (PDT)
From: Vipin Jain <vipinietf@yahoo.com>
To: kchen <kchen@seu.edu.cn>
Cc: l2tp ietflist <L2tpext@ietf.org>
In-Reply-To: <002701c33085$7896acb0$c90b77ca@kchen>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [L2tpext] Re: a question
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>

kchen,

I'd encourage your to send L2TP tunnel switching related questions to L2TP
list, because this is the right forum for such discussions. my response
inline..

--- kchen <kchen@seu.edu.cn> wrote:
> Hi,I have a question to ask you.
> [L2] <--- PPP ---> [LAC] <---L2TP --> [ TSA ] <--- PPTP---> [LNS]
> In such a example,the TSA should dencrypt the packet from LAC and encrypt it
> to LNS,is it?if this is true,I think the TSA is a bottleneck.
you are correct, TSA would be bottleneck specially if encryption and decription
is done in software;
In general, if one uses TSA that can't handle traffic (control as well as data)
from multiple LACs then there is some problem in the network delpoyment.

> [L2] <--- PPP ---> [LAC] <---L2TP --> [ TSA ] <--- L2TP---> [LNS]
> In this situation,the tunnel beside the TSA are both L2TP.The packet is
> forward to LNS directly.Is it true?
nope.. the packet needs to switch the session and tunnel so it can't be
forwarded directo to the LNS; It must be destined to TSA's tunnel IP address,
which could decide to tunnel the session or drop it depending on configured
policies.

thanks,
-- vipin

> Thank you fore you help.
> 


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Mon Jun 16 17:00: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 RAA02281
	for <l2tpext-archive@lists.ietf.org>; Mon, 16 Jun 2003 17:00:38 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GK52a31325;
	Mon, 16 Jun 2003 16:05:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GK4am31284
	for <l2tpext@optimus.ietf.org>; Mon, 16 Jun 2003 16:04:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29383
	for <L2tpext@ietf.org>; Mon, 16 Jun 2003 16:04:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0BI-000601-00
	for L2tpext@ietf.org; Mon, 16 Jun 2003 16:02:20 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0BH-0005yF-00
	for L2tpext@ietf.org; Mon, 16 Jun 2003 16:02:19 -0400
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5GK42Ta028576
	for <L2tpext@ietf.org>; Mon, 16 Jun 2003 13:04:02 -0700 (PDT)
Received: from ponychuvectra (dhcp-128-107-166-52.cisco.com [128.107.166.52])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AEB73108;
	Mon, 16 Jun 2003 13:04:01 -0700 (PDT)
Message-ID: <009b01c33443$bb332410$34a66b80@ponychuvectra>
From: "Jiang Zhu" <jiangzhu@stanford.edu>
To: "l2tp ietflist" <L2tpext@ietf.org>
References: <20030612032508.21349.qmail@web41302.mail.yahoo.com>
Date: Mon, 16 Jun 2003 13:13:19 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [L2tpext] L2 Specific Sublayer AVP
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>

Hi, there,
Do we have IANA# for layer 2 specific sublayer AVP?
Thanks a lot.
-Jiang


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


From mailnull@www1.ietf.org  Mon Jun 16 17:01:39 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 RAA02399
	for <l2tpext-archive@odin.ietf.org>; Mon, 16 Jun 2003 17:01:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5GL1CP03306
	for l2tpext-archive@odin.ietf.org; Mon, 16 Jun 2003 17:01:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GL1Bm03303
	for <l2tpext-web-archive@optimus.ietf.org>; Mon, 16 Jun 2003 17:01:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02360
	for <l2tpext-web-archive@ietf.org>; Mon, 16 Jun 2003 17:01:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S142-0006n0-00
	for l2tpext-web-archive@ietf.org; Mon, 16 Jun 2003 16:58:54 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19S141-0006mu-00
	for l2tpext-web-archive@ietf.org; Mon, 16 Jun 2003 16:58:53 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GK52a31325;
	Mon, 16 Jun 2003 16:05:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GK4am31284
	for <l2tpext@optimus.ietf.org>; Mon, 16 Jun 2003 16:04:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29383
	for <L2tpext@ietf.org>; Mon, 16 Jun 2003 16:04:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0BI-000601-00
	for L2tpext@ietf.org; Mon, 16 Jun 2003 16:02:20 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19S0BH-0005yF-00
	for L2tpext@ietf.org; Mon, 16 Jun 2003 16:02:19 -0400
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h5GK42Ta028576
	for <L2tpext@ietf.org>; Mon, 16 Jun 2003 13:04:02 -0700 (PDT)
Received: from ponychuvectra (dhcp-128-107-166-52.cisco.com [128.107.166.52])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AEB73108;
	Mon, 16 Jun 2003 13:04:01 -0700 (PDT)
Message-ID: <009b01c33443$bb332410$34a66b80@ponychuvectra>
From: "Jiang Zhu" <jiangzhu@stanford.edu>
To: "l2tp ietflist" <L2tpext@ietf.org>
References: <20030612032508.21349.qmail@web41302.mail.yahoo.com>
Date: Mon, 16 Jun 2003 13:13:19 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [L2tpext] L2 Specific Sublayer AVP
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>

Hi, there,
Do we have IANA# for layer 2 specific sublayer AVP?
Thanks a lot.
-Jiang


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



From l2tpext-admin@ietf.org  Wed Jun 18 10:57:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10964
	for <l2tpext-archive@lists.ietf.org>; Wed, 18 Jun 2003 10:57:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdiG-0003De-V5; Wed, 18 Jun 2003 10:15:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SbVJ-0004p5-S9
	for l2tpext@optimus.ietf.org; Wed, 18 Jun 2003 07:53:29 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28218;
	Wed, 18 Jun 2003 07:53:28 -0400 (EDT)
Message-Id: <200306181153.HAA28218@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 18 Jun 2003 07:53:28 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-pwe3-fr-02.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		: Frame-Relay Pseudo-Wire Extensions for L2TP
	Author(s)	: W. Townsley et al.
	Filename	: draft-ietf-l2tpext-pwe3-fr-02.txt
	Pages		: 10
	Date		: 2003-6-17
	
The Layer 2 Tunneling Protocol [L2TPv3] defines an extensible
tunneling protocol suitable for Pseudowire Emulation Edge to Edge
(PWE3) applications. This document describes the specifics of how to
use the L2TP control plane for Frame-Relay Pseudo-Wires, including
PVC creation, deletion, and line status change notification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-pwe3-fr-02.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-pwe3-fr-02.txt".

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID:	<2003-6-17144553.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 Jun 18 11:02:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11147
	for <l2tpext-archive@lists.ietf.org>; Wed, 18 Jun 2003 11:02:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdiH-0003Dm-9h; Wed, 18 Jun 2003 10:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SbVO-0004pG-VR
	for l2tpext@optimus.ietf.org; Wed, 18 Jun 2003 07:53:34 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28247;
	Wed, 18 Jun 2003 07:53:33 -0400 (EDT)
Message-Id: <200306181153.HAA28247@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 18 Jun 2003 07:53:33 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-pwe3-hdlc-01.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		: HDLC Frames Over L2TPv3
	Author(s)	: W. Townsley
	Filename	: draft-ietf-l2tpext-pwe3-hdlc-01.txt
	Pages		: 7
	Date		: 2003-6-17
	
Simple HDLC frame transport over L2TPv3 is described in this
document. This mechanism may be used in the creation of pseudowires
to transport HDLC PDUs over an IP network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-pwe3-hdlc-01.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-pwe3-hdlc-01.txt".

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Wed Jun 18 11:29:28 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 LAA12623
	for <l2tpext-archive@odin.ietf.org>; Wed, 18 Jun 2003 11:29:27 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IFSxZ27906
	for l2tpext-archive@odin.ietf.org; Wed, 18 Jun 2003 11:28:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SeN5-0005jS-Bf
	for l2tpext-web-archive@optimus.ietf.org; Wed, 18 Jun 2003 10:57:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10950
	for <l2tpext-web-archive@ietf.org>; Wed, 18 Jun 2003 10:57:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SeKn-0005Qi-00
	for l2tpext-web-archive@ietf.org; Wed, 18 Jun 2003 10:54:50 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SeKn-0005Qe-00
	for l2tpext-web-archive@ietf.org; Wed, 18 Jun 2003 10:54:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdiG-0003De-V5; Wed, 18 Jun 2003 10:15:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SbVJ-0004p5-S9
	for l2tpext@optimus.ietf.org; Wed, 18 Jun 2003 07:53:29 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28218;
	Wed, 18 Jun 2003 07:53:28 -0400 (EDT)
Message-Id: <200306181153.HAA28218@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 18 Jun 2003 07:53:28 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-pwe3-fr-02.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		: Frame-Relay Pseudo-Wire Extensions for L2TP
	Author(s)	: W. Townsley et al.
	Filename	: draft-ietf-l2tpext-pwe3-fr-02.txt
	Pages		: 10
	Date		: 2003-6-17
	
The Layer 2 Tunneling Protocol [L2TPv3] defines an extensible
tunneling protocol suitable for Pseudowire Emulation Edge to Edge
(PWE3) applications. This document describes the specifics of how to
use the L2TP control plane for Frame-Relay Pseudo-Wires, including
PVC creation, deletion, and line status change notification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-pwe3-fr-02.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-pwe3-fr-02.txt".

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Wed Jun 18 11:31:50 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 LAA12690
	for <l2tpext-archive@odin.ietf.org>; Wed, 18 Jun 2003 11:31:50 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5IFVMl28128
	for l2tpext-archive@odin.ietf.org; Wed, 18 Jun 2003 11:31:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SeRe-0005rb-Bb
	for l2tpext-web-archive@optimus.ietf.org; Wed, 18 Jun 2003 11:01:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11127
	for <l2tpext-web-archive@ietf.org>; Wed, 18 Jun 2003 11:01:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19SePM-0005TG-00
	for l2tpext-web-archive@ietf.org; Wed, 18 Jun 2003 10:59:33 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19SePM-0005TD-00
	for l2tpext-web-archive@ietf.org; Wed, 18 Jun 2003 10:59:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SdiH-0003Dm-9h; Wed, 18 Jun 2003 10:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19SbVO-0004pG-VR
	for l2tpext@optimus.ietf.org; Wed, 18 Jun 2003 07:53:34 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28247;
	Wed, 18 Jun 2003 07:53:33 -0400 (EDT)
Message-Id: <200306181153.HAA28247@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 18 Jun 2003 07:53:33 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-pwe3-hdlc-01.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		: HDLC Frames Over L2TPv3
	Author(s)	: W. Townsley
	Filename	: draft-ietf-l2tpext-pwe3-hdlc-01.txt
	Pages		: 7
	Date		: 2003-6-17
	
Simple HDLC frame transport over L2TPv3 is described in this
document. This mechanism may be used in the creation of pseudowires
to transport HDLC PDUs over an IP network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-pwe3-hdlc-01.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-pwe3-hdlc-01.txt".

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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



From l2tpext-admin@ietf.org  Fri Jun 20 04:59:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22173
	for <l2tpext-archive@lists.ietf.org>; Fri, 20 Jun 2003 04:59:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19THjZ-00041Z-MJ; Fri, 20 Jun 2003 04:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19THj2-000418-79
	for l2tpext@optimus.ietf.org; Fri, 20 Jun 2003 04:58:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22161;
	Fri, 20 Jun 2003 04:58:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THgi-0000p3-00; Fri, 20 Jun 2003 04:56:04 -0400
Received: from cvis163.marconicomms.com ([128.87.251.113])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THgh-0000oz-00; Fri, 20 Jun 2003 04:56:03 -0400
Received: from cvis152.mail.marconicomms.com by cvis163.marconicomms.com with ESMTP
	(8.11.6+Sun/mcig-3) id h5K8vsE21461; Fri, 20 Jun 2003 09:57:54 +0100 (BST)
Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis153.mail.marconicomms.com
 (Content Technologies SMTPRS 4.3.10) with ESMTP id <T62f10ec59dc0a899e3304@cvis153.mail.marconicomms.com>;
 Fri, 20 Jun 2003 09:57:52 +0100
To: l2tpext@ietf.org, l2tpext-admin@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
From: "Jane Humphrey" <Jane.Humphrey@marconi.com>
Message-ID: <OF70B76B25.6A7A6A60-ON80256D4B.002F8CC7-80256D4B.0031514A@uk.marconicomms.com>
Date: Fri, 20 Jun 2003 09:57:49 +0100
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(Release 5.0.12  |February 13, 2003) at
 20/06/2003 09:57:35,
	Serialize complete at 20/06/2003 09:57:35
Content-Type: multipart/alternative; boundary="=_alternative 00311A4780256D4B_="
Subject: [L2tpext] Status of RFC 2661
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 multipart message in MIME format.
--=_alternative 00311A4780256D4B_=
Content-Type: text/plain; charset="us-ascii"

Hello,

First my apologies if this issue has previously been discussed but I do 
not attend the L2TP meetings and my monitoring of the L2TP email exploder 
over the past 12 months I cannot recall this being mentioned.

Version 3 of L2TP is nearing completion, this new version is not a direct 
replacement of RFC 2661but it reformats the material from 2661with some 
additional clarifications and a few new features.  Once Version 3 is 
completed what will happen to RFC 2661, will it be deleted as an active 
RFC?

Regards

Jane Humphrey
Marconi Communications
--=_alternative 00311A4780256D4B_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hello,</font>
<br>
<br><font size=2 face="sans-serif">First my apologies if this issue has previously been discussed but I do not attend the L2TP meetings and my monitoring of the L2TP email exploder over the past 12 months I cannot recall this being mentioned.</font>
<br>
<br><font size=2 face="sans-serif">Version 3 of L2TP is nearing completion, this new version is not a direct replacement of RFC 2661but it reformats the material from 2661with some additional clarifications and a few new features. &nbsp;Once Version 3 is completed what will happen to RFC 2661, will it be deleted as an active RFC?</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Jane Humphrey</font>
<br><font size=2 face="sans-serif">Marconi Communications</font>
--=_alternative 00311A4780256D4B_=--

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


From exim@www1.ietf.org  Fri Jun 20 04:59:37 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 EAA22189
	for <l2tpext-archive@odin.ietf.org>; Fri, 20 Jun 2003 04:59:36 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5K8x9515525
	for l2tpext-archive@odin.ietf.org; Fri, 20 Jun 2003 04:59:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19THjh-00042K-Aw
	for l2tpext-web-archive@optimus.ietf.org; Fri, 20 Jun 2003 04:59:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22167
	for <l2tpext-web-archive@ietf.org>; Fri, 20 Jun 2003 04:59:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THhN-0000pG-00
	for l2tpext-web-archive@ietf.org; Fri, 20 Jun 2003 04:56:45 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19THhM-0000pC-00
	for l2tpext-web-archive@ietf.org; Fri, 20 Jun 2003 04:56:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19THjZ-00041Z-MJ; Fri, 20 Jun 2003 04:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19THj2-000418-79
	for l2tpext@optimus.ietf.org; Fri, 20 Jun 2003 04:58:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22161;
	Fri, 20 Jun 2003 04:58:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THgi-0000p3-00; Fri, 20 Jun 2003 04:56:04 -0400
Received: from cvis163.marconicomms.com ([128.87.251.113])
	by ietf-mx with esmtp (Exim 4.12)
	id 19THgh-0000oz-00; Fri, 20 Jun 2003 04:56:03 -0400
Received: from cvis152.mail.marconicomms.com by cvis163.marconicomms.com with ESMTP
	(8.11.6+Sun/mcig-3) id h5K8vsE21461; Fri, 20 Jun 2003 09:57:54 +0100 (BST)
Received: from cvdgwy01.uk.marconicomms.com (unverified) by cvis153.mail.marconicomms.com
 (Content Technologies SMTPRS 4.3.10) with ESMTP id <T62f10ec59dc0a899e3304@cvis153.mail.marconicomms.com>;
 Fri, 20 Jun 2003 09:57:52 +0100
To: l2tpext@ietf.org, l2tpext-admin@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
From: "Jane Humphrey" <Jane.Humphrey@marconi.com>
Message-ID: <OF70B76B25.6A7A6A60-ON80256D4B.002F8CC7-80256D4B.0031514A@uk.marconicomms.com>
Date: Fri, 20 Jun 2003 09:57:49 +0100
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(Release 5.0.12  |February 13, 2003) at
 20/06/2003 09:57:35,
	Serialize complete at 20/06/2003 09:57:35
Content-Type: multipart/alternative; boundary="=_alternative 00311A4780256D4B_="
Subject: [L2tpext] Status of RFC 2661
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 multipart message in MIME format.
--=_alternative 00311A4780256D4B_=
Content-Type: text/plain; charset="us-ascii"

Hello,

First my apologies if this issue has previously been discussed but I do 
not attend the L2TP meetings and my monitoring of the L2TP email exploder 
over the past 12 months I cannot recall this being mentioned.

Version 3 of L2TP is nearing completion, this new version is not a direct 
replacement of RFC 2661but it reformats the material from 2661with some 
additional clarifications and a few new features.  Once Version 3 is 
completed what will happen to RFC 2661, will it be deleted as an active 
RFC?

Regards

Jane Humphrey
Marconi Communications
--=_alternative 00311A4780256D4B_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hello,</font>
<br>
<br><font size=2 face="sans-serif">First my apologies if this issue has previously been discussed but I do not attend the L2TP meetings and my monitoring of the L2TP email exploder over the past 12 months I cannot recall this being mentioned.</font>
<br>
<br><font size=2 face="sans-serif">Version 3 of L2TP is nearing completion, this new version is not a direct replacement of RFC 2661but it reformats the material from 2661with some additional clarifications and a few new features. &nbsp;Once Version 3 is completed what will happen to RFC 2661, will it be deleted as an active RFC?</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Jane Humphrey</font>
<br><font size=2 face="sans-serif">Marconi Communications</font>
--=_alternative 00311A4780256D4B_=--

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



From l2tpext-admin@ietf.org  Mon Jun 23 18:54:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14318
	for <l2tpext-archive@lists.ietf.org>; Mon, 23 Jun 2003 18:54:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UaCG-0007rq-Kx; Mon, 23 Jun 2003 18:54:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UaBL-0007q6-0b
	for l2tpext@optimus.ietf.org; Mon, 23 Jun 2003 18:53:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14271
	for <l2tpext@ietf.org>; Mon, 23 Jun 2003 18:52:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UaBH-0006Lf-00
	for l2tpext@ietf.org; Mon, 23 Jun 2003 18:52:59 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UaB7-0006LL-00
	for l2tpext@ietf.org; Mon, 23 Jun 2003 18:52:49 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 23 Jun 2003 15:55:40 -0800
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h5NMqUgE029367;
	Mon, 23 Jun 2003 15:52:30 -0700 (PDT)
Received: from gwzw2k (sjc-vpn4-291.cisco.com [10.21.81.35]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id PAA13064; Mon, 23 Jun 2003 15:52:29 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "'Jane Humphrey'" <Jane.Humphrey@marconi.com>, <l2tpext@ietf.org>
Subject: RE: [L2tpext] Status of RFC 2661
Date: Mon, 23 Jun 2003 15:51:54 -0700
Organization: Cisco Systems
Message-ID: <022d01c339da$1cdc28b0$6f904104@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <OF70B76B25.6A7A6A60-ON80256D4B.002F8CC7-80256D4B.0031514A@uk.marconicomms.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
Content-Transfer-Encoding: 7bit
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

l2tpext-admin@ietf.org <mailto:l2tpext-admin@ietf.org> writes:

> Hello,
> 
> First my apologies if this issue has previously been discussed but I
> do not attend the L2TP meetings and my monitoring of the L2TP email
> exploder over the past 12 months I cannot recall this being
> mentioned.   
> 
> Version 3 of L2TP is nearing completion, this new version is not a
> direct replacement of RFC 2661but it reformats the material from
> 2661with some additional clarifications and a few new features.  

and lots of deletions...

> Once
> Version 3 is completed what will happen to RFC 2661, will it be
> deleted as an active RFC? 

RFCs are never deleted.  I agree that there needs to be some mention in
the I-D of the intention of the document, however (i.e., "Obsoletes: RFC
2661").
   
> 
> Regards
> 
> Jane Humphrey
> Marconi Communications

Hope this helps,

~gwz

"They that can give up essential liberty to obtain a little temporary
safety deserve neither..." 
-- Benjamin Franklin, 1759

"It is forbidden to kill; therefore all murderers are punished unless
they kill in large numbers and to the sound of trumpets." 
-- Voltaire


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


From exim@www1.ietf.org  Mon Jun 23 18:54:40 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 SAA14337
	for <l2tpext-archive@odin.ietf.org>; Mon, 23 Jun 2003 18:54:40 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5NMsE230294
	for l2tpext-archive@odin.ietf.org; Mon, 23 Jun 2003 18:54:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UaCU-0007sX-Sz
	for l2tpext-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 18:54:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14314
	for <l2tpext-web-archive@ietf.org>; Mon, 23 Jun 2003 18:54:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UaCR-0006MB-00
	for l2tpext-web-archive@ietf.org; Mon, 23 Jun 2003 18:54:11 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UaCM-0006M6-00
	for l2tpext-web-archive@ietf.org; Mon, 23 Jun 2003 18:54:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UaCG-0007rq-Kx; Mon, 23 Jun 2003 18:54:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19UaBL-0007q6-0b
	for l2tpext@optimus.ietf.org; Mon, 23 Jun 2003 18:53:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14271
	for <l2tpext@ietf.org>; Mon, 23 Jun 2003 18:52:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19UaBH-0006Lf-00
	for l2tpext@ietf.org; Mon, 23 Jun 2003 18:52:59 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19UaB7-0006LL-00
	for l2tpext@ietf.org; Mon, 23 Jun 2003 18:52:49 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 23 Jun 2003 15:55:40 -0800
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h5NMqUgE029367;
	Mon, 23 Jun 2003 15:52:30 -0700 (PDT)
Received: from gwzw2k (sjc-vpn4-291.cisco.com [10.21.81.35]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id PAA13064; Mon, 23 Jun 2003 15:52:29 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "'Jane Humphrey'" <Jane.Humphrey@marconi.com>, <l2tpext@ietf.org>
Subject: RE: [L2tpext] Status of RFC 2661
Date: Mon, 23 Jun 2003 15:51:54 -0700
Organization: Cisco Systems
Message-ID: <022d01c339da$1cdc28b0$6f904104@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <OF70B76B25.6A7A6A60-ON80256D4B.002F8CC7-80256D4B.0031514A@uk.marconicomms.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
Content-Transfer-Encoding: 7bit
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

l2tpext-admin@ietf.org <mailto:l2tpext-admin@ietf.org> writes:

> Hello,
> 
> First my apologies if this issue has previously been discussed but I
> do not attend the L2TP meetings and my monitoring of the L2TP email
> exploder over the past 12 months I cannot recall this being
> mentioned.   
> 
> Version 3 of L2TP is nearing completion, this new version is not a
> direct replacement of RFC 2661but it reformats the material from
> 2661with some additional clarifications and a few new features.  

and lots of deletions...

> Once
> Version 3 is completed what will happen to RFC 2661, will it be
> deleted as an active RFC? 

RFCs are never deleted.  I agree that there needs to be some mention in
the I-D of the intention of the document, however (i.e., "Obsoletes: RFC
2661").
   
> 
> Regards
> 
> Jane Humphrey
> Marconi Communications

Hope this helps,

~gwz

"They that can give up essential liberty to obtain a little temporary
safety deserve neither..." 
-- Benjamin Franklin, 1759

"It is forbidden to kill; therefore all murderers are punished unless
they kill in large numbers and to the sound of trumpets." 
-- Voltaire


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



