From mailman-admin@ietf.org  Fri Aug  1 09:32:09 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 JAA14455
	for <l2tpext-archive@lists.ietf.org>; Fri, 1 Aug 2003 09:19:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19iZXw-0002OY-Vj
	for l2tpext-archive@lists.ietf.org; Fri, 01 Aug 2003 09:02:12 -0400
Date: Fri, 01 Aug 2003 09:02:12 -0400
Message-ID: <20030801130212.29120.98011.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: l2tpext-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

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

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

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

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


                              Note Well

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

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

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

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


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

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

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


From l2tpext-admin@ietf.org  Tue Aug  5 14:28:33 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 OAA21541
	for <l2tpext-archive@lists.ietf.org>; Tue, 5 Aug 2003 14:28:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6XQ-0002AB-4N; Tue, 05 Aug 2003 14:28:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6Wa-000247-2U
	for l2tpext@optimus.ietf.org; Tue, 05 Aug 2003 14:27:08 -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 OAA21476
	for <l2tpext@ietf.org>; Tue, 5 Aug 2003 14:27:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6WX-0004WQ-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 14:27:05 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6WW-0004WM-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 14:27:04 -0400
Received: from zbl6c012.us.nortel.com (zbl6c012.us.nortel.com [132.245.205.62])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h75IQWR17178
	for <l2tpext@ietf.org>; Tue, 5 Aug 2003 14:26:32 -0400 (EDT)
Received: by zbl6c012.corpeast.baynetworks.com with Internet Mail Service (5.5.2653.19)
	id <3ZF0QCSQ>; Tue, 5 Aug 2003 14:26:32 -0400
Message-ID: <8B888AAAAB0FD31189590008C79184431431C0A9@zbl6c002.corpeast.baynetworks.com>
From: "Puneet Sood" <psood@nortelnetworks.com>
To: "'l2tpext@ietf.org'" <l2tpext@ietf.org>
Date: Tue, 5 Aug 2003 14:26:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C35B7F.17CECC4E"
Subject: [L2tpext] Comments on draft-ietf-l2tpext-failover-01
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C35B7F.17CECC4E
Content-Type: text/plain

Hello,

I read the draft recently and had the following questions/comments on it.

I have the November 2002 revision of the draft. Is there a new revision of
the draft?

Comments:

1. Section 4.5 "Failover Session State AVP".
The FSS AVP has one session per AVP. Wouldn't it be more efficient to allow
multiple sessions per AVP? This would be more efficient in terms of the
message size and also the computation required to optionally hide the AVP.
Putting multiple sessions in a single AVP would not preclude sending
multiple FSQ or FSR messages.

2. Creating new sessions in a recovered tunnel.
After a peer fails, it starts recovery by creating a new tunnel and adding
the old tunnel ID AVP to the SCCRQ message. Once the tunnel is up, FSQ and
FSR messages can be exchanged between the peers to synchronize session state
for pre-existing sessions. There is no specific point at which the session
synchronization is known to be complete. My question is: at what point can
new sessions be created on this tunnel? If a new session is created before
session state is synchronized, one end could attempt to create a session
with a session id that is unused on its end but is in use for a session at
the peer. This would cause the peer to fail the session creation request it
receives. By itself this is not a big problem but it would be nice if some
mechanism exists to avoid this problem. If adding a mechanism for this is
not possible some text should be added to the document explaining this
problem.

3. When the two peers of a tunnel are both failover capable and one of the
peers goes down, how long should the other peer save the state for the
tunnel for a possible failover recovery?
It could happen that the peer died and is not coming back for a long long
time. Should the tunnel be deleted as usual when the L2TP tunnel keepalive
mechanism detects the tunnel is down?

4. Old Tunnel ID and Old Local Tunnel ID AVPs.
Both these AVPs are sent in both SCCRQ and SCCRP messages. Sending them in
the SCCRQ should be sufficient. Is there any use of sending them in the
SCCRP also?

5. Section 4.3 Old Tunnel ID AVP.
The packet format is missing the AVP value "old tunnel id".

Thanks,
Puneet

------_=_NextPart_001_01C35B7F.17CECC4E
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>Comments on draft-ietf-l2tpext-failover-01</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2>I read the draft recently and had the following =
questions/comments on it.</FONT>
</P>

<P><FONT SIZE=3D2>I have the November 2002 revision of the draft. Is =
there a new revision of the draft?</FONT>
</P>

<P><FONT SIZE=3D2>Comments:</FONT>
</P>

