From mailman-bounces@ietf.org  Thu Jul  1 07:31:38 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16188
	for <l2tpext-archive@lists.ietf.org>; Thu, 1 Jul 2004 07:31:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bfxk3-0005MV-P9
	for l2tpext-archive@lists.ietf.org; Thu, 01 Jul 2004 05:20:27 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: l2tpext-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.17279.1088672710.3306.mailman@lists.ietf.org>
Date: Thu, 01 Jul 2004 05:05:10 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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, mailman-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:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

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

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@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-bounces@ietf.org  Fri Jul  2 08:54:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02696
	for <l2tpext-archive@lists.ietf.org>; Fri, 2 Jul 2004 08:54:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgNPL-0004zY-OL; Fri, 02 Jul 2004 08:44:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BY8qL-0006h1-NC; Wed, 09 Jun 2004 15:34:37 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13106;
	Wed, 9 Jun 2004 15:34:35 -0400 (EDT)
Message-Id: <200406091934.PAA13106@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 09 Jun 2004 15:34:35 -0400
X-Mailman-Approved-At: Fri, 02 Jul 2004 08:44:45 -0400
Cc: l2tpext@ietf.org
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-14.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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>
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org

--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)
	Author(s)	: J. Lau, et al.
	Filename	: draft-ietf-l2tpext-l2tp-base-14.txt
	Pages		: 92
	Date		: 2004-6-9
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the base control protocol and
encapsulation for tunneling multiple layer 2 connections between two
IP connected nodes. Additional documents detail the specifics for
each link-type being emulated.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-14.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-14.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: <2004-6-9152933.I-D@ietf.org>

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From l2tpext-bounces@ietf.org  Wed Jul 21 06:42:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06074
	for <l2tpext-archive@lists.ietf.org>; Wed, 21 Jul 2004 06:42:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnEWd-0006CI-AU; Wed, 21 Jul 2004 06:40:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnEW4-0005d3-Sx
	for l2tpext@megatron.ietf.org; Wed, 21 Jul 2004 06:40:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05820
	for <l2tpext@ietf.org>; Wed, 21 Jul 2004 06:40:02 -0400 (EDT)
Received: from mta1.huawei.com ([61.144.161.40] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnEWN-0000Kx-St
	for l2tpext@ietf.org; Wed, 21 Jul 2004 06:40:25 -0400
Received: from kalyana (huawei.com [172.17.1.62])
	by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep
	8 2003)) with ESMTPA id <0I17005RV6VS06@mta0.huawei.com> for
	l2tpext@ietf.org; Wed, 21 Jul 2004 18:38:17 +0800 (CST)
Date: Wed, 21 Jul 2004 16:03:42 +0530
From: kalyana <kalyana@huawei.com>
To: townsley@cisco.com
Message-id: <002501c46f0e$322446c0$8104120a@kalyana>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: l2tpext@ietf.org
Subject: [L2tpext] Clarification for TBD values
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1647433594=="
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1647433594==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_NTNtxIU2U45haK1R6dFsUQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_NTNtxIU2U45haK1R6dFsUQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

 Hi Mark,

In most of L2TPv3 drafts(Layer Two Tunneling Protocol V3, Ethernet Frames over L2TPv3,  HDLC Frames over L2TPv3  and Frame-Relay over L2TPv3, )many  
AVPs ( For IANA Considerations) are mentioned as TBD. What is the current staus of these TBD values ?
Without these TBD values finalised, I feel there will be interoperabilty problem between different vendor routers.

Regards,
Kalyan

--Boundary_(ID_NTNtxIU2U45haK1R6dFsUQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>&nbsp;<FONT face=Arial size=2>Hi Mark,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>In most of L2TPv3 drafts(Layer Two Tunneling 
Protocol V3, Ethernet Frames over L2TPv3,&nbsp; HDLC Frames over L2TPv3&nbsp; 
and Frame-Relay over L2TPv3, )many &nbsp;<BR>AVPs ( For IANA Considerations) are 
mentioned as TBD. What is the current staus of these TBD values ?</FONT></DIV>
<DIV><FONT face=Arial size=2>Without these TBD values finalised, I feel there 
will be interoperabilty problem between different vendor routers.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Regards,<BR>Kalyan</FONT></DIV></BODY></HTML>

--Boundary_(ID_NTNtxIU2U45haK1R6dFsUQ)--


--===============1647433594==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1647433594==--



From l2tpext-bounces@ietf.org  Mon Jul 26 19:11:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19328
	for <l2tpext-archive@lists.ietf.org>; Mon, 26 Jul 2004 19:11:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BpEZA-0003Ay-CH; Mon, 26 Jul 2004 19:07:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BpES6-0000w3-Aw
	for l2tpext@megatron.ietf.org; Mon, 26 Jul 2004 19:00:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18705
	for <l2tpext@ietf.org>; Mon, 26 Jul 2004 19:00:11 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpETW-00025F-Bo
	for l2tpext@ietf.org; Mon, 26 Jul 2004 19:01:46 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 26 Jul 2004 19:05:33 -0400
X-BrightmailFiltered: true
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6QMxVP9014628; 
	Mon, 26 Jul 2004 18:59:32 -0400 (EDT)
Received: from [128.107.176.90] ([128.107.176.90])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id BAV59606;
	Mon, 26 Jul 2004 15:59:29 -0700 (PDT)
Message-ID: <41058D21.6020308@cisco.com>
Date: Mon, 26 Jul 2004 18:00:49 -0500
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: kalyana <kalyana@huawei.com>
References: <002501c46f0e$322446c0$8104120a@kalyana>
In-Reply-To: <002501c46f0e$322446c0$8104120a@kalyana>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: iana@iana.org, l2tpext@ietf.org
Subject: [L2tpext] Re: Clarification for TBD values
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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>
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org
Content-Transfer-Encoding: 7bit


Yes, we have already experienced some problems.

For draft-ietf-l2tpext-l2tp-base-14.txt, I am hoping that IANA will assign these 
values very soon. The draft has been approved for publication, and I have 
already requested that the number assignment be expedited.

Thanks,

- Mark

kalyana wrote:

>  Hi Mark,
>  
> In most of L2TPv3 drafts(Layer Two Tunneling Protocol V3, Ethernet 
> Frames over L2TPv3,  HDLC Frames over L2TPv3  and Frame-Relay over 
> L2TPv3, )many  
> AVPs ( For IANA Considerations) are mentioned as TBD. What is the 
> current staus of these TBD values ?
> Without these TBD values finalised, I feel there will be interoperabilty 
> problem between different vendor routers.
>  
> Regards,
> Kalyan

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