<P><FONT SIZE=3D2>1. Section 4.5 &quot;Failover Session State =
AVP&quot;.</FONT>
<BR><FONT SIZE=3D2>The FSS AVP has one session per AVP. Wouldn't it be =
more efficient to allow multiple sessions per AVP? This would be more =
efficient in terms of the message size and also the computation =
required to optionally hide the AVP. Putting multiple sessions in a =
single AVP would not preclude sending multiple FSQ or FSR =
messages.</FONT></P>

<P><FONT SIZE=3D2>2. Creating new sessions in a recovered =
tunnel.</FONT>
<BR><FONT SIZE=3D2>After a peer fails, it starts recovery by creating a =
new tunnel and adding the old tunnel ID AVP to the SCCRQ message. Once =
the tunnel is up, FSQ and FSR messages can be exchanged between the =
peers to synchronize session state for pre-existing sessions. There is =
no specific point at which the session synchronization is known to be =
complete. My question is: at what point can new sessions be created on =
this tunnel? If a new session is created before session state is =
synchronized, one end could attempt to create a session with a session =
id that is unused on its end but is in use for a session at the peer. =
This would cause the peer to fail the session creation request it =
receives. By itself this is not a big problem but it would be nice if =
some mechanism exists to avoid this problem. If adding a mechanism for =
this is not possible some text should be added to the document =
explaining this problem.</FONT></P>

<P><FONT SIZE=3D2>3. When the two peers of a tunnel are both failover =
capable and one of the peers goes down, how long should the other peer =
save the state for the tunnel for a possible failover =
recovery?</FONT></P>

<P><FONT SIZE=3D2>It could happen that the peer died and is not coming =
back for a long long time. Should the tunnel be deleted as usual when =
the L2TP tunnel keepalive mechanism detects the tunnel is =
down?</FONT></P>

<P><FONT SIZE=3D2>4. Old Tunnel ID and Old Local Tunnel ID AVPs.</FONT>
<BR><FONT SIZE=3D2>Both these AVPs are sent in both SCCRQ and SCCRP =
messages. Sending them in the SCCRQ should be sufficient. Is there any =
use of sending them in the SCCRP also?</FONT></P>

<P><FONT SIZE=3D2>5. Section 4.3 Old Tunnel ID AVP.</FONT>
<BR><FONT SIZE=3D2>The packet format is missing the AVP value &quot;old =
tunnel id&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Puneet</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C35B7F.17CECC4E--

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


From exim@www1.ietf.org  Tue Aug  5 14:29:03 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 OAA21585
	for <l2tpext-archive@odin.ietf.org>; Tue, 5 Aug 2003 14:29:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6Y2-0002EJ-Ao
	for l2tpext-archive@odin.ietf.org; Tue, 05 Aug 2003 14:28:38 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75IScnT008565
	for l2tpext-archive@odin.ietf.org; Tue, 5 Aug 2003 14:28:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6Y2-0002E4-5l
	for l2tpext-web-archive@optimus.ietf.org; Tue, 05 Aug 2003 14:28:38 -0400
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 OAA21542
	for <l2tpext-web-archive@ietf.org>; Tue, 5 Aug 2003 14:28:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6XQ-0002AB-4N; Tue, 05 Aug 2003 14:28:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19k6Wa-000247-2U
	for l2tpext@optimus.ietf.org; Tue, 05 Aug 2003 14:27:08 -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 OAA21476
	for <l2tpext@ietf.org>; Tue, 5 Aug 2003 14:27:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6WX-0004WQ-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 14:27:05 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 19k6WW-0004WM-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 14:27:04 -0400
Received: from zbl6c012.us.nortel.com (zbl6c012.us.nortel.com [132.245.205.62])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h75IQWR17178
	for <l2tpext@ietf.org>; Tue, 5 Aug 2003 14:26:32 -0400 (EDT)
Received: by zbl6c012.corpeast.baynetworks.com with Internet Mail Service (5.5.2653.19)
	id <3ZF0QCSQ>; Tue, 5 Aug 2003 14:26:32 -0400
Message-ID: <8B888AAAAB0FD31189590008C79184431431C0A9@zbl6c002.corpeast.baynetworks.com>
From: "Puneet Sood" <psood@nortelnetworks.com>
To: "'l2tpext@ietf.org'" <l2tpext@ietf.org>
Date: Tue, 5 Aug 2003 14:26:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C35B7F.17CECC4E"
Subject: [L2tpext] Comments on draft-ietf-l2tpext-failover-01
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C35B7F.17CECC4E
Content-Type: text/plain

Hello,

I read the draft recently and had the following questions/comments on it.

I have the November 2002 revision of the draft. Is there a new revision of
the draft?

Comments:

1. Section 4.5 "Failover Session State AVP".
The FSS AVP has one session per AVP. Wouldn't it be more efficient to allow
multiple sessions per AVP? This would be more efficient in terms of the
message size and also the computation required to optionally hide the AVP.
Putting multiple sessions in a single AVP would not preclude sending
multiple FSQ or FSR messages.

2. Creating new sessions in a recovered tunnel.
After a peer fails, it starts recovery by creating a new tunnel and adding
the old tunnel ID AVP to the SCCRQ message. Once the tunnel is up, FSQ and
FSR messages can be exchanged between the peers to synchronize session state
for pre-existing sessions. There is no specific point at which the session
synchronization is known to be complete. My question is: at what point can
new sessions be created on this tunnel? If a new session is created before
session state is synchronized, one end could attempt to create a session
with a session id that is unused on its end but is in use for a session at
the peer. This would cause the peer to fail the session creation request it
receives. By itself this is not a big problem but it would be nice if some
mechanism exists to avoid this problem. If adding a mechanism for this is
not possible some text should be added to the document explaining this
problem.

3. When the two peers of a tunnel are both failover capable and one of the
peers goes down, how long should the other peer save the state for the
tunnel for a possible failover recovery?
It could happen that the peer died and is not coming back for a long long
time. Should the tunnel be deleted as usual when the L2TP tunnel keepalive
mechanism detects the tunnel is down?

4. Old Tunnel ID and Old Local Tunnel ID AVPs.
Both these AVPs are sent in both SCCRQ and SCCRP messages. Sending them in
the SCCRQ should be sufficient. Is there any use of sending them in the
SCCRP also?

5. Section 4.3 Old Tunnel ID AVP.
The packet format is missing the AVP value "old tunnel id".

Thanks,
Puneet

------_=_NextPart_001_01C35B7F.17CECC4E
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>Comments on draft-ietf-l2tpext-failover-01</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2>I read the draft recently and had the following =
questions/comments on it.</FONT>
</P>

<P><FONT SIZE=3D2>I have the November 2002 revision of the draft. Is =
there a new revision of the draft?</FONT>
</P>

<P><FONT SIZE=3D2>Comments:</FONT>
</P>

<P><FONT SIZE=3D2>1. Section 4.5 &quot;Failover Session State =
AVP&quot;.</FONT>
<BR><FONT SIZE=3D2>The FSS AVP has one session per AVP. Wouldn't it be =
more efficient to allow multiple sessions per AVP? This would be more =
efficient in terms of the message size and also the computation =
required to optionally hide the AVP. Putting multiple sessions in a =
single AVP would not preclude sending multiple FSQ or FSR =
messages.</FONT></P>

<P><FONT SIZE=3D2>2. Creating new sessions in a recovered =
tunnel.</FONT>
<BR><FONT SIZE=3D2>After a peer fails, it starts recovery by creating a =
new tunnel and adding the old tunnel ID AVP to the SCCRQ message. Once =
the tunnel is up, FSQ and FSR messages can be exchanged between the =
peers to synchronize session state for pre-existing sessions. There is =
no specific point at which the session synchronization is known to be =
complete. My question is: at what point can new sessions be created on =
this tunnel? If a new session is created before session state is =
synchronized, one end could attempt to create a session with a session =
id that is unused on its end but is in use for a session at the peer. =
This would cause the peer to fail the session creation request it =
receives. By itself this is not a big problem but it would be nice if =
some mechanism exists to avoid this problem. If adding a mechanism for =
this is not possible some text should be added to the document =
explaining this problem.</FONT></P>

<P><FONT SIZE=3D2>3. When the two peers of a tunnel are both failover =
capable and one of the peers goes down, how long should the other peer =
save the state for the tunnel for a possible failover =
recovery?</FONT></P>

<P><FONT SIZE=3D2>It could happen that the peer died and is not coming =
back for a long long time. Should the tunnel be deleted as usual when =
the L2TP tunnel keepalive mechanism detects the tunnel is =
down?</FONT></P>

<P><FONT SIZE=3D2>4. Old Tunnel ID and Old Local Tunnel ID AVPs.</FONT>
<BR><FONT SIZE=3D2>Both these AVPs are sent in both SCCRQ and SCCRP =
messages. Sending them in the SCCRQ should be sufficient. Is there any =
use of sending them in the SCCRP also?</FONT></P>

<P><FONT SIZE=3D2>5. Section 4.3 Old Tunnel ID AVP.</FONT>
<BR><FONT SIZE=3D2>The packet format is missing the AVP value &quot;old =
tunnel id&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Puneet</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C35B7F.17CECC4E--

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



From l2tpext-admin@ietf.org  Tue Aug  5 19:18: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 TAA02769
	for <l2tpext-archive@lists.ietf.org>; Tue, 5 Aug 2003 19:18: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 19kB45-0004do-9f; Tue, 05 Aug 2003 19:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kB3Z-0004cC-0i
	for l2tpext@optimus.ietf.org; Tue, 05 Aug 2003 19:17:29 -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 TAA02724
	for <l2tpext@ietf.org>; Tue, 5 Aug 2003 19:17:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kB3X-0006be-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 19:17:27 -0400
Received: from web41312.mail.yahoo.com ([66.218.93.61])
	by ietf-mx with smtp (Exim 4.12)
	id 19kB3W-0006b5-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 19:17:26 -0400
Message-ID: <20030805231655.35954.qmail@web41312.mail.yahoo.com>
Received: from [66.17.149.13] by web41312.mail.yahoo.com via HTTP; Tue, 05 Aug 2003 16:16:55 PDT
Date: Tue, 5 Aug 2003 16:16:55 -0700 (PDT)
From: Vipin Jain <vipinietf@yahoo.com>
Subject: Re: [L2tpext] Comments on draft-ietf-l2tpext-failover-01
To: Puneet Sood <psood@nortelnetworks.com>,
        "'l2tpext@ietf.org'" <l2tpext@ietf.org>
Cc: vipin@riverstonenet.com
In-Reply-To: <8B888AAAAB0FD31189590008C79184431431C0A9@zbl6c002.corpeast.baynetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>


thanks for your comments. my comments inline..

> I have the November 2002 revision of the draft. Is there a new revision of
> the draft?
not yet, primarily driven by the interest in the group.
Now since there is some feedback, we'll be happy to incorporate it and send the
update.

> 1. Section 4.5 "Failover Session State AVP".
> The FSS AVP has one session per AVP. Wouldn't it be more efficient to allow
> multiple sessions per AVP? This would be more efficient in terms of the
> message size and also the computation required to optionally hide the AVP.
> Putting multiple sessions in a single AVP would not preclude sending
> multiple FSQ or FSR messages.
Initially we thought of bundling them in one single AVP, in fact we were
thinking of pairing 'tid, sid' pairs to leverage even more, and as you pointed
out the advantages are obvious, however there are some disadvantages:
- bundling them together mandates all sessions to assume similar AVP
characterstics, like whether to hide them or not, etc. Not that it is a big
deal, but we thought the similar flexibility is provided during session
establishment.
- In a more scalable deployment (i.e. about 30k l2tp sessions per tunnel) we
thought there would be about 1k sessions (on the higher side) that would get
stuck in a dangling state (there are only two such states for incoming calls,
viz. ICCN not ZLB Acked, or ICRP not Acked). About 1k such messages could
easily be handled in one or two FSQ, FSR messages. I mean overhead of about 50%
(please note this is not the CPU overhead, rather more bandwidth consumption)
was okay. I mean, AVP encapsulation in general is not the best for conversation
of bandwidth, but it gives flexibility. Tommorw if we'd like to add more
parameters to the 'Failover Session State AVP'.
- Implementation wise, parsing one AVP for a session looked much simpler. 

> 2. Creating new sessions in a recovered tunnel.
> After a peer fails, it starts recovery by creating a new tunnel and adding
> the old tunnel ID AVP to the SCCRQ message. Once the tunnel is up, FSQ and
> FSR messages can be exchanged between the peers to synchronize session state
> for pre-existing sessions. There is no specific point at which the session
> synchronization is known to be complete. My question is: at what point can
> new sessions be created on this tunnel? If a new session is created before
> session state is synchronized, one end could attempt to create a session
> with a session id that is unused on its end but is in use for a session at
> the peer. This would cause the peer to fail the session creation request it
> receives. By itself this is not a big problem but it would be nice if some
> mechanism exists to avoid this problem. If adding a mechanism for this is
> not possible some text should be added to the document explaining this
> problem.
Good that you brought it up, may be it needs more clarification. Couple of
things:
- New sessions can be created on the tunnel as soon as the new tunnel is
established.
- Old sessions that were in established state are moved (rather, considered
moved by software) to the new tunnel
- Not every such session's state is synchronized. They are either 'dropped' if
they were not in established state, and they are 'moved' if they were in
established state. However, there are situations, as explained in section
2.3.3, some session would be 'dropped' on one side where other side would
consider them in established state and move them. Such sessions, could be
explicitly synchronized by FSQ and FSR messages.
- In such process, some sessions that have inconsistent states on two sides
might result in session establishment failure, which would then help bring the
peers in sync on sessions and their state. This needs to be mentioned,
explicitly to make the text clear, as you indicate.

> 3. When the two peers of a tunnel are both failover capable and one of the
> peers goes down, how long should the other peer save the state for the
> tunnel for a possible failover recovery?
As defined by RFC2661 and configured values of control packet timeouts.

> It could happen that the peer died and is not coming back for a long long
> time. Should the tunnel be deleted as usual when the L2TP tunnel keepalive
> mechanism detects the tunnel is down?
Tunnel keep alives (Hellos), as per rfc2661, would start with 2 second retires
wihch is exponentially backed off and say retried upto 6 times, would take
about a minute to teardown the entire tunnel. This means, entire restart
process shouldn't take more than a minute for a scalable deployment. This was
one of the consideration during the design. Besides, one MUST recover the
sessions way before PPP LCP Echo requests times out - which is typically about
40 seconds.

> 4. Old Tunnel ID and Old Local Tunnel ID AVPs.
> Both these AVPs are sent in both SCCRQ and SCCRP messages. Sending them in
> the SCCRQ should be sufficient. Is there any use of sending them in the
> SCCRP also?
The failed node puts them in SCCRQ, and its peer puts them in SCCRP.
Getting these values back in SCCRP would validate that peer has associated the
right old tunnel with the new tunnel. Old Local Tunnel ID AVP is kept only for
security purposes. So it would be difficult to guess 2^32 bit unique value (16
bit Old Tunnel ID and 16 bit Old Local Tunnel ID)

> 5. Section 4.3 Old Tunnel ID AVP.
> The packet format is missing the AVP value "old tunnel id".
I think we missed it. Thanks for pointing it out.

thanks,
-- vipin

> 
> Thanks,
> Puneet
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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


From exim@www1.ietf.org  Tue Aug  5 19:18:32 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 TAA02799
	for <l2tpext-archive@odin.ietf.org>; Tue, 5 Aug 2003 19:18:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kB49-0004gV-Uy
	for l2tpext-archive@odin.ietf.org; Tue, 05 Aug 2003 19:18:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h75NI5q6018003
	for l2tpext-archive@odin.ietf.org; Tue, 5 Aug 2003 19:18:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kB49-0004gI-Qx
	for l2tpext-web-archive@optimus.ietf.org; Tue, 05 Aug 2003 19:18:05 -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 TAA02763
	for <l2tpext-web-archive@ietf.org>; Tue, 5 Aug 2003 19:18:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kB48-0006cQ-00
	for l2tpext-web-archive@ietf.org; Tue, 05 Aug 2003 19:18:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19kB47-0006cL-00
	for l2tpext-web-archive@ietf.org; Tue, 05 Aug 2003 19:18:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kB45-0004do-9f; Tue, 05 Aug 2003 19:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19kB3Z-0004cC-0i
	for l2tpext@optimus.ietf.org; Tue, 05 Aug 2003 19:17:29 -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 TAA02724
	for <l2tpext@ietf.org>; Tue, 5 Aug 2003 19:17:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19kB3X-0006be-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 19:17:27 -0400
Received: from web41312.mail.yahoo.com ([66.218.93.61])
	by ietf-mx with smtp (Exim 4.12)
	id 19kB3W-0006b5-00
	for l2tpext@ietf.org; Tue, 05 Aug 2003 19:17:26 -0400
Message-ID: <20030805231655.35954.qmail@web41312.mail.yahoo.com>
Received: from [66.17.149.13] by web41312.mail.yahoo.com via HTTP; Tue, 05 Aug 2003 16:16:55 PDT
Date: Tue, 5 Aug 2003 16:16:55 -0700 (PDT)
From: Vipin Jain <vipinietf@yahoo.com>
Subject: Re: [L2tpext] Comments on draft-ietf-l2tpext-failover-01
To: Puneet Sood <psood@nortelnetworks.com>,
        "'l2tpext@ietf.org'" <l2tpext@ietf.org>
Cc: vipin@riverstonenet.com
In-Reply-To: <8B888AAAAB0FD31189590008C79184431431C0A9@zbl6c002.corpeast.baynetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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>


thanks for your comments. my comments inline..

> I have the November 2002 revision of the draft. Is there a new revision of
> the draft?
not yet, primarily driven by the interest in the group.
Now since there is some feedback, we'll be happy to incorporate it and send the
update.

> 1. Section 4.5 "Failover Session State AVP".
> The FSS AVP has one session per AVP. Wouldn't it be more efficient to allow
> multiple sessions per AVP? This would be more efficient in terms of the
> message size and also the computation required to optionally hide the AVP.
> Putting multiple sessions in a single AVP would not preclude sending
> multiple FSQ or FSR messages.
Initially we thought of bundling them in one single AVP, in fact we were
thinking of pairing 'tid, sid' pairs to leverage even more, and as you pointed
out the advantages are obvious, however there are some disadvantages:
- bundling them together mandates all sessions to assume similar AVP
characterstics, like whether to hide them or not, etc. Not that it is a big
deal, but we thought the similar flexibility is provided during session
establishment.
- In a more scalable deployment (i.e. about 30k l2tp sessions per tunnel) we
thought there would be about 1k sessions (on the higher side) that would get
stuck in a dangling state (there are only two such states for incoming calls,
viz. ICCN not ZLB Acked, or ICRP not Acked). About 1k such messages could
easily be handled in one or two FSQ, FSR messages. I mean overhead of about 50%
(please note this is not the CPU overhead, rather more bandwidth consumption)
was okay. I mean, AVP encapsulation in general is not the best for conversation
of bandwidth, but it gives flexibility. Tommorw if we'd like to add more
parameters to the 'Failover Session State AVP'.
- Implementation wise, parsing one AVP for a session looked much simpler. 

> 2. Creating new sessions in a recovered tunnel.
> After a peer fails, it starts recovery by creating a new tunnel and adding
> the old tunnel ID AVP to the SCCRQ message. Once the tunnel is up, FSQ and
> FSR messages can be exchanged between the peers to synchronize session state
> for pre-existing sessions. There is no specific point at which the session
> synchronization is known to be complete. My question is: at what point can
> new sessions be created on this tunnel? If a new session is created before
> session state is synchronized, one end could attempt to create a session
> with a session id that is unused on its end but is in use for a session at
> the peer. This would cause the peer to fail the session creation request it
> receives. By itself this is not a big problem but it would be nice if some
> mechanism exists to avoid this problem. If adding a mechanism for this is
> not possible some text should be added to the document explaining this
> problem.
Good that you brought it up, may be it needs more clarification. Couple of
things:
- New sessions can be created on the tunnel as soon as the new tunnel is
established.
- Old sessions that were in established state are moved (rather, considered
moved by software) to the new tunnel
- Not every such session's state is synchronized. They are either 'dropped' if
they were not in established state, and they are 'moved' if they were in
established state. However, there are situations, as explained in section
2.3.3, some session would be 'dropped' on one side where other side would
consider them in established state and move them. Such sessions, could be
explicitly synchronized by FSQ and FSR messages.
- In such process, some sessions that have inconsistent states on two sides
might result in session establishment failure, which would then help bring the
peers in sync on sessions and their state. This needs to be mentioned,
explicitly to make the text clear, as you indicate.

> 3. When the two peers of a tunnel are both failover capable and one of the
> peers goes down, how long should the other peer save the state for the
> tunnel for a possible failover recovery?
As defined by RFC2661 and configured values of control packet timeouts.

> It could happen that the peer died and is not coming back for a long long
> time. Should the tunnel be deleted as usual when the L2TP tunnel keepalive
> mechanism detects the tunnel is down?
Tunnel keep alives (Hellos), as per rfc2661, would start with 2 second retires
wihch is exponentially backed off and say retried upto 6 times, would take
about a minute to teardown the entire tunnel. This means, entire restart
process shouldn't take more than a minute for a scalable deployment. This was
one of the consideration during the design. Besides, one MUST recover the
sessions way before PPP LCP Echo requests times out - which is typically about
40 seconds.

> 4. Old Tunnel ID and Old Local Tunnel ID AVPs.
> Both these AVPs are sent in both SCCRQ and SCCRP messages. Sending them in
> the SCCRQ should be sufficient. Is there any use of sending them in the
> SCCRP also?
The failed node puts them in SCCRQ, and its peer puts them in SCCRP.
Getting these values back in SCCRP would validate that peer has associated the
right old tunnel with the new tunnel. Old Local Tunnel ID AVP is kept only for
security purposes. So it would be difficult to guess 2^32 bit unique value (16
bit Old Tunnel ID and 16 bit Old Local Tunnel ID)

> 5. Section 4.3 Old Tunnel ID AVP.
> The packet format is missing the AVP value "old tunnel id".
I think we missed it. Thanks for pointing it out.

thanks,
-- vipin

> 
> Thanks,
> Puneet
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



From l2tpext-admin@ietf.org  Sun Aug 17 20:06:38 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 UAA24519
	for <l2tpext-archive@lists.ietf.org>; Sun, 17 Aug 2003 20:06:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19oXX7-0007ub-ER; Sun, 17 Aug 2003 20:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19niTa-0007Bm-BJ
	for l2tpext@optimus.ietf.org; Fri, 15 Aug 2003 13:34:58 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06013;
	Fri, 15 Aug 2003 13:34:53 -0400 (EDT)
Message-Id: <200308151734.NAA06013@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: Fri, 15 Aug 2003 13:34:53 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-10.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Layer Two Tunneling Protocol (Version 3)
	Author(s)	: J. Lau, M. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-10.txt
	Pages		: 88
	Date		: 2003-8-15
	
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-10.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-l2tp-base-10.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-10.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-8-15124010.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Sun Aug 17 20:06:39 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 UAA24534
	for <l2tpext-archive@odin.ietf.org>; Sun, 17 Aug 2003 20:06:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19oXXJ-0007vn-N7
	for l2tpext-archive@odin.ietf.org; Sun, 17 Aug 2003 20:06:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7I06D1U030483
	for l2tpext-archive@odin.ietf.org; Sun, 17 Aug 2003 20:06:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19oXXJ-0007va-J5
	for l2tpext-web-archive@optimus.ietf.org; Sun, 17 Aug 2003 20:06:13 -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 UAA24507
	for <l2tpext-web-archive@ietf.org>; Sun, 17 Aug 2003 20:06:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19oXXH-0003Lo-00
	for l2tpext-web-archive@ietf.org; Sun, 17 Aug 2003 20:06:11 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19oXXH-0003Lk-00
	for l2tpext-web-archive@ietf.org; Sun, 17 Aug 2003 20:06:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19oXX7-0007ub-ER; Sun, 17 Aug 2003 20:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19niTa-0007Bm-BJ
	for l2tpext@optimus.ietf.org; Fri, 15 Aug 2003 13:34:58 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06013;
	Fri, 15 Aug 2003 13:34:53 -0400 (EDT)
Message-Id: <200308151734.NAA06013@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: Fri, 15 Aug 2003 13:34:53 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-10.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Layer Two Tunneling Protocol (Version 3)
	Author(s)	: J. Lau, M. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-10.txt
	Pages		: 88
	Date		: 2003-8-15
	
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-10.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-l2tp-base-10.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-10.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-8-15124010.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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



From l2tpext-admin@ietf.org  Mon Aug 18 10:13:42 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 KAA20237
	for <l2tpext-archive@lists.ietf.org>; Mon, 18 Aug 2003 10:13:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19okkn-0006rz-If; Mon, 18 Aug 2003 10:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19okkg-0006rg-63
	for l2tpext@optimus.ietf.org; Mon, 18 Aug 2003 10:12: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 KAA20141
	for <l2tpext@ietf.org>; Mon, 18 Aug 2003 10:12:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19okke-0007Kk-00
	for l2tpext@ietf.org; Mon, 18 Aug 2003 10:12:52 -0400
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19okkd-0007Kg-00
	for l2tpext@ietf.org; Mon, 18 Aug 2003 10:12:51 -0400
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 18 Aug 2003 16:11:41 +0200
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h7IEA348000664;
	Mon, 18 Aug 2003 16:10:03 +0200 (MET DST)
Received: from cisco.com (sjc-vpn1-597.cisco.com [10.21.98.85])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA11676;
	Mon, 18 Aug 2003 16:12:17 +0200 (MET DST)
Message-ID: <3F40DEC1.3070505@cisco.com>
Date: Mon, 18 Aug 2003 16:12:17 +0200
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
CC: narten@us.ibm.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] WG Last Call for draft-ietf-l2tpext-l2tp-base-10.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


This is Working Group last call for draft-ietf-l2tpext-l2tp-base-10.txt. This 
version contains revisisions based on a review by James Carlson (at the request 
of the IESG) and additional editorial changes.

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

Thanks,

- Mark



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


From exim@www1.ietf.org  Mon Aug 18 10:13:44 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 KAA20252
	for <l2tpext-archive@odin.ietf.org>; Mon, 18 Aug 2003 10:13:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19okl4-0006sw-RN
	for l2tpext-archive@odin.ietf.org; Mon, 18 Aug 2003 10:13:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7IEDIID026460
	for l2tpext-archive@odin.ietf.org; Mon, 18 Aug 2003 10:13:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19okl4-0006sh-LL
	for l2tpext-web-archive@optimus.ietf.org; Mon, 18 Aug 2003 10:13:18 -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 KAA20189
	for <l2tpext-web-archive@ietf.org>; Mon, 18 Aug 2003 10:13:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19okl2-0007LA-00
	for l2tpext-web-archive@ietf.org; Mon, 18 Aug 2003 10:13:16 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19okl1-0007L7-00
	for l2tpext-web-archive@ietf.org; Mon, 18 Aug 2003 10:13:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19okkn-0006rz-If; Mon, 18 Aug 2003 10:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19okkg-0006rg-63
	for l2tpext@optimus.ietf.org; Mon, 18 Aug 2003 10:12: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 KAA20141
	for <l2tpext@ietf.org>; Mon, 18 Aug 2003 10:12:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19okke-0007Kk-00
	for l2tpext@ietf.org; Mon, 18 Aug 2003 10:12:52 -0400
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 19okkd-0007Kg-00
	for l2tpext@ietf.org; Mon, 18 Aug 2003 10:12:51 -0400
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 18 Aug 2003 16:11:41 +0200
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h7IEA348000664;
	Mon, 18 Aug 2003 16:10:03 +0200 (MET DST)
Received: from cisco.com (sjc-vpn1-597.cisco.com [10.21.98.85])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA11676;
	Mon, 18 Aug 2003 16:12:17 +0200 (MET DST)
Message-ID: <3F40DEC1.3070505@cisco.com>
Date: Mon, 18 Aug 2003 16:12:17 +0200
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
CC: narten@us.ibm.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] WG Last Call for draft-ietf-l2tpext-l2tp-base-10.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


This is Working Group last call for draft-ietf-l2tpext-l2tp-base-10.txt. This 
version contains revisisions based on a review by James Carlson (at the request 
of the IESG) and additional editorial changes.

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

Thanks,

- Mark



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



From l2tpext-admin@ietf.org  Fri Aug 22 10:11:34 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 KAA26123
	for <l2tpext-archive@lists.ietf.org>; Fri, 22 Aug 2003 10:11:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19qCd3-0004bV-4l; Fri, 22 Aug 2003 10:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19qCTu-0003b2-V7
	for l2tpext@optimus.ietf.org; Fri, 22 Aug 2003 10:01: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 KAA24861;
	Fri, 22 Aug 2003 10:01:28 -0400 (EDT)
Message-Id: <200308221401.KAA24861@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: Fri, 22 Aug 2003 10:01:28 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-failover-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		: Fail Over extensions for L2TP 'failover'
	Author(s)	: R. Penno, K. Parikh et al.
	Filename	: draft-ietf-l2tpext-failover-02.txt
	Pages		: 13
	Date		: 2003-8-22
	
L2TP is a connection-oriented protocol that has shared state between
active endpoints. Some of this shared state is vital for operation
but may be rather volatile in nature, such as packet sequence numbers
used on the L2TP Control Connection. When failure of one side of a
control connection occurs, a new control connection is created and
associated with the old connection by exchanging information about
the old connection. Such a mechanism is not intended as a replacement
for an active fail over with some mirrored connection states, but as
an aid just for those parameters that are particularly difficult to
have immediately available. Protocol extensions to L2TP defined in
this document are intended to facilitate state recovery, providing
additional resiliency in an L2TP network and improving a remote
system's layer 2 connectivity.

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

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Fri Aug 22 10:11: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 KAA26140
	for <l2tpext-archive@odin.ietf.org>; Fri, 22 Aug 2003 10:11: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 19qCdD-0004cZ-9d
	for l2tpext-archive@odin.ietf.org; Fri, 22 Aug 2003 10:11:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h7MEBBZK017757
	for l2tpext-archive@odin.ietf.org; Fri, 22 Aug 2003 10:11:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19qCdD-0004cK-5M
	for l2tpext-web-archive@optimus.ietf.org; Fri, 22 Aug 2003 10:11: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 KAA26066
	for <l2tpext-web-archive@ietf.org>; Fri, 22 Aug 2003 10:11:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19qCdA-0004Op-00
	for l2tpext-web-archive@ietf.org; Fri, 22 Aug 2003 10:11:09 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19qCdA-0004Ok-00
	for l2tpext-web-archive@ietf.org; Fri, 22 Aug 2003 10:11:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19qCd3-0004bV-4l; Fri, 22 Aug 2003 10:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19qCTu-0003b2-V7
	for l2tpext@optimus.ietf.org; Fri, 22 Aug 2003 10:01: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 KAA24861;
	Fri, 22 Aug 2003 10:01:28 -0400 (EDT)
Message-Id: <200308221401.KAA24861@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: Fri, 22 Aug 2003 10:01:28 -0400
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-failover-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		: Fail Over extensions for L2TP 'failover'
	Author(s)	: R. Penno, K. Parikh et al.
	Filename	: draft-ietf-l2tpext-failover-02.txt
	Pages		: 13
	Date		: 2003-8-22
	
L2TP is a connection-oriented protocol that has shared state between
active endpoints. Some of this shared state is vital for operation
but may be rather volatile in nature, such as packet sequence numbers
used on the L2TP Control Connection. When failure of one side of a
control connection occurs, a new control connection is created and
associated with the old connection by exchanging information about
the old connection. Such a mechanism is not intended as a replacement
for an active fail over with some mirrored connection states, but as
an aid just for those parameters that are particularly difficult to
have immediately available. Protocol extensions to L2TP defined in
this document are intended to facilitate state recovery, providing
additional resiliency in an L2TP network and improving a remote
system's layer 2 connectivity.

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

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

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

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

--OtherAccess--

--NextPart--



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



