From l2tpext-admin@ietf.org  Fri Jan  9 10:09:40 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03292
	for <l2tpext-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:09:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeyFw-0001xA-TA; Fri, 09 Jan 2004 10:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeyFg-0001wu-8o
	for l2tpext@optimus.ietf.org; Fri, 09 Jan 2004 10:08:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03218
	for <l2tpext@ietf.org>; Fri, 9 Jan 2004 10:08:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeyFT-0006R7-00
	for l2tpext@ietf.org; Fri, 09 Jan 2004 10:08:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeyBs-0006D1-00
	for l2tpext@ietf.org; Fri, 09 Jan 2004 10:04:49 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=beta.jnpr.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aey6o-0005um-00
	for l2tpext@ietf.org; Fri, 09 Jan 2004 09:59:35 -0500
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by beta.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 9 Jan 2004 06:58:39 -0800
Received: from juniper.net ([10.10.248.153] RDNS failed) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 9 Jan 2004 09:58:37 -0500
Message-ID: <3FFEC1A0.2010503@juniper.net>
Date: Fri, 09 Jan 2004 09:58:40 -0500
From: "Paul W. Howard" <phoward@juniper.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
References: <3FEF31C0.8020409@cisco.com>
In-Reply-To: <3FEF31C0.8020409@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jan 2004 14:58:37.0900 (UTC) FILETIME=[0FD2A0C0:01C3D6C1]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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

I have a few questions/concerns in regards to this draft:

1) This proposal presents what appears to be an entirely different 
mechanism than that proposed in the v2 draft 
(draft-vipin-l2tpext-failover-02.txt).   It would seem to be important 
that we attempt to have a single mechanism for both v2 and v3 or to at 
least minimize the differences to those that are unavoidable.

2) I don't understand the basic reset of the sequence number space for 
the control connection.   Is this setting up a replacement tunnel or 
attempting to reset the sequence numbers of the extant tunnel?

3) It would appear that there is a linear relationship between the 
number of packets required for the failover and the number of 
established sessions.   This would seem to present issues with scalability.

Thanx,

Paul Howard

W. Mark Townsley wrote:

>
> I would like to ask that interested parties review the following draft 
> "Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
> provide comments to the list. This draft was originally presented in 
> Vienna, and updated based on comments during the meeting.
>
> http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
>
> The authors would like to make this a WG document.
>
> Thanks,
>
> - Mark
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Fri Jan  9 10:35:48 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05706
	for <l2tpext-archive@odin.ietf.org>; Fri, 9 Jan 2004 10:35:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeyfQ-0002z1-Mw
	for l2tpext-archive@odin.ietf.org; Fri, 09 Jan 2004 10:35:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i09FZKDL011465
	for l2tpext-archive@odin.ietf.org; Fri, 9 Jan 2004 10:35:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeyfQ-0002yq-F3
	for l2tpext-web-archive@optimus.ietf.org; Fri, 09 Jan 2004 10:35:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05582
	for <l2tpext-web-archive@ietf.org>; Fri, 9 Jan 2004 10:35:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aeyd9-0007fq-00
	for l2tpext-web-archive@ietf.org; Fri, 09 Jan 2004 10:32:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeyNV-0006nc-00
	for l2tpext-web-archive@ietf.org; Fri, 09 Jan 2004 10:16:50 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeyGW-0006TZ-00
	for l2tpext-web-archive@ietf.org; Fri, 09 Jan 2004 10:09:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeyFw-0001xA-TA; Fri, 09 Jan 2004 10:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeyFg-0001wu-8o
	for l2tpext@optimus.ietf.org; Fri, 09 Jan 2004 10:08:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03218
	for <l2tpext@ietf.org>; Fri, 9 Jan 2004 10:08:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AeyFT-0006R7-00
	for l2tpext@ietf.org; Fri, 09 Jan 2004 10:08:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AeyBs-0006D1-00
	for l2tpext@ietf.org; Fri, 09 Jan 2004 10:04:49 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=beta.jnpr.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aey6o-0005um-00
	for l2tpext@ietf.org; Fri, 09 Jan 2004 09:59:35 -0500
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by beta.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 9 Jan 2004 06:58:39 -0800
Received: from juniper.net ([10.10.248.153] RDNS failed) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 9 Jan 2004 09:58:37 -0500
Message-ID: <3FFEC1A0.2010503@juniper.net>
Date: Fri, 09 Jan 2004 09:58:40 -0500
From: "Paul W. Howard" <phoward@juniper.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
References: <3FEF31C0.8020409@cisco.com>
In-Reply-To: <3FEF31C0.8020409@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jan 2004 14:58:37.0900 (UTC) FILETIME=[0FD2A0C0:01C3D6C1]
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I have a few questions/concerns in regards to this draft:

1) This proposal presents what appears to be an entirely different 
mechanism than that proposed in the v2 draft 
(draft-vipin-l2tpext-failover-02.txt).   It would seem to be important 
that we attempt to have a single mechanism for both v2 and v3 or to at 
least minimize the differences to those that are unavoidable.

2) I don't understand the basic reset of the sequence number space for 
the control connection.   Is this setting up a replacement tunnel or 
attempting to reset the sequence numbers of the extant tunnel?

3) It would appear that there is a linear relationship between the 
number of packets required for the failover and the number of 
established sessions.   This would seem to present issues with scalability.

Thanx,

Paul Howard

W. Mark Townsley wrote:

>
> I would like to ask that interested parties review the following draft 
> "Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
> provide comments to the list. This draft was originally presented in 
> Vienna, and updated based on comments during the meeting.
>
> http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
>
> The authors would like to make this a WG document.
>
> Thanks,
>
> - Mark
>
>
> _______________________________________________
> 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 mailman-admin@ietf.org  Fri Jan  9 12:57:26 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18514
	for <l2tpext-archive@lists.ietf.org>; Fri, 9 Jan 2004 12:57:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af0sV-0007Dq-Ud
	for l2tpext-archive@lists.ietf.org; Fri, 09 Jan 2004 12:56:59 -0500
Date: Fri, 09 Jan 2004 12:56:59 -0500
Message-ID: <20040109175659.9164.66781.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 Jan 11 08:55:40 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28498
	for <l2tpext-archive@lists.ietf.org>; Sun, 11 Jan 2004 08:55:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Afg3T-0000si-Hh; Sun, 11 Jan 2004 08:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Afg35-0000rP-DM
	for l2tpext@optimus.ietf.org; Sun, 11 Jan 2004 08:54:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28402
	for <l2tpext@ietf.org>; Sun, 11 Jan 2004 08:54:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afg34-0005L0-00
	for l2tpext@ietf.org; Sun, 11 Jan 2004 08:54:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Afg1A-0005Cg-00
	for l2tpext@ietf.org; Sun, 11 Jan 2004 08:52:43 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AffvY-0004zI-00
	for l2tpext@ietf.org; Sun, 11 Jan 2004 08:46:53 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Sun, 11 Jan 2004 15:45:26 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <Y3GCT2LW>; Sun, 11 Jan 2004 15:44:10 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085FEA@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'Paul W. Howard'" <phoward@juniper.net>,
        "W. Mark Townsley"
	 <townsley@cisco.com>
Cc: l2tpext@ietf.org
Subject: RE: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
Date: Sun, 11 Jan 2004 15:44:09 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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,
See my response in the mail body.

Sharon Galtzur

> -----Original Message-----
> From: Paul W. Howard [mailto:phoward@juniper.net]
> Sent: Friday, January 09, 2004 4:59 PM
> To: W. Mark Townsley
> Cc: l2tpext@ietf.org
> Subject: Re: [L2tpext] Please comment on 
> draft-galtzur-l2tpext-gr-01.txt
> 
> 
> I have a few questions/concerns in regards to this draft:
> 
> 1) This proposal presents what appears to be an entirely different 
> mechanism than that proposed in the v2 draft 
> (draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
> important 
> that we attempt to have a single mechanism for both v2 and v3 
> or to at 
> least minimize the differences to those that are unavoidable.

In LDP there is exactly the same occurrence - 
RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 

This draft follows the model presented in RFC 3478 with adaptation to L2TPv3

> 
> 2) I don't understand the basic reset of the sequence number 
> space for 
> the control connection.   Is this setting up a replacement tunnel or 
> attempting to reset the sequence numbers of the extant tunnel?

The tunnel is restarted almost exactly as in
draft-ietf-l2tpext-l2tp-base-11.txt
One technical difference is the added AVP to advertise the graceful restart
capability.
Another difference is that while restarting the sessions certain information
need 
to endure the restart (i.e. Session ID, Cookie value etc) that will allow
the data path
to continue without interruptions.

> 
> 3) It would appear that there is a linear relationship between the 
> number of packets required for the fail over and the number of 
> established sessions.   This would seem to present issues 
> with scalability.

The behavior of the graceful restart proposal is not worse then normal start
of 
L2TPv3 (since the mechanism of the graceful and non graceful restart are
practically the same). 
If there is scalability issue in this proposal it is inherit to the whole
L2TP model and not restricted to 
the proposed graceful restart


> 
> Thanx,
> 
> Paul Howard
> 
> W. Mark Townsley wrote:
> 
> >
> > I would like to ask that interested parties review the 
> following draft 
> > "Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
> > provide comments to the list. This draft was originally 
> presented in 
> > Vienna, and updated based on comments during the meeting.
> >
> > http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
> >
> > The authors would like to make this a WG document.
> >
> > Thanks,
> >
> > - Mark
> >
> >
> > _______________________________________________
> > 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
> 

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


From exim@www1.ietf.org  Sun Jan 11 08:59:22 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28675
	for <l2tpext-archive@odin.ietf.org>; Sun, 11 Jan 2004 08:59:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Afg7B-000123-AH
	for l2tpext-archive@odin.ietf.org; Sun, 11 Jan 2004 08:58:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0BDwrNL003961
	for l2tpext-archive@odin.ietf.org; Sun, 11 Jan 2004 08:58:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Afg7B-00011o-5u
	for l2tpext-web-archive@optimus.ietf.org; Sun, 11 Jan 2004 08:58:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28634
	for <l2tpext-web-archive@ietf.org>; Sun, 11 Jan 2004 08:58:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afg79-0005c0-00
	for l2tpext-web-archive@ietf.org; Sun, 11 Jan 2004 08:58:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Afg5A-0005VC-00
	for l2tpext-web-archive@ietf.org; Sun, 11 Jan 2004 08:56:49 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afg3b-0005PY-00
	for l2tpext-web-archive@ietf.org; Sun, 11 Jan 2004 08:55:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Afg3T-0000si-Hh; Sun, 11 Jan 2004 08:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Afg35-0000rP-DM
	for l2tpext@optimus.ietf.org; Sun, 11 Jan 2004 08:54:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28402
	for <l2tpext@ietf.org>; Sun, 11 Jan 2004 08:54:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Afg34-0005L0-00
	for l2tpext@ietf.org; Sun, 11 Jan 2004 08:54:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Afg1A-0005Cg-00
	for l2tpext@ietf.org; Sun, 11 Jan 2004 08:52:43 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AffvY-0004zI-00
	for l2tpext@ietf.org; Sun, 11 Jan 2004 08:46:53 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Sun, 11 Jan 2004 15:45:26 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <Y3GCT2LW>; Sun, 11 Jan 2004 15:44:10 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085FEA@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'Paul W. Howard'" <phoward@juniper.net>,
        "W. Mark Townsley"
	 <townsley@cisco.com>
Cc: l2tpext@ietf.org
Subject: RE: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
Date: Sun, 11 Jan 2004 15:44:09 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hello all,
See my response in the mail body.

Sharon Galtzur

> -----Original Message-----
> From: Paul W. Howard [mailto:phoward@juniper.net]
> Sent: Friday, January 09, 2004 4:59 PM
> To: W. Mark Townsley
> Cc: l2tpext@ietf.org
> Subject: Re: [L2tpext] Please comment on 
> draft-galtzur-l2tpext-gr-01.txt
> 
> 
> I have a few questions/concerns in regards to this draft:
> 
> 1) This proposal presents what appears to be an entirely different 
> mechanism than that proposed in the v2 draft 
> (draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
> important 
> that we attempt to have a single mechanism for both v2 and v3 
> or to at 
> least minimize the differences to those that are unavoidable.

In LDP there is exactly the same occurrence - 
RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 

This draft follows the model presented in RFC 3478 with adaptation to L2TPv3

> 
> 2) I don't understand the basic reset of the sequence number 
> space for 
> the control connection.   Is this setting up a replacement tunnel or 
> attempting to reset the sequence numbers of the extant tunnel?

The tunnel is restarted almost exactly as in
draft-ietf-l2tpext-l2tp-base-11.txt
One technical difference is the added AVP to advertise the graceful restart
capability.
Another difference is that while restarting the sessions certain information
need 
to endure the restart (i.e. Session ID, Cookie value etc) that will allow
the data path
to continue without interruptions.

> 
> 3) It would appear that there is a linear relationship between the 
> number of packets required for the fail over and the number of 
> established sessions.   This would seem to present issues 
> with scalability.

The behavior of the graceful restart proposal is not worse then normal start
of 
L2TPv3 (since the mechanism of the graceful and non graceful restart are
practically the same). 
If there is scalability issue in this proposal it is inherit to the whole
L2TP model and not restricted to 
the proposed graceful restart


> 
> Thanx,
> 
> Paul Howard
> 
> W. Mark Townsley wrote:
> 
> >
> > I would like to ask that interested parties review the 
> following draft 
> > "Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
> > provide comments to the list. This draft was originally 
> presented in 
> > Vienna, and updated based on comments during the meeting.
> >
> > http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
> >
> > The authors would like to make this a WG document.
> >
> > Thanks,
> >
> > - Mark
> >
> >
> > _______________________________________________
> > 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
> 

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



From l2tpext-admin@ietf.org  Wed Jan 14 14:27:37 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04488
	for <l2tpext-archive@lists.ietf.org>; Wed, 14 Jan 2004 14:27:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgqfM-00027v-6w; Wed, 14 Jan 2004 14:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgqfI-00027V-3s
	for l2tpext@optimus.ietf.org; Wed, 14 Jan 2004 14:26:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04461
	for <l2tpext@ietf.org>; Wed, 14 Jan 2004 14:26:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqfF-0003kj-00
	for l2tpext@ietf.org; Wed, 14 Jan 2004 14:26:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgqeM-0003jA-00
	for l2tpext@ietf.org; Wed, 14 Jan 2004 14:26:00 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=gamma.jnpr.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqdU-0003en-00
	for l2tpext@ietf.org; Wed, 14 Jan 2004 14:25:04 -0500
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by gamma.jnpr.net with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 14 Jan 2004 11:24:33 -0800
Received: from juniper.net ([10.10.248.146] RDNS failed) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 14 Jan 2004 14:24:32 -0500
Message-ID: <40059772.60607@juniper.net>
Date: Wed, 14 Jan 2004 14:24:34 -0500
From: "Paul W. Howard" <phoward@juniper.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sharon Galtzur <sharon@AXERRA.com>
CC: "W. Mark Townsley" <townsley@cisco.com>, l2tpext@ietf.org
Subject: Re: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
References: <AF5018AC03D1D411ABB70002A509132601085FEA@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A509132601085FEA@TLV1>
Content-Type: multipart/alternative;
 boundary="------------070109090105070106030900"
X-OriginalArrivalTime: 14 Jan 2004 19:24:32.0144 (UTC) FILETIME=[095BD100:01C3DAD4]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_MESSAGE,
	HTML_TITLE_EMPTY autolearn=no version=2.60
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

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

Sharon,

Thanx for your responses.   Please see further comments inline ([pwh])

Thanx,

Paul Howard

Sharon Galtzur wrote:

>Hello all,
>See my response in the mail body.
>
>Sharon Galtzur
>
>  
>
>>-----Original Message-----
>>From: Paul W. Howard [mailto:phoward@juniper.net]
>>Sent: Friday, January 09, 2004 4:59 PM
>>To: W. Mark Townsley
>>Cc: l2tpext@ietf.org
>>Subject: Re: [L2tpext] Please comment on 
>>draft-galtzur-l2tpext-gr-01.txt
>>
>>
>>I have a few questions/concerns in regards to this draft:
>>
>>1) This proposal presents what appears to be an entirely different 
>>mechanism than that proposed in the v2 draft 
>>(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
>>important 
>>that we attempt to have a single mechanism for both v2 and v3 
>>or to at 
>>least minimize the differences to those that are unavoidable.
>>    
>>
>
>In LDP there is exactly the same occurrence - 
>RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
>RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 
>
>This draft follows the model presented in RFC 3478 with adaptation to L2TPv3
>  
>
[pwh] My understanding is that 3478 and 3479 present signficantly 
different approaches to the problem of dealing with a failed endpoint - 
3478 recovers by learning from the non-failed endpoint (graceful 
restart) whereas 3479 recovers by state replication on the failed 
endpoint.    Both your draft and Vipin's would seem to fall into the 
category of graceful restart (i.e. learning from the non-failed 
endpoint).   Both of the l2tp drafts deal with trying to recover key 
pieces of the control plane that are not normally obtainable from the 
forwarding database - the sequence numbers of the control connection and 
the state (established or non-established) of each of the sessions.   It 
would thus seem reasonable to resolve the differences between these 
drafts and produce as common an approach as possible to graceful restart.

[pwh] btw - I misquoted the current version of the other draft - it's 
draft-ietf-l2tpext-failover-02.txt

>  
>
>>2) I don't understand the basic reset of the sequence number 
>>space for 
>>the control connection.   Is this setting up a replacement tunnel or 
>>attempting to reset the sequence numbers of the extant tunnel?
>>    
>>
>
>The tunnel is restarted almost exactly as in
>draft-ietf-l2tpext-l2tp-base-11.txt
>One technical difference is the added AVP to advertise the graceful restart
>capability.
>Another difference is that while restarting the sessions certain information
>need 
>to endure the restart (i.e. Session ID, Cookie value etc) that will allow
>the data path
>to continue without interruptions.
>
[pwh] I'm not entirely clear on your answer.   There would seem to be 
two basic approaches to recovery of the control connection - one is to 
establish an entirely new control connection and eventually transfer the 
sessions from the old control connection to the new control connection; 
the other is to reset the extant control connection,   It's not clear to 
me from your answer or the draft which direction you are proposing.   
So, when I attempt to restart a control connection by sending an SCCRQ 
with the GR AVP and a non-zero recovery time, what is the value of the 
Assigned Control Connection Id AVP?  Is it the same as the one from the 
initial establishment (implies reset of the extant control connection) 
or a new value (implies a recovery control connection and transfer of 
the sessions from the old to the new)

>  
>
>>3) It would appear that there is a linear relationship between the 
>>number of packets required for the fail over and the number of 
>>established sessions.   This would seem to present issues 
>>with scalability.
>>    
>>
>
>The behavior of the graceful restart proposal is not worse then normal start
>of 
>L2TPv3 (since the mechanism of the graceful and non graceful restart are
>practically the same). 
>If there is scalability issue in this proposal it is inherit to the whole
>L2TP model and not restricted to 
>the proposed graceful restart
>
>  
>
[pwh] IMHO, there is a scability problem that needs to be addressed.    
When a failover occurs, the failed endpoint is in the process of trying 
to recover it's state not only for L2TP, but for all other applications 
running in the failed endpoint (e.g. IP, BGP, PPP, AAA, etc.).   It is a 
time of maximum stress on the failed endpoint coupled with restrictive 
time limits (e.g. BGP neighbor notifications).   Failover processes 
needs to be designed with minimal resource consumption.    This draft 
proposes 'n' packets to be sent from the failed endpoint to the 
non-failed endpoint where 'n' is the number of sessions between the 2 
endpoints.   This results in 10's of thousands if not 100's of thousands 
of packets to complete the recovery.    In order to avoid this issue, it 
would seem that the session recovery needs to be able to recover by 
packing multiple session recoveries per packet - thus reducing to n/m 
packets where m is the number of recoveries per packet.   As the primary 
recovery requirement for the session is to confirm that both endpoints 
believe the session to be in established state, this could reduce to 
sending the session id's of the established sessions from the failed 
endpoint to the non-failed endpoint followed by the non-failed endpoint 
sending back the session ids of the established sessions based on the 
intersection of what it received from the failed endpoint and it's local 
database.   Assuming say 256 session ids packed in a single packet (1K 
of data), then we end up with 2 * n / 256 packets to recover.   Thus 
with 100,000 sessions only 782 packets are required to recover instead 
of 100,000+ packets.  

>  
>
>>Thanx,
>>
>>Paul Howard
>>
>>W. Mark Townsley wrote:
>>
>>    
>>
>>>I would like to ask that interested parties review the 
>>>      
>>>
>>following draft 
>>    
>>
>>>"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
>>>provide comments to the list. This draft was originally 
>>>      
>>>
>>presented in 
>>    
>>
>>>Vienna, and updated based on comments during the meeting.
>>>
>>>http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
>>>
>>>The authors would like to make this a WG document.
>>>
>>>Thanks,
>>>
>>>- Mark
>>>
>>>
>>>_______________________________________________
>>>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
>>
>>    
>>
>
>  
>

--------------070109090105070106030900
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
Sharon,<br>
<br>
Thanx for your responses.&nbsp;&nbsp; Please see further comments inline ([pwh])<br>
<br>
Thanx,<br>
<br>
Paul Howard<br>
<br>
Sharon Galtzur wrote:<br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">Hello all,
See my response in the mail body.

Sharon Galtzur

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: Paul W. Howard [<a
 class="moz-txt-link-freetext" href="mailto:phoward@juniper.net">mailto:phoward@juniper.net</a>]
Sent: Friday, January 09, 2004 4:59 PM
To: W. Mark Townsley
Cc: <a
 class="moz-txt-link-abbreviated" href="mailto:l2tpext@ietf.org">l2tpext@ietf.org</a>
Subject: Re: [L2tpext] Please comment on 
draft-galtzur-l2tpext-gr-01.txt


I have a few questions/concerns in regards to this draft:

1) This proposal presents what appears to be an entirely different 
mechanism than that proposed in the v2 draft 
(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
important 
that we attempt to have a single mechanism for both v2 and v3 
or to at 
least minimize the differences to those that are unavoidable.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
In LDP there is exactly the same occurrence - 
RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 

This draft follows the model presented in RFC 3478 with adaptation to L2TPv3
  </pre>
</blockquote>
[pwh] My understanding is that 3478 and 3479 present signficantly
different approaches to the problem of dealing with a failed endpoint -
3478 recovers by learning from the non-failed endpoint (graceful
restart) whereas 3479 recovers by state replication on the failed
endpoint.&nbsp;&nbsp;&nbsp; Both your draft and Vipin's would seem to fall into the
category of graceful restart (i.e. learning from the non-failed
endpoint).&nbsp;&nbsp; Both of the l2tp drafts deal with trying to recover key
pieces of the control plane that are not normally obtainable from the
forwarding database - the sequence numbers of the control connection
and the state (established or non-established) of each of the
sessions.&nbsp;&nbsp; It would thus seem reasonable to resolve the differences
between these drafts and produce as common an approach as possible to
graceful restart.<br>
<br>
[pwh] btw - I misquoted the current version of the other draft - it's
draft-ietf-l2tpext-failover-02.txt<br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">  </pre>
  <blockquote type="cite">
    <pre wrap="">2) I don't understand the basic reset of the sequence number 
space for 
the control connection.   Is this setting up a replacement tunnel or 
attempting to reset the sequence numbers of the extant tunnel?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The tunnel is restarted almost exactly as in
draft-ietf-l2tpext-l2tp-base-11.txt
One technical difference is the added AVP to advertise the graceful restart
capability.
Another difference is that while restarting the sessions certain information
need 
to endure the restart (i.e. Session ID, Cookie value etc) that will allow
the data path
to continue without interruptions.</pre>
</blockquote>
[pwh] I'm not entirely clear on your answer.&nbsp;&nbsp; There would seem to be
two basic approaches to recovery of the control connection - one is to
establish an entirely new control connection and eventually transfer
the sessions from the old control connection to the new control
connection; the other is to reset the extant control connection,&nbsp;&nbsp; It's
not clear to me from your answer or the draft which direction you are
proposing.&nbsp;&nbsp; So, when I attempt to restart a control connection by
sending an SCCRQ with the GR AVP and a non-zero recovery time, what is
the value of the Assigned Control Connection Id AVP?&nbsp; Is it the same as
the one from the initial establishment (implies reset of the extant
control connection) or a new value (implies a recovery control
connection and transfer of the sessions from the old to the new)<br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">  </pre>
  <blockquote type="cite">
    <pre wrap="">3) It would appear that there is a linear relationship between the 
number of packets required for the fail over and the number of 
established sessions.   This would seem to present issues 
with scalability.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The behavior of the graceful restart proposal is not worse then normal start
of 
L2TPv3 (since the mechanism of the graceful and non graceful restart are
practically the same). 
If there is scalability issue in this proposal it is inherit to the whole
L2TP model and not restricted to 
the proposed graceful restart

  </pre>
</blockquote>
[pwh] IMHO, there is a scability problem that needs to be addressed.&nbsp;&nbsp;&nbsp;
When a failover occurs, the failed endpoint is in the process of trying
to recover it's state not only for L2TP, but for all other applications
running in the failed endpoint (e.g. IP, BGP, PPP, AAA, etc.).&nbsp;&nbsp; It is
a time of maximum stress on the failed endpoint coupled with
restrictive time limits (e.g. BGP neighbor notifications).&nbsp;&nbsp; Failover
processes needs to be designed with minimal resource consumption.&nbsp;&nbsp;&nbsp;
This draft proposes 'n' packets to be sent from the failed endpoint to
the non-failed endpoint where 'n' is the number of sessions between the
2 endpoints.&nbsp;&nbsp; This results in 10's of thousands if not 100's of
thousands of packets to complete the recovery.&nbsp;&nbsp;&nbsp; In order to avoid
this issue, it would seem that the session recovery needs to be able to
recover by packing multiple session recoveries per packet - thus
reducing to n/m packets where m is the number of recoveries per
packet.&nbsp;&nbsp; As the primary recovery requirement for the session is to
confirm that both endpoints believe the session to be in established
state, this could reduce to sending the session id's of the established
sessions from the failed endpoint to the non-failed endpoint followed
by the non-failed endpoint sending back the session ids of the
established sessions based on the intersection of what it received from
the failed endpoint and it's local database.&nbsp;&nbsp; Assuming say 256 session
ids packed in a single packet (1K of data), then we end up with 2 * n /
256 packets to recover.&nbsp;&nbsp; Thus with 100,000 sessions only 782 packets
are required to recover instead of 100,000+ packets.&nbsp;&nbsp; <br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">  </pre>
  <blockquote type="cite">
    <pre wrap="">Thanx,

Paul Howard

W. Mark Townsley wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">I would like to ask that interested parties review the 
      </pre>
    </blockquote>
    <pre wrap="">following draft 
    </pre>
    <blockquote type="cite">
      <pre wrap="">"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
provide comments to the list. This draft was originally 
      </pre>
    </blockquote>
    <pre wrap="">presented in 
    </pre>
    <blockquote type="cite">
      <pre wrap="">Vienna, and updated based on comments during the meeting.

<a class="moz-txt-link-freetext"
 href="http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt">http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt</a>

The authors would like to make this a WG document.

Thanks,

- Mark


_______________________________________________
L2tpext mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</a>
<a class="moz-txt-link-freetext"
 href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</a>

      </pre>
    </blockquote>
    <pre wrap="">_______________________________________________
L2tpext mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</a>
<a class="moz-txt-link-freetext"
 href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--------------070109090105070106030900--



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


From exim@www1.ietf.org  Wed Jan 14 14:29:49 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04594
	for <l2tpext-archive@odin.ietf.org>; Wed, 14 Jan 2004 14:29:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agqhd-0002FF-Cz
	for l2tpext-archive@odin.ietf.org; Wed, 14 Jan 2004 14:29:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0EJTLdd008630
	for l2tpext-archive@odin.ietf.org; Wed, 14 Jan 2004 14:29:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Agqhd-0002F7-66
	for l2tpext-web-archive@optimus.ietf.org; Wed, 14 Jan 2004 14:29:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04578
	for <l2tpext-web-archive@ietf.org>; Wed, 14 Jan 2004 14:29:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Agqha-0003pL-00
	for l2tpext-web-archive@ietf.org; Wed, 14 Jan 2004 14:29:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgqgF-0003nR-00
	for l2tpext-web-archive@ietf.org; Wed, 14 Jan 2004 14:27:57 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqfT-0003lq-00
	for l2tpext-web-archive@ietf.org; Wed, 14 Jan 2004 14:27:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgqfM-00027v-6w; Wed, 14 Jan 2004 14:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgqfI-00027V-3s
	for l2tpext@optimus.ietf.org; Wed, 14 Jan 2004 14:26:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04461
	for <l2tpext@ietf.org>; Wed, 14 Jan 2004 14:26:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqfF-0003kj-00
	for l2tpext@ietf.org; Wed, 14 Jan 2004 14:26:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgqeM-0003jA-00
	for l2tpext@ietf.org; Wed, 14 Jan 2004 14:26:00 -0500
Received: from natint2.juniper.net ([207.17.136.150] helo=gamma.jnpr.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgqdU-0003en-00
	for l2tpext@ietf.org; Wed, 14 Jan 2004 14:25:04 -0500
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by gamma.jnpr.net with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 14 Jan 2004 11:24:33 -0800
Received: from juniper.net ([10.10.248.146] RDNS failed) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 14 Jan 2004 14:24:32 -0500
Message-ID: <40059772.60607@juniper.net>
Date: Wed, 14 Jan 2004 14:24:34 -0500
From: "Paul W. Howard" <phoward@juniper.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sharon Galtzur <sharon@AXERRA.com>
CC: "W. Mark Townsley" <townsley@cisco.com>, l2tpext@ietf.org
Subject: Re: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
References: <AF5018AC03D1D411ABB70002A509132601085FEA@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A509132601085FEA@TLV1>
Content-Type: multipart/alternative;
 boundary="------------070109090105070106030900"
X-OriginalArrivalTime: 14 Jan 2004 19:24:32.0144 (UTC) FILETIME=[095BD100:01C3DAD4]
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_MESSAGE,
	HTML_TITLE_EMPTY autolearn=no version=2.60

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

Sharon,

Thanx for your responses.   Please see further comments inline ([pwh])

Thanx,

Paul Howard

Sharon Galtzur wrote:

>Hello all,
>See my response in the mail body.
>
>Sharon Galtzur
>
>  
>
>>-----Original Message-----
>>From: Paul W. Howard [mailto:phoward@juniper.net]
>>Sent: Friday, January 09, 2004 4:59 PM
>>To: W. Mark Townsley
>>Cc: l2tpext@ietf.org
>>Subject: Re: [L2tpext] Please comment on 
>>draft-galtzur-l2tpext-gr-01.txt
>>
>>
>>I have a few questions/concerns in regards to this draft:
>>
>>1) This proposal presents what appears to be an entirely different 
>>mechanism than that proposed in the v2 draft 
>>(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
>>important 
>>that we attempt to have a single mechanism for both v2 and v3 
>>or to at 
>>least minimize the differences to those that are unavoidable.
>>    
>>
>
>In LDP there is exactly the same occurrence - 
>RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
>RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 
>
>This draft follows the model presented in RFC 3478 with adaptation to L2TPv3
>  
>
[pwh] My understanding is that 3478 and 3479 present signficantly 
different approaches to the problem of dealing with a failed endpoint - 
3478 recovers by learning from the non-failed endpoint (graceful 
restart) whereas 3479 recovers by state replication on the failed 
endpoint.    Both your draft and Vipin's would seem to fall into the 
category of graceful restart (i.e. learning from the non-failed 
endpoint).   Both of the l2tp drafts deal with trying to recover key 
pieces of the control plane that are not normally obtainable from the 
forwarding database - the sequence numbers of the control connection and 
the state (established or non-established) of each of the sessions.   It 
would thus seem reasonable to resolve the differences between these 
drafts and produce as common an approach as possible to graceful restart.

[pwh] btw - I misquoted the current version of the other draft - it's 
draft-ietf-l2tpext-failover-02.txt

>  
>
>>2) I don't understand the basic reset of the sequence number 
>>space for 
>>the control connection.   Is this setting up a replacement tunnel or 
>>attempting to reset the sequence numbers of the extant tunnel?
>>    
>>
>
>The tunnel is restarted almost exactly as in
>draft-ietf-l2tpext-l2tp-base-11.txt
>One technical difference is the added AVP to advertise the graceful restart
>capability.
>Another difference is that while restarting the sessions certain information
>need 
>to endure the restart (i.e. Session ID, Cookie value etc) that will allow
>the data path
>to continue without interruptions.
>
[pwh] I'm not entirely clear on your answer.   There would seem to be 
two basic approaches to recovery of the control connection - one is to 
establish an entirely new control connection and eventually transfer the 
sessions from the old control connection to the new control connection; 
the other is to reset the extant control connection,   It's not clear to 
me from your answer or the draft which direction you are proposing.   
So, when I attempt to restart a control connection by sending an SCCRQ 
with the GR AVP and a non-zero recovery time, what is the value of the 
Assigned Control Connection Id AVP?  Is it the same as the one from the 
initial establishment (implies reset of the extant control connection) 
or a new value (implies a recovery control connection and transfer of 
the sessions from the old to the new)

>  
>
>>3) It would appear that there is a linear relationship between the 
>>number of packets required for the fail over and the number of 
>>established sessions.   This would seem to present issues 
>>with scalability.
>>    
>>
>
>The behavior of the graceful restart proposal is not worse then normal start
>of 
>L2TPv3 (since the mechanism of the graceful and non graceful restart are
>practically the same). 
>If there is scalability issue in this proposal it is inherit to the whole
>L2TP model and not restricted to 
>the proposed graceful restart
>
>  
>
[pwh] IMHO, there is a scability problem that needs to be addressed.    
When a failover occurs, the failed endpoint is in the process of trying 
to recover it's state not only for L2TP, but for all other applications 
running in the failed endpoint (e.g. IP, BGP, PPP, AAA, etc.).   It is a 
time of maximum stress on the failed endpoint coupled with restrictive 
time limits (e.g. BGP neighbor notifications).   Failover processes 
needs to be designed with minimal resource consumption.    This draft 
proposes 'n' packets to be sent from the failed endpoint to the 
non-failed endpoint where 'n' is the number of sessions between the 2 
endpoints.   This results in 10's of thousands if not 100's of thousands 
of packets to complete the recovery.    In order to avoid this issue, it 
would seem that the session recovery needs to be able to recover by 
packing multiple session recoveries per packet - thus reducing to n/m 
packets where m is the number of recoveries per packet.   As the primary 
recovery requirement for the session is to confirm that both endpoints 
believe the session to be in established state, this could reduce to 
sending the session id's of the established sessions from the failed 
endpoint to the non-failed endpoint followed by the non-failed endpoint 
sending back the session ids of the established sessions based on the 
intersection of what it received from the failed endpoint and it's local 
database.   Assuming say 256 session ids packed in a single packet (1K 
of data), then we end up with 2 * n / 256 packets to recover.   Thus 
with 100,000 sessions only 782 packets are required to recover instead 
of 100,000+ packets.  

>  
>
>>Thanx,
>>
>>Paul Howard
>>
>>W. Mark Townsley wrote:
>>
>>    
>>
>>>I would like to ask that interested parties review the 
>>>      
>>>
>>following draft 
>>    
>>
>>>"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
>>>provide comments to the list. This draft was originally 
>>>      
>>>
>>presented in 
>>    
>>
>>>Vienna, and updated based on comments during the meeting.
>>>
>>>http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
>>>
>>>The authors would like to make this a WG document.
>>>
>>>Thanks,
>>>
>>>- Mark
>>>
>>>
>>>_______________________________________________
>>>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
>>
>>    
>>
>
>  
>

--------------070109090105070106030900
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
Sharon,<br>
<br>
Thanx for your responses.&nbsp;&nbsp; Please see further comments inline ([pwh])<br>
<br>
Thanx,<br>
<br>
Paul Howard<br>
<br>
Sharon Galtzur wrote:<br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">Hello all,
See my response in the mail body.

Sharon Galtzur

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: Paul W. Howard [<a
 class="moz-txt-link-freetext" href="mailto:phoward@juniper.net">mailto:phoward@juniper.net</a>]
Sent: Friday, January 09, 2004 4:59 PM
To: W. Mark Townsley
Cc: <a
 class="moz-txt-link-abbreviated" href="mailto:l2tpext@ietf.org">l2tpext@ietf.org</a>
Subject: Re: [L2tpext] Please comment on 
draft-galtzur-l2tpext-gr-01.txt


I have a few questions/concerns in regards to this draft:

1) This proposal presents what appears to be an entirely different 
mechanism than that proposed in the v2 draft 
(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
important 
that we attempt to have a single mechanism for both v2 and v3 
or to at 
least minimize the differences to those that are unavoidable.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
In LDP there is exactly the same occurrence - 
RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 

This draft follows the model presented in RFC 3478 with adaptation to L2TPv3
  </pre>
</blockquote>
[pwh] My understanding is that 3478 and 3479 present signficantly
different approaches to the problem of dealing with a failed endpoint -
3478 recovers by learning from the non-failed endpoint (graceful
restart) whereas 3479 recovers by state replication on the failed
endpoint.&nbsp;&nbsp;&nbsp; Both your draft and Vipin's would seem to fall into the
category of graceful restart (i.e. learning from the non-failed
endpoint).&nbsp;&nbsp; Both of the l2tp drafts deal with trying to recover key
pieces of the control plane that are not normally obtainable from the
forwarding database - the sequence numbers of the control connection
and the state (established or non-established) of each of the
sessions.&nbsp;&nbsp; It would thus seem reasonable to resolve the differences
between these drafts and produce as common an approach as possible to
graceful restart.<br>
<br>
[pwh] btw - I misquoted the current version of the other draft - it's
draft-ietf-l2tpext-failover-02.txt<br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">  </pre>
  <blockquote type="cite">
    <pre wrap="">2) I don't understand the basic reset of the sequence number 
space for 
the control connection.   Is this setting up a replacement tunnel or 
attempting to reset the sequence numbers of the extant tunnel?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The tunnel is restarted almost exactly as in
draft-ietf-l2tpext-l2tp-base-11.txt
One technical difference is the added AVP to advertise the graceful restart
capability.
Another difference is that while restarting the sessions certain information
need 
to endure the restart (i.e. Session ID, Cookie value etc) that will allow
the data path
to continue without interruptions.</pre>
</blockquote>
[pwh] I'm not entirely clear on your answer.&nbsp;&nbsp; There would seem to be
two basic approaches to recovery of the control connection - one is to
establish an entirely new control connection and eventually transfer
the sessions from the old control connection to the new control
connection; the other is to reset the extant control connection,&nbsp;&nbsp; It's
not clear to me from your answer or the draft which direction you are
proposing.&nbsp;&nbsp; So, when I attempt to restart a control connection by
sending an SCCRQ with the GR AVP and a non-zero recovery time, what is
the value of the Assigned Control Connection Id AVP?&nbsp; Is it the same as
the one from the initial establishment (implies reset of the extant
control connection) or a new value (implies a recovery control
connection and transfer of the sessions from the old to the new)<br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">  </pre>
  <blockquote type="cite">
    <pre wrap="">3) It would appear that there is a linear relationship between the 
number of packets required for the fail over and the number of 
established sessions.   This would seem to present issues 
with scalability.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The behavior of the graceful restart proposal is not worse then normal start
of 
L2TPv3 (since the mechanism of the graceful and non graceful restart are
practically the same). 
If there is scalability issue in this proposal it is inherit to the whole
L2TP model and not restricted to 
the proposed graceful restart

  </pre>
</blockquote>
[pwh] IMHO, there is a scability problem that needs to be addressed.&nbsp;&nbsp;&nbsp;
When a failover occurs, the failed endpoint is in the process of trying
to recover it's state not only for L2TP, but for all other applications
running in the failed endpoint (e.g. IP, BGP, PPP, AAA, etc.).&nbsp;&nbsp; It is
a time of maximum stress on the failed endpoint coupled with
restrictive time limits (e.g. BGP neighbor notifications).&nbsp;&nbsp; Failover
processes needs to be designed with minimal resource consumption.&nbsp;&nbsp;&nbsp;
This draft proposes 'n' packets to be sent from the failed endpoint to
the non-failed endpoint where 'n' is the number of sessions between the
2 endpoints.&nbsp;&nbsp; This results in 10's of thousands if not 100's of
thousands of packets to complete the recovery.&nbsp;&nbsp;&nbsp; In order to avoid
this issue, it would seem that the session recovery needs to be able to
recover by packing multiple session recoveries per packet - thus
reducing to n/m packets where m is the number of recoveries per
packet.&nbsp;&nbsp; As the primary recovery requirement for the session is to
confirm that both endpoints believe the session to be in established
state, this could reduce to sending the session id's of the established
sessions from the failed endpoint to the non-failed endpoint followed
by the non-failed endpoint sending back the session ids of the
established sessions based on the intersection of what it received from
the failed endpoint and it's local database.&nbsp;&nbsp; Assuming say 256 session
ids packed in a single packet (1K of data), then we end up with 2 * n /
256 packets to recover.&nbsp;&nbsp; Thus with 100,000 sessions only 782 packets
are required to recover instead of 100,000+ packets.&nbsp;&nbsp; <br>
<blockquote type="cite"
 cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1">
  <pre wrap="">  </pre>
  <blockquote type="cite">
    <pre wrap="">Thanx,

Paul Howard

W. Mark Townsley wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">I would like to ask that interested parties review the 
      </pre>
    </blockquote>
    <pre wrap="">following draft 
    </pre>
    <blockquote type="cite">
      <pre wrap="">"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
provide comments to the list. This draft was originally 
      </pre>
    </blockquote>
    <pre wrap="">presented in 
    </pre>
    <blockquote type="cite">
      <pre wrap="">Vienna, and updated based on comments during the meeting.

<a class="moz-txt-link-freetext"
 href="http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt">http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt</a>

The authors would like to make this a WG document.

Thanks,

- Mark


_______________________________________________
L2tpext mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</a>
<a class="moz-txt-link-freetext"
 href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</a>

      </pre>
    </blockquote>
    <pre wrap="">_______________________________________________
L2tpext mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</a>
<a class="moz-txt-link-freetext"
 href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--------------070109090105070106030900--



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



From l2tpext-admin@ietf.org  Wed Jan 21 09:44:35 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23950
	for <l2tpext-archive@lists.ietf.org>; Wed, 21 Jan 2004 09:44:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjJaK-00076M-Jr; Wed, 21 Jan 2004 09:44:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjJZZ-00074E-TH
	for l2tpext@optimus.ietf.org; Wed, 21 Jan 2004 09:43:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23895
	for <l2tpext@ietf.org>; Wed, 21 Jan 2004 09:43:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjJZY-0001mG-00
	for l2tpext@ietf.org; Wed, 21 Jan 2004 09:43:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjJYU-0001j1-00
	for l2tpext@ietf.org; Wed, 21 Jan 2004 09:42:09 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AjJXT-0001V3-00
	for l2tpext@ietf.org; Wed, 21 Jan 2004 09:41:04 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Wed, 21 Jan 2004 16:07:34 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <DLZ5B6MD>; Wed, 21 Jan 2004 16:06:06 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085FED@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'Paul W. Howard'" <phoward@juniper.net>
Cc: "W. Mark Townsley" <townsley@cisco.com>, l2tpext@ietf.org
Subject: RE: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
Date: Wed, 21 Jan 2004 16:06:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-e67da9d1-cea2-410d-a8e5-5f1baa7c3116"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY,MIME_BOUND_NEXTPART 
	autolearn=no version=2.60
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.

------=_NextPartTM-000-e67da9d1-cea2-410d-a8e5-5f1baa7c3116
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3E027.B429F1E0"

------_=_NextPart_001_01C3E027.B429F1E0
Content-Type: text/plain;
	charset="ISO-8859-8"

Hello Paul and all,
See my comments inline
 
Sharon Galtzur
 

-----Original Message-----
From: Paul W. Howard [mailto:phoward@juniper.net]
Sent: Wednesday, January 14, 2004 9:25 PM
To: Sharon Galtzur
Cc: W. Mark Townsley; l2tpext@ietf.org
Subject: Re: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt


Sharon,

Thanx for your responses.   Please see further comments inline ([pwh])

Thanx,

Paul Howard

Sharon Galtzur wrote:


Hello all,

See my response in the mail body.



Sharon Galtzur



  

-----Original Message-----

From: Paul W. Howard [ mailto:phoward@juniper.net
<mailto:phoward@juniper.net> ]

Sent: Friday, January 09, 2004 4:59 PM

To: W. Mark Townsley

Cc:  l2tpext@ietf.org <mailto:l2tpext@ietf.org> 

Subject: Re: [L2tpext] Please comment on 

draft-galtzur-l2tpext-gr-01.txt





I have a few questions/concerns in regards to this draft:



1) This proposal presents what appears to be an entirely different 

mechanism than that proposed in the v2 draft 

(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 

important 

that we attempt to have a single mechanism for both v2 and v3 

or to at 

least minimize the differences to those that are unavoidable.

    



In LDP there is exactly the same occurrence - 

RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 

RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 



This draft follows the model presented in RFC 3478 with adaptation to L2TPv3

  

[pwh] My understanding is that 3478 and 3479 present signficantly different
approaches to the problem of dealing with a failed endpoint - 3478 recovers
by learning from the non-failed endpoint (graceful restart) whereas 3479
recovers by state replication on the failed endpoint.    Both your draft and
Vipin's would seem to fall into the category of graceful restart (i.e.
learning from the non-failed endpoint).   Both of the l2tp drafts deal with
trying to recover key pieces of the control plane that are not normally
obtainable from the forwarding database - the sequence numbers of the
control connection and the state (established or non-established) of each of
the sessions.   It would thus seem reasonable to resolve the differences
between these drafts and produce as common an approach as possible to
graceful restart.

[pwh] btw - I misquoted the current version of the other draft - it's
draft-ietf-l2tpext-failover-02.txt


  

2) I don't understand the basic reset of the sequence number 

space for 

the control connection.   Is this setting up a replacement tunnel or 

attempting to reset the sequence numbers of the extant tunnel?

    



The tunnel is restarted almost exactly as in

draft-ietf-l2tpext-l2tp-base-11.txt

One technical difference is the added AVP to advertise the graceful restart

capability.

Another difference is that while restarting the sessions certain information

need 

to endure the restart (i.e. Session ID, Cookie value etc) that will allow

the data path

to continue without interruptions.

[pwh] I'm not entirely clear on your answer.   There would seem to be two
basic approaches to recovery of the control connection - one is to establish
an entirely new control connection and eventually transfer the sessions from
the old control connection to the new control connection; the other is to
reset the extant control connection,   It's not clear to me from your answer
or the draft which direction you are proposing.   So, when I attempt to
restart a control connection by sending an SCCRQ with the GR AVP and a
non-zero recovery time, what is the value of the Assigned Control Connection
Id AVP?  Is it the same as the one from the initial establishment (implies
reset of the extant control connection) or a new value (implies a recovery
control connection and transfer of the sessions from the old to the new)
 
[Sharon Galtzur] I agree this is indeed missing from the draft - 
The pro and con of each approach are as follow: 
1. If we remember the the CC ID - we gain a bit more confidence when we
looking up the CC in the LCCE that wasn't restart, because we have more
information
    to compare to when recovering the CC. The drawback is that the restarted
LCCE must have the means to remember this information (since this
information is NOT 
    a part of the data path and hence is not transferred to the data path
parts of the system). 
2. If we don't remember the CC ID - we lose some confidence when we looking
up the CC (but really not more then when doing normal restart). The gain is
that there is 
    no need for this information to be persistent.
 
Currently I would think that not remembering the CC ID from restart to
restart is preferred because it is less restrictive and is more close to the
non-graceful restart requirements. 
 
I would like to hear from others what they think before I update the draft.
 
 


  

3) It would appear that there is a linear relationship between the 

number of packets required for the fail over and the number of 

established sessions.   This would seem to present issues 

with scalability.

    



The behavior of the graceful restart proposal is not worse then normal start

of 

L2TPv3 (since the mechanism of the graceful and non graceful restart are

practically the same). 

If there is scalability issue in this proposal it is inherit to the whole

L2TP model and not restricted to 

the proposed graceful restart



  

[pwh] IMHO, there is a scability problem that needs to be addressed.    When
a failover occurs, the failed endpoint is in the process of trying to
recover it's state not only for L2TP, but for all other applications running
in the failed endpoint (e.g. IP, BGP, PPP, AAA, etc.).   It is a time of
maximum stress on the failed endpoint coupled with restrictive time limits
(e.g. BGP neighbor notifications).   Failover processes needs to be designed
with minimal resource consumption.    This draft proposes 'n' packets to be
sent from the failed endpoint to the non-failed endpoint where 'n' is the
number of sessions between the 2 endpoints.   This results in 10's of
thousands if not 100's of thousands of packets to complete the recovery.
In order to avoid this issue, it would seem that the session recovery needs
to be able to recover by packing multiple session recoveries per packet -
thus reducing to n/m packets where m is the number of recoveries per packet.
As the primary recovery requirement for the session is to confirm that both
endpoints believe the session to be in established state, this could reduce
to sending the session id's of the established sessions from the failed
endpoint to the non-failed endpoint followed by the non-failed endpoint
sending back the session ids of the established sessions based on the
intersection of what it received from the failed endpoint and it's local
database.   Assuming say 256 session ids packed in a single packet (1K of
data), then we end up with 2 * n / 256 packets to recover.   Thus with
100,000 sessions only 782 packets are required to recover instead of
100,000+ packets.  
  
[Sharon Galtzur] The same can be said for the current L2TP non-graceful
restart. It is probably even more pressing since there is no data flow till
the connections are 
restarted. The big advantage I see in this approach is that it is so similar
to normal L2TP model. This will allow implementers of L2TP stacks to
implement one model of establishing sessions instead of 2. 
I would suggest that if there is a real concern of connecting 100k
connection between 2 LCCE we should re-examine the possibility of
establishing multiple sessions connection using 1 packet instead of
requiring 1 packet per session in the non-graceful restart and then adopt it
to the graceful restart mode. 
 


  

Thanx,



Paul Howard



W. Mark Townsley wrote:



    

I would like to ask that interested parties review the 

      

following draft 

    

"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 

provide comments to the list. This draft was originally 

      

presented in 

    

Vienna, and updated based on comments during the meeting.



http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
<http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt> 



The authors would like to make this a WG document.



Thanks,



- Mark





_______________________________________________

L2tpext mailing list

L2tpext@ietf.org <mailto:L2tpext@ietf.org> 

https://www1.ietf.org/mailman/listinfo/l2tpext
<https://www1.ietf.org/mailman/listinfo/l2tpext> 



      

_______________________________________________

L2tpext mailing list

L2tpext@ietf.org <mailto:L2tpext@ietf.org> 

https://www1.ietf.org/mailman/listinfo/l2tpext
<https://www1.ietf.org/mailman/listinfo/l2tpext> 



    



  


------_=_NextPart_001_01C3E027.B429F1E0
Content-Type: text/html;
	charset="ISO-8859-8"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-8">
<TITLE></TITLE>

<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=245563909-21012004>Hello 
Paul<SPAN class=901140614-21012004> and all</SPAN>,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=245563909-21012004>See my 
comments inline</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=245563909-21012004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=245563909-21012004>Sharon 
Galtzur</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Paul W. Howard 
  [mailto:phoward@juniper.net]<BR><B>Sent:</B> Wednesday, January 14, 2004 9:25 
  PM<BR><B>To:</B> Sharon Galtzur<BR><B>Cc:</B> W. Mark Townsley; 
  l2tpext@ietf.org<BR><B>Subject:</B> Re: [L2tpext] Please comment on 
  draft-galtzur-l2tpext-gr-01.txt<BR><BR></FONT></DIV>Sharon,<BR><BR>Thanx for 
  your responses.&nbsp;&nbsp; Please see further comments inline 
  ([pwh])<BR><BR>Thanx,<BR><BR>Paul Howard<BR><BR>Sharon Galtzur wrote:<BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">Hello all,
See my response in the mail body.

Sharon Galtzur

  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">-----Original Message-----
From: Paul W. Howard [<A class=moz-txt-link-freetext href="mailto:phoward@juniper.net">mailto:phoward@juniper.net</A>]
Sent: Friday, January 09, 2004 4:59 PM
To: W. Mark Townsley
Cc: <A class=moz-txt-link-abbreviated href="mailto:l2tpext@ietf.org">l2tpext@ietf.org</A>
Subject: Re: [L2tpext] Please comment on 
draft-galtzur-l2tpext-gr-01.txt


I have a few questions/concerns in regards to this draft:

1) This proposal presents what appears to be an entirely different 
mechanism than that proposed in the v2 draft 
(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
important 
that we attempt to have a single mechanism for both v2 and v3 
or to at 
least minimize the differences to those that are unavoidable.
    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
In LDP there is exactly the same occurrence - 
RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 

This draft follows the model presented in RFC 3478 with adaptation to L2TPv3
  </PRE></BLOCKQUOTE>[pwh] My understanding is that 3478 and 3479 present 
  signficantly different approaches to the problem of dealing with a failed 
  endpoint - 3478 recovers by learning from the non-failed endpoint (graceful 
  restart) whereas 3479 recovers by state replication on the failed 
  endpoint.&nbsp;&nbsp;&nbsp; Both your draft and Vipin's would seem to fall 
  into the category of graceful restart (i.e. learning from the non-failed 
  endpoint).&nbsp;&nbsp; Both of the l2tp drafts deal with trying to recover key 
  pieces of the control plane that are not normally obtainable from the 
  forwarding database - the sequence numbers of the control connection and the 
  state (established or non-established) of each of the sessions.&nbsp;&nbsp; It 
  would thus seem reasonable to resolve the differences between these drafts and 
  produce as common an approach as possible to graceful restart.<BR><BR>[pwh] 
  btw - I misquoted the current version of the other draft - it's 
  draft-ietf-l2tpext-failover-02.txt<BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">2) I don't understand the basic reset of the sequence number 
space for 
the control connection.   Is this setting up a replacement tunnel or 
attempting to reset the sequence numbers of the extant tunnel?
    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
The tunnel is restarted almost exactly as in
draft-ietf-l2tpext-l2tp-base-11.txt
One technical difference is the added AVP to advertise the graceful restart
capability.
Another difference is that while restarting the sessions certain information
need 
to endure the restart (i.e. Session ID, Cookie value etc) that will allow
the data path
to continue without interruptions.</PRE></BLOCKQUOTE>[pwh] I'm not entirely 
  clear on your answer.&nbsp;&nbsp; There would seem to be two basic approaches 
  to recovery of the control connection - one is to establish an entirely new 
  control connection and eventually transfer the sessions from the old control 
  connection to the new control connection; the other is to reset the extant 
  control connection,&nbsp;&nbsp; It's not clear to me from your answer or the 
  draft which direction you are proposing.&nbsp;&nbsp; So, when I attempt to 
  restart a control connection by sending an SCCRQ with the GR AVP and a 
  non-zero recovery time, what is the value of the Assigned Control Connection 
  Id AVP?&nbsp; Is it the same as the one from the initial establishment 
  (implies reset of the extant control connection) or a new value (implies a 
  recovery control connection and transfer of the sessions from the old to the 
  new)<BR><SPAN class=901140614-21012004><FONT face=Arial color=#0000ff 
  size=2>&nbsp;</FONT></SPAN><BR><SPAN class=901140614-21012004><FONT face=Arial 
  color=#0000ff size=2><SPAN class=245563909-21012004>[Sharon Galtzur]&nbsp;I 
  agree this is indeed missing from the draft - </SPAN>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>The pro and con of each approach are as follow: 
  </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>1. If we remember the the CC ID - we gain a bit more 
  confidence when we looking up the CC in the LCCE that wasn't restart, because 
  we have more information</FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>&nbsp;&nbsp;&nbsp; to compare to when recovering the CC. 
  The drawback is that the restarted LCCE must have the means to remember this 
  information (since this information is NOT </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>&nbsp;&nbsp;&nbsp; a part of the data path and hence is 
  not transferred to the data path parts of the system). </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>2. If we don't remember the CC ID - we lose some 
  confidence when we looking up the CC (but really not more then when doing 
  normal restart). The gain is that there is </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004>&nbsp;&nbsp;&nbsp; <FONT 
  face=Arial color=#0000ff size=2>no need for this information to be 
  persistent.</FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>Currently I would think that not remembering the CC ID 
  from restart to restart is preferred because it is less restrictive and is 
  more close to the non-graceful restart requirements. </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>I would like to hear from others what they think before I 
  update the draft.</FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>&nbsp;</FONT></SPAN><BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">3) It would appear that there is a linear relationship between the 
number of packets required for the fail over and the number of 
established sessions.   This would seem to present issues 
with scalability.
    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
The behavior of the graceful restart proposal is not worse then normal start
of 
L2TPv3 (since the mechanism of the graceful and non graceful restart are
practically the same). 
If there is scalability issue in this proposal it is inherit to the whole
L2TP model and not restricted to 
the proposed graceful restart

  </PRE></BLOCKQUOTE>[pwh] IMHO, there is a scability problem that needs to be 
  addressed.&nbsp;&nbsp;&nbsp; When a failover occurs, the failed endpoint is in 
  the process of trying to recover it's state not only for L2TP, but for all 
  other applications running in the failed endpoint (e.g. IP, BGP, PPP, AAA, 
  etc.).&nbsp;&nbsp; It is a time of maximum stress on the failed endpoint 
  coupled with restrictive time limits (e.g. BGP neighbor 
  notifications).&nbsp;&nbsp; Failover processes needs to be designed with 
  minimal resource consumption.&nbsp;&nbsp;&nbsp; This draft proposes 'n' 
  packets to be sent from the failed endpoint to the non-failed endpoint where 
  'n' is the number of sessions between the 2 endpoints.&nbsp;&nbsp; This 
  results in 10's of thousands if not 100's of thousands of packets to complete 
  the recovery.&nbsp;&nbsp;&nbsp; In order to avoid this issue, it would seem 
  that the session recovery needs to be able to recover by packing multiple 
  session recoveries per packet - thus reducing to n/m packets where m is the 
  number of recoveries per packet.&nbsp;&nbsp; As the primary recovery 
  requirement for the session is to confirm that both endpoints believe the 
  session to be in established state, this could reduce to sending the session 
  id's of the established sessions from the failed endpoint to the non-failed 
  endpoint followed by the non-failed endpoint sending back the session ids of 
  the established sessions based on the intersection of what it received from 
  the failed endpoint and it's local database.&nbsp;&nbsp; Assuming say 256 
  session ids packed in a single packet (1K of data), then we end up with 2 * n 
  / 256 packets to recover.&nbsp;&nbsp; Thus with 100,000 sessions only 782 
  packets are required to recover instead of 100,000+ 
  packets.&nbsp;&nbsp;<BR><SPAN class=901140614-21012004><FONT face=Arial 
  color=#0000ff size=2>&nbsp;</FONT></SPAN>&nbsp;<BR><SPAN 
  class=901140614-21012004><FONT face=Arial color=#0000ff size=2><SPAN 
  class=245563909-21012004>[Sharon Galtzur]&nbsp;The same can&nbsp;be said for 
  the current L2TP non-graceful restart. It is probably even more pressing since 
  there is no data flow till the connections are </SPAN>
  <DIV dir=ltr wrap=""><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN 
  class=245563909-21012004>restarted. The big advantage I see in this approach 
  is that it is so similar to normal L2TP model. This will allow implementers of 
  L2TP stacks to implement one model of establishing sessions instead of 2. 
  </SPAN></FONT></FONT></FONT></DIV>
  <DIV dir=ltr wrap=""><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN 
  class=245563909-21012004>I would suggest that if there is&nbsp;a real concern 
  of connecting 100k connection between 2 LCCE we should re-examine the 
  possibility of establishing multiple sessions connection using 1 packet 
  instead of requiring 1 packet per session in the non-graceful restart and then 
  adopt it to the graceful restart mode. 
  </SPAN></FONT></FONT></FONT></DIV>&nbsp;</FONT></SPAN><BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">Thanx,

Paul Howard

W. Mark Townsley wrote:

    </PRE>
      <BLOCKQUOTE type="cite"><PRE wrap="">I would like to ask that interested parties review the 
      </PRE></BLOCKQUOTE><PRE wrap="">following draft 
    </PRE>
      <BLOCKQUOTE type="cite"><PRE wrap="">"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
provide comments to the list. This draft was originally 
      </PRE></BLOCKQUOTE><PRE wrap="">presented in 
    </PRE>
      <BLOCKQUOTE type="cite"><PRE wrap="">Vienna, and updated based on comments during the meeting.

<A class=moz-txt-link-freetext href="http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt">http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt</A>

The authors would like to make this a WG document.

Thanks,

- Mark


_______________________________________________
L2tpext mailing list
<A class=moz-txt-link-abbreviated href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</A>
<A class=moz-txt-link-freetext href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</A>

      </PRE></BLOCKQUOTE><PRE wrap="">_______________________________________________
L2tpext mailing list
<A class=moz-txt-link-abbreviated href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</A>
<A class=moz-txt-link-freetext href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</A>

    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
  </PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3E027.B429F1E0--

------=_NextPartTM-000-e67da9d1-cea2-410d-a8e5-5f1baa7c3116--


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


From exim@www1.ietf.org  Wed Jan 21 09:46:39 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24070
	for <l2tpext-archive@odin.ietf.org>; Wed, 21 Jan 2004 09:46:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjJcR-0007ES-HZ
	for l2tpext-archive@odin.ietf.org; Wed, 21 Jan 2004 09:46:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0LEkBSZ027796
	for l2tpext-archive@odin.ietf.org; Wed, 21 Jan 2004 09:46:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjJcR-0007EF-Dn
	for l2tpext-web-archive@optimus.ietf.org; Wed, 21 Jan 2004 09:46:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24015
	for <l2tpext-web-archive@ietf.org>; Wed, 21 Jan 2004 09:46:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjJcP-0001vm-00
	for l2tpext-web-archive@ietf.org; Wed, 21 Jan 2004 09:46:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjJbQ-0001sR-00
	for l2tpext-web-archive@ietf.org; Wed, 21 Jan 2004 09:45:10 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjJaX-0001qA-00
	for l2tpext-web-archive@ietf.org; Wed, 21 Jan 2004 09:44:13 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AjJaU-0006oz-PH
	for l2tpext-web-archive@ietf.org; Wed, 21 Jan 2004 09:44:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjJaK-00076M-Jr; Wed, 21 Jan 2004 09:44:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjJZZ-00074E-TH
	for l2tpext@optimus.ietf.org; Wed, 21 Jan 2004 09:43:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23895
	for <l2tpext@ietf.org>; Wed, 21 Jan 2004 09:43:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjJZY-0001mG-00
	for l2tpext@ietf.org; Wed, 21 Jan 2004 09:43:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjJYU-0001j1-00
	for l2tpext@ietf.org; Wed, 21 Jan 2004 09:42:09 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AjJXT-0001V3-00
	for l2tpext@ietf.org; Wed, 21 Jan 2004 09:41:04 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Wed, 21 Jan 2004 16:07:34 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <DLZ5B6MD>; Wed, 21 Jan 2004 16:06:06 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085FED@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'Paul W. Howard'" <phoward@juniper.net>
Cc: "W. Mark Townsley" <townsley@cisco.com>, l2tpext@ietf.org
Subject: RE: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt
Date: Wed, 21 Jan 2004 16:06:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-e67da9d1-cea2-410d-a8e5-5f1baa7c3116"
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE,HTML_TITLE_EMPTY,MIME_BOUND_NEXTPART 
	autolearn=no version=2.60

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.

------=_NextPartTM-000-e67da9d1-cea2-410d-a8e5-5f1baa7c3116
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3E027.B429F1E0"

------_=_NextPart_001_01C3E027.B429F1E0
Content-Type: text/plain;
	charset="ISO-8859-8"

Hello Paul and all,
See my comments inline
 
Sharon Galtzur
 

-----Original Message-----
From: Paul W. Howard [mailto:phoward@juniper.net]
Sent: Wednesday, January 14, 2004 9:25 PM
To: Sharon Galtzur
Cc: W. Mark Townsley; l2tpext@ietf.org
Subject: Re: [L2tpext] Please comment on draft-galtzur-l2tpext-gr-01.txt


Sharon,

Thanx for your responses.   Please see further comments inline ([pwh])

Thanx,

Paul Howard

Sharon Galtzur wrote:


Hello all,

See my response in the mail body.



Sharon Galtzur



  

-----Original Message-----

From: Paul W. Howard [ mailto:phoward@juniper.net
<mailto:phoward@juniper.net> ]

Sent: Friday, January 09, 2004 4:59 PM

To: W. Mark Townsley

Cc:  l2tpext@ietf.org <mailto:l2tpext@ietf.org> 

Subject: Re: [L2tpext] Please comment on 

draft-galtzur-l2tpext-gr-01.txt





I have a few questions/concerns in regards to this draft:



1) This proposal presents what appears to be an entirely different 

mechanism than that proposed in the v2 draft 

(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 

important 

that we attempt to have a single mechanism for both v2 and v3 

or to at 

least minimize the differences to those that are unavoidable.

    



In LDP there is exactly the same occurrence - 

RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 

RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 



This draft follows the model presented in RFC 3478 with adaptation to L2TPv3

  

[pwh] My understanding is that 3478 and 3479 present signficantly different
approaches to the problem of dealing with a failed endpoint - 3478 recovers
by learning from the non-failed endpoint (graceful restart) whereas 3479
recovers by state replication on the failed endpoint.    Both your draft and
Vipin's would seem to fall into the category of graceful restart (i.e.
learning from the non-failed endpoint).   Both of the l2tp drafts deal with
trying to recover key pieces of the control plane that are not normally
obtainable from the forwarding database - the sequence numbers of the
control connection and the state (established or non-established) of each of
the sessions.   It would thus seem reasonable to resolve the differences
between these drafts and produce as common an approach as possible to
graceful restart.

[pwh] btw - I misquoted the current version of the other draft - it's
draft-ietf-l2tpext-failover-02.txt


  

2) I don't understand the basic reset of the sequence number 

space for 

the control connection.   Is this setting up a replacement tunnel or 

attempting to reset the sequence numbers of the extant tunnel?

    



The tunnel is restarted almost exactly as in

draft-ietf-l2tpext-l2tp-base-11.txt

One technical difference is the added AVP to advertise the graceful restart

capability.

Another difference is that while restarting the sessions certain information

need 

to endure the restart (i.e. Session ID, Cookie value etc) that will allow

the data path

to continue without interruptions.

[pwh] I'm not entirely clear on your answer.   There would seem to be two
basic approaches to recovery of the control connection - one is to establish
an entirely new control connection and eventually transfer the sessions from
the old control connection to the new control connection; the other is to
reset the extant control connection,   It's not clear to me from your answer
or the draft which direction you are proposing.   So, when I attempt to
restart a control connection by sending an SCCRQ with the GR AVP and a
non-zero recovery time, what is the value of the Assigned Control Connection
Id AVP?  Is it the same as the one from the initial establishment (implies
reset of the extant control connection) or a new value (implies a recovery
control connection and transfer of the sessions from the old to the new)
 
[Sharon Galtzur] I agree this is indeed missing from the draft - 
The pro and con of each approach are as follow: 
1. If we remember the the CC ID - we gain a bit more confidence when we
looking up the CC in the LCCE that wasn't restart, because we have more
information
    to compare to when recovering the CC. The drawback is that the restarted
LCCE must have the means to remember this information (since this
information is NOT 
    a part of the data path and hence is not transferred to the data path
parts of the system). 
2. If we don't remember the CC ID - we lose some confidence when we looking
up the CC (but really not more then when doing normal restart). The gain is
that there is 
    no need for this information to be persistent.
 
Currently I would think that not remembering the CC ID from restart to
restart is preferred because it is less restrictive and is more close to the
non-graceful restart requirements. 
 
I would like to hear from others what they think before I update the draft.
 
 


  

3) It would appear that there is a linear relationship between the 

number of packets required for the fail over and the number of 

established sessions.   This would seem to present issues 

with scalability.

    



The behavior of the graceful restart proposal is not worse then normal start

of 

L2TPv3 (since the mechanism of the graceful and non graceful restart are

practically the same). 

If there is scalability issue in this proposal it is inherit to the whole

L2TP model and not restricted to 

the proposed graceful restart



  

[pwh] IMHO, there is a scability problem that needs to be addressed.    When
a failover occurs, the failed endpoint is in the process of trying to
recover it's state not only for L2TP, but for all other applications running
in the failed endpoint (e.g. IP, BGP, PPP, AAA, etc.).   It is a time of
maximum stress on the failed endpoint coupled with restrictive time limits
(e.g. BGP neighbor notifications).   Failover processes needs to be designed
with minimal resource consumption.    This draft proposes 'n' packets to be
sent from the failed endpoint to the non-failed endpoint where 'n' is the
number of sessions between the 2 endpoints.   This results in 10's of
thousands if not 100's of thousands of packets to complete the recovery.
In order to avoid this issue, it would seem that the session recovery needs
to be able to recover by packing multiple session recoveries per packet -
thus reducing to n/m packets where m is the number of recoveries per packet.
As the primary recovery requirement for the session is to confirm that both
endpoints believe the session to be in established state, this could reduce
to sending the session id's of the established sessions from the failed
endpoint to the non-failed endpoint followed by the non-failed endpoint
sending back the session ids of the established sessions based on the
intersection of what it received from the failed endpoint and it's local
database.   Assuming say 256 session ids packed in a single packet (1K of
data), then we end up with 2 * n / 256 packets to recover.   Thus with
100,000 sessions only 782 packets are required to recover instead of
100,000+ packets.  
  
[Sharon Galtzur] The same can be said for the current L2TP non-graceful
restart. It is probably even more pressing since there is no data flow till
the connections are 
restarted. The big advantage I see in this approach is that it is so similar
to normal L2TP model. This will allow implementers of L2TP stacks to
implement one model of establishing sessions instead of 2. 
I would suggest that if there is a real concern of connecting 100k
connection between 2 LCCE we should re-examine the possibility of
establishing multiple sessions connection using 1 packet instead of
requiring 1 packet per session in the non-graceful restart and then adopt it
to the graceful restart mode. 
 


  

Thanx,



Paul Howard



W. Mark Townsley wrote:



    

I would like to ask that interested parties review the 

      

following draft 

    

"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 

provide comments to the list. This draft was originally 

      

presented in 

    

Vienna, and updated based on comments during the meeting.



http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt
<http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt> 



The authors would like to make this a WG document.



Thanks,



- Mark





_______________________________________________

L2tpext mailing list

L2tpext@ietf.org <mailto:L2tpext@ietf.org> 

https://www1.ietf.org/mailman/listinfo/l2tpext
<https://www1.ietf.org/mailman/listinfo/l2tpext> 



      

_______________________________________________

L2tpext mailing list

L2tpext@ietf.org <mailto:L2tpext@ietf.org> 

https://www1.ietf.org/mailman/listinfo/l2tpext
<https://www1.ietf.org/mailman/listinfo/l2tpext> 



    



  


------_=_NextPart_001_01C3E027.B429F1E0
Content-Type: text/html;
	charset="ISO-8859-8"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-8">
<TITLE></TITLE>

<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=245563909-21012004>Hello 
Paul<SPAN class=901140614-21012004> and all</SPAN>,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=245563909-21012004>See my 
comments inline</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=245563909-21012004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=245563909-21012004>Sharon 
Galtzur</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Paul W. Howard 
  [mailto:phoward@juniper.net]<BR><B>Sent:</B> Wednesday, January 14, 2004 9:25 
  PM<BR><B>To:</B> Sharon Galtzur<BR><B>Cc:</B> W. Mark Townsley; 
  l2tpext@ietf.org<BR><B>Subject:</B> Re: [L2tpext] Please comment on 
  draft-galtzur-l2tpext-gr-01.txt<BR><BR></FONT></DIV>Sharon,<BR><BR>Thanx for 
  your responses.&nbsp;&nbsp; Please see further comments inline 
  ([pwh])<BR><BR>Thanx,<BR><BR>Paul Howard<BR><BR>Sharon Galtzur wrote:<BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">Hello all,
See my response in the mail body.

Sharon Galtzur

  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">-----Original Message-----
From: Paul W. Howard [<A class=moz-txt-link-freetext href="mailto:phoward@juniper.net">mailto:phoward@juniper.net</A>]
Sent: Friday, January 09, 2004 4:59 PM
To: W. Mark Townsley
Cc: <A class=moz-txt-link-abbreviated href="mailto:l2tpext@ietf.org">l2tpext@ietf.org</A>
Subject: Re: [L2tpext] Please comment on 
draft-galtzur-l2tpext-gr-01.txt


I have a few questions/concerns in regards to this draft:

1) This proposal presents what appears to be an entirely different 
mechanism than that proposed in the v2 draft 
(draft-vipin-l2tpext-failover-02.txt).   It would seem to be 
important 
that we attempt to have a single mechanism for both v2 and v3 
or to at 
least minimize the differences to those that are unavoidable.
    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
In LDP there is exactly the same occurrence - 
RFC 3478: Graceful Restart Mechanism for Label Distribution Protocol 
RFC 3479: Fault Tolerance for the Label Distribution Protocol (LDP) 

This draft follows the model presented in RFC 3478 with adaptation to L2TPv3
  </PRE></BLOCKQUOTE>[pwh] My understanding is that 3478 and 3479 present 
  signficantly different approaches to the problem of dealing with a failed 
  endpoint - 3478 recovers by learning from the non-failed endpoint (graceful 
  restart) whereas 3479 recovers by state replication on the failed 
  endpoint.&nbsp;&nbsp;&nbsp; Both your draft and Vipin's would seem to fall 
  into the category of graceful restart (i.e. learning from the non-failed 
  endpoint).&nbsp;&nbsp; Both of the l2tp drafts deal with trying to recover key 
  pieces of the control plane that are not normally obtainable from the 
  forwarding database - the sequence numbers of the control connection and the 
  state (established or non-established) of each of the sessions.&nbsp;&nbsp; It 
  would thus seem reasonable to resolve the differences between these drafts and 
  produce as common an approach as possible to graceful restart.<BR><BR>[pwh] 
  btw - I misquoted the current version of the other draft - it's 
  draft-ietf-l2tpext-failover-02.txt<BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">2) I don't understand the basic reset of the sequence number 
space for 
the control connection.   Is this setting up a replacement tunnel or 
attempting to reset the sequence numbers of the extant tunnel?
    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
The tunnel is restarted almost exactly as in
draft-ietf-l2tpext-l2tp-base-11.txt
One technical difference is the added AVP to advertise the graceful restart
capability.
Another difference is that while restarting the sessions certain information
need 
to endure the restart (i.e. Session ID, Cookie value etc) that will allow
the data path
to continue without interruptions.</PRE></BLOCKQUOTE>[pwh] I'm not entirely 
  clear on your answer.&nbsp;&nbsp; There would seem to be two basic approaches 
  to recovery of the control connection - one is to establish an entirely new 
  control connection and eventually transfer the sessions from the old control 
  connection to the new control connection; the other is to reset the extant 
  control connection,&nbsp;&nbsp; It's not clear to me from your answer or the 
  draft which direction you are proposing.&nbsp;&nbsp; So, when I attempt to 
  restart a control connection by sending an SCCRQ with the GR AVP and a 
  non-zero recovery time, what is the value of the Assigned Control Connection 
  Id AVP?&nbsp; Is it the same as the one from the initial establishment 
  (implies reset of the extant control connection) or a new value (implies a 
  recovery control connection and transfer of the sessions from the old to the 
  new)<BR><SPAN class=901140614-21012004><FONT face=Arial color=#0000ff 
  size=2>&nbsp;</FONT></SPAN><BR><SPAN class=901140614-21012004><FONT face=Arial 
  color=#0000ff size=2><SPAN class=245563909-21012004>[Sharon Galtzur]&nbsp;I 
  agree this is indeed missing from the draft - </SPAN>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>The pro and con of each approach are as follow: 
  </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>1. If we remember the the CC ID - we gain a bit more 
  confidence when we looking up the CC in the LCCE that wasn't restart, because 
  we have more information</FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>&nbsp;&nbsp;&nbsp; to compare to when recovering the CC. 
  The drawback is that the restarted LCCE must have the means to remember this 
  information (since this information is NOT </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>&nbsp;&nbsp;&nbsp; a part of the data path and hence is 
  not transferred to the data path parts of the system). </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>2. If we don't remember the CC ID - we lose some 
  confidence when we looking up the CC (but really not more then when doing 
  normal restart). The gain is that there is </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004>&nbsp;&nbsp;&nbsp; <FONT 
  face=Arial color=#0000ff size=2>no need for this information to be 
  persistent.</FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>Currently I would think that not remembering the CC ID 
  from restart to restart is preferred because it is less restrictive and is 
  more close to the non-graceful restart requirements. </FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2>I would like to hear from others what they think before I 
  update the draft.</FONT></SPAN></DIV>
  <DIV dir=ltr wrap=""><SPAN class=245563909-21012004><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>&nbsp;</FONT></SPAN><BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">3) It would appear that there is a linear relationship between the 
number of packets required for the fail over and the number of 
established sessions.   This would seem to present issues 
with scalability.
    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
The behavior of the graceful restart proposal is not worse then normal start
of 
L2TPv3 (since the mechanism of the graceful and non graceful restart are
practically the same). 
If there is scalability issue in this proposal it is inherit to the whole
L2TP model and not restricted to 
the proposed graceful restart

  </PRE></BLOCKQUOTE>[pwh] IMHO, there is a scability problem that needs to be 
  addressed.&nbsp;&nbsp;&nbsp; When a failover occurs, the failed endpoint is in 
  the process of trying to recover it's state not only for L2TP, but for all 
  other applications running in the failed endpoint (e.g. IP, BGP, PPP, AAA, 
  etc.).&nbsp;&nbsp; It is a time of maximum stress on the failed endpoint 
  coupled with restrictive time limits (e.g. BGP neighbor 
  notifications).&nbsp;&nbsp; Failover processes needs to be designed with 
  minimal resource consumption.&nbsp;&nbsp;&nbsp; This draft proposes 'n' 
  packets to be sent from the failed endpoint to the non-failed endpoint where 
  'n' is the number of sessions between the 2 endpoints.&nbsp;&nbsp; This 
  results in 10's of thousands if not 100's of thousands of packets to complete 
  the recovery.&nbsp;&nbsp;&nbsp; In order to avoid this issue, it would seem 
  that the session recovery needs to be able to recover by packing multiple 
  session recoveries per packet - thus reducing to n/m packets where m is the 
  number of recoveries per packet.&nbsp;&nbsp; As the primary recovery 
  requirement for the session is to confirm that both endpoints believe the 
  session to be in established state, this could reduce to sending the session 
  id's of the established sessions from the failed endpoint to the non-failed 
  endpoint followed by the non-failed endpoint sending back the session ids of 
  the established sessions based on the intersection of what it received from 
  the failed endpoint and it's local database.&nbsp;&nbsp; Assuming say 256 
  session ids packed in a single packet (1K of data), then we end up with 2 * n 
  / 256 packets to recover.&nbsp;&nbsp; Thus with 100,000 sessions only 782 
  packets are required to recover instead of 100,000+ 
  packets.&nbsp;&nbsp;<BR><SPAN class=901140614-21012004><FONT face=Arial 
  color=#0000ff size=2>&nbsp;</FONT></SPAN>&nbsp;<BR><SPAN 
  class=901140614-21012004><FONT face=Arial color=#0000ff size=2><SPAN 
  class=245563909-21012004>[Sharon Galtzur]&nbsp;The same can&nbsp;be said for 
  the current L2TP non-graceful restart. It is probably even more pressing since 
  there is no data flow till the connections are </SPAN>
  <DIV dir=ltr wrap=""><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN 
  class=245563909-21012004>restarted. The big advantage I see in this approach 
  is that it is so similar to normal L2TP model. This will allow implementers of 
  L2TP stacks to implement one model of establishing sessions instead of 2. 
  </SPAN></FONT></FONT></FONT></DIV>
  <DIV dir=ltr wrap=""><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN 
  class=245563909-21012004>I would suggest that if there is&nbsp;a real concern 
  of connecting 100k connection between 2 LCCE we should re-examine the 
  possibility of establishing multiple sessions connection using 1 packet 
  instead of requiring 1 packet per session in the non-graceful restart and then 
  adopt it to the graceful restart mode. 
  </SPAN></FONT></FONT></FONT></DIV>&nbsp;</FONT></SPAN><BR>
  <BLOCKQUOTE cite="midAF5018AC03D1D411ABB70002A509132601085FEA@TLV1" 
  type="cite"><PRE wrap="">  </PRE>
    <BLOCKQUOTE type="cite"><PRE wrap="">Thanx,

Paul Howard

W. Mark Townsley wrote:

    </PRE>
      <BLOCKQUOTE type="cite"><PRE wrap="">I would like to ask that interested parties review the 
      </PRE></BLOCKQUOTE><PRE wrap="">following draft 
    </PRE>
      <BLOCKQUOTE type="cite"><PRE wrap="">"Layer Two Tunneling Protocol (Version 3) Graceful Restart" and 
provide comments to the list. This draft was originally 
      </PRE></BLOCKQUOTE><PRE wrap="">presented in 
    </PRE>
      <BLOCKQUOTE type="cite"><PRE wrap="">Vienna, and updated based on comments during the meeting.

<A class=moz-txt-link-freetext href="http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt">http://www.ietf.org/internet-drafts/draft-galtzur-l2tpext-gr-01.txt</A>

The authors would like to make this a WG document.

Thanks,

- Mark


_______________________________________________
L2tpext mailing list
<A class=moz-txt-link-abbreviated href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</A>
<A class=moz-txt-link-freetext href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</A>

      </PRE></BLOCKQUOTE><PRE wrap="">_______________________________________________
L2tpext mailing list
<A class=moz-txt-link-abbreviated href="mailto:L2tpext@ietf.org">L2tpext@ietf.org</A>
<A class=moz-txt-link-freetext href="https://www1.ietf.org/mailman/listinfo/l2tpext">https://www1.ietf.org/mailman/listinfo/l2tpext</A>

    </PRE></BLOCKQUOTE><PRE wrap=""><!---->
  </PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3E027.B429F1E0--

------=_NextPartTM-000-e67da9d1-cea2-410d-a8e5-5f1baa7c3116--


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



From l2tpext-admin@ietf.org  Tue Jan 27 05:29:47 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28261
	for <l2tpext-archive@lists.ietf.org>; Tue, 27 Jan 2004 05:29:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlQSv-00088m-Qs; Tue, 27 Jan 2004 05:29:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlQSV-00087W-Qc
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 05:28:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28198
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 05:28:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlQSS-0005hS-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 05:28:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlQRa-0005eq-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 05:27:43 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlQQi-0005Z8-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 05:26:48 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
  by sj-iport-5.cisco.com with ESMTP; 27 Jan 2004 02:28:35 -0800
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0RAQG5g011819;
	Tue, 27 Jan 2004 05:26:16 -0500 (EST)
Received: from cisco.com ([10.25.65.251])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AWN16125;
	Tue, 27 Jan 2004 02:26:13 -0800 (PST)
Message-ID: <40163CC3.5050405@cisco.com>
Date: Tue, 27 Jan 2004 11:26:11 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org, Vipin Jain <vipinietf@yahoo.com>,
        Sharon Galtzur <sharon@AXERRA.com>,
        "Paul W. Howard" <phoward@juniper.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and 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>
Content-Transfer-Encoding: 7bit


I would like to try and offer a level set here for continuing the discussion.

I see that these two drafts are trying to solve similar problems, though perhaps 
optimized differently. Fundamentally, both intend to address the restablishment 
of control connection and session state for L2TP during a failure scenario. That 
may mean failover from an active to standby RP, or the restart of an RP while 
continuing to forward packets.

For the most part, either mechanism could be made to work for L2TPv3 or L2TPv2. 
I think there are obvious benefits if we can have a single mechanism for both.

The only fundamental difference I see between the two protocols themselves which 
might affect the design of the associated restart method is that in L2TPv3 the 
Control Connection ID is *not* carried in the L2TP Data Message Header, and in 
L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data Message Header. 
Thus, v3 has the advantage over v2 in that it can restart with a different 
Control Connection ID without affecting the forwarding plane. This difference is 
tangible, but would hopefully not prohibit convergence on a common mechanism.

I believe the more fundamental reason we see two divergent solutions is that 
each is being targeted to different deployment environments.

draft-galtzur-l2tpext-gr-01.txt is targeted at the current L2TPv3 space, while 
draft-ietf-l2tpext-failover-02.txt is targeted at the more mature RFC2661 L2TPv2 
space. As such,

draft-galtzur-l2tpext-gr-01.txt is optimized for an environment which is:

- Provisioned in a relatively static manner
- Has a fairly small number of sessions per LCCE
- Largely addresses restart of a single RP while continuing to forward traffic 
on a separate dataplane

draft-ietf-l2tpext-failover-02.txt is optimized for an environment which is:

- Provisioned in a largely dynamic manner
- Has a large number of sessions per LCCE
- Addresses restart of an RP, or failover to a secondary RP or node, where some 
amount of session and control connection state may be checkpointed (e.g., beyond 
that necessary for forwarding alone), and where traffic flow may be interrupted 
during failover.

One might argue that, over time, the deployment environment of L2TPv3 will look 
more and more like that of L2TPv2. e.g., higher density, more dynamic 
provisioning via auto-discovery or NMS systems, etc. Thus, some of the scaling 
benefits of draft-ietf-l2tpext-failover-02.txt could become more relevant as well.

That said, I don't believe the draft-ietf-l2tpext-failover-02.txt has all the 
kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has the advantage of 
being quite simple, is relatively complete, and requires very little (if any) 
state checkpointing beyond that which could be gleaned from the still-active 
forwarding plane which is assumed to be present. It's perfectly adequate for 
cases where you aren't concerned about how fast the sessions recover (and if you 
have a forwarding plane that is still passing packets for fairly static 
sessions, why should you care?).

Authors, please let me know if I have not articulated the situation accurately.

Next step is to try and come up with a single method (or very close to a single 
method) that operates with both versions of L2TP.

Thanks,

- Mark


















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


From exim@www1.ietf.org  Tue Jan 27 05:31:07 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28295
	for <l2tpext-archive@odin.ietf.org>; Tue, 27 Jan 2004 05:31:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlQUS-0008Ev-9Q
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 05:30:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0RAUecL031673
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 05:30:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlQUS-0008Em-0o
	for l2tpext-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 05:30:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28289
	for <l2tpext-web-archive@ietf.org>; Tue, 27 Jan 2004 05:30:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlQUO-0005nF-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 05:30:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlQTV-0005lO-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 05:29:42 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlQT7-0005iz-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 05:29:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlQSv-00088m-Qs; Tue, 27 Jan 2004 05:29:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlQSV-00087W-Qc
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 05:28:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28198
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 05:28:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlQSS-0005hS-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 05:28:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlQRa-0005eq-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 05:27:43 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlQQi-0005Z8-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 05:26:48 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
  by sj-iport-5.cisco.com with ESMTP; 27 Jan 2004 02:28:35 -0800
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0RAQG5g011819;
	Tue, 27 Jan 2004 05:26:16 -0500 (EST)
Received: from cisco.com ([10.25.65.251])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AWN16125;
	Tue, 27 Jan 2004 02:26:13 -0800 (PST)
Message-ID: <40163CC3.5050405@cisco.com>
Date: Tue, 27 Jan 2004 11:26:11 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org, Vipin Jain <vipinietf@yahoo.com>,
        Sharon Galtzur <sharon@AXERRA.com>,
        "Paul W. Howard" <phoward@juniper.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and 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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I would like to try and offer a level set here for continuing the discussion.

I see that these two drafts are trying to solve similar problems, though perhaps 
optimized differently. Fundamentally, both intend to address the restablishment 
of control connection and session state for L2TP during a failure scenario. That 
may mean failover from an active to standby RP, or the restart of an RP while 
continuing to forward packets.

For the most part, either mechanism could be made to work for L2TPv3 or L2TPv2. 
I think there are obvious benefits if we can have a single mechanism for both.

The only fundamental difference I see between the two protocols themselves which 
might affect the design of the associated restart method is that in L2TPv3 the 
Control Connection ID is *not* carried in the L2TP Data Message Header, and in 
L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data Message Header. 
Thus, v3 has the advantage over v2 in that it can restart with a different 
Control Connection ID without affecting the forwarding plane. This difference is 
tangible, but would hopefully not prohibit convergence on a common mechanism.

I believe the more fundamental reason we see two divergent solutions is that 
each is being targeted to different deployment environments.

draft-galtzur-l2tpext-gr-01.txt is targeted at the current L2TPv3 space, while 
draft-ietf-l2tpext-failover-02.txt is targeted at the more mature RFC2661 L2TPv2 
space. As such,

draft-galtzur-l2tpext-gr-01.txt is optimized for an environment which is:

- Provisioned in a relatively static manner
- Has a fairly small number of sessions per LCCE
- Largely addresses restart of a single RP while continuing to forward traffic 
on a separate dataplane

draft-ietf-l2tpext-failover-02.txt is optimized for an environment which is:

- Provisioned in a largely dynamic manner
- Has a large number of sessions per LCCE
- Addresses restart of an RP, or failover to a secondary RP or node, where some 
amount of session and control connection state may be checkpointed (e.g., beyond 
that necessary for forwarding alone), and where traffic flow may be interrupted 
during failover.

One might argue that, over time, the deployment environment of L2TPv3 will look 
more and more like that of L2TPv2. e.g., higher density, more dynamic 
provisioning via auto-discovery or NMS systems, etc. Thus, some of the scaling 
benefits of draft-ietf-l2tpext-failover-02.txt could become more relevant as well.

That said, I don't believe the draft-ietf-l2tpext-failover-02.txt has all the 
kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has the advantage of 
being quite simple, is relatively complete, and requires very little (if any) 
state checkpointing beyond that which could be gleaned from the still-active 
forwarding plane which is assumed to be present. It's perfectly adequate for 
cases where you aren't concerned about how fast the sessions recover (and if you 
have a forwarding plane that is still passing packets for fairly static 
sessions, why should you care?).

Authors, please let me know if I have not articulated the situation accurately.

Next step is to try and come up with a single method (or very close to a single 
method) that operates with both versions of L2TP.

Thanks,

- Mark


















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



From l2tpext-admin@ietf.org  Tue Jan 27 09:53:33 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07091
	for <l2tpext-archive@lists.ietf.org>; Tue, 27 Jan 2004 09:53:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlUaK-0004We-8W; Tue, 27 Jan 2004 09:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKo0-0000hM-VQ
	for l2tpext@optimus.ietf.org; Wed, 07 Jan 2004 16:01:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01497;
	Wed, 7 Jan 2004 16:01:30 -0500 (EST)
Message-Id: <200401072101.QAA01497@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, 07 Jan 2004 16:01:30 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-pwe3-ethernet-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		: Transport of Ethernet Frames over L2TPv3
	Author(s)	: R. Aggarwal
	Filename	: draft-ietf-l2tpext-pwe3-ethernet-01.txt
	Pages		: 10
	Date		: 2004-1-7
	
This document describes transport of Ethernet frames over Layer 2
Tunneling Protocol (L2TPv3). This includes the transport of Ethernet 
port to port frames as well as the transport of Ethernet VLAN frames. 
The mechanism described in this document can be used in the creation 
of Pseudo Wires to transport Ethernet frames over an IP network.

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

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Tue Jan 27 09:55:19 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07191
	for <l2tpext-archive@odin.ietf.org>; Tue, 27 Jan 2004 09:55:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlUc8-0004dp-Fb
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 09:54:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0REsqDS017835
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 09:54:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlUc8-0004da-Bl
	for l2tpext-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 09:54:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07180
	for <l2tpext-web-archive@ietf.org>; Tue, 27 Jan 2004 09:54:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlUc6-0006ZE-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 09:54:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlUbE-0006VH-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 09:53:57 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlUaO-0006R9-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 09:53:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlUaK-0004We-8W; Tue, 27 Jan 2004 09:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AeKo0-0000hM-VQ
	for l2tpext@optimus.ietf.org; Wed, 07 Jan 2004 16:01:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01497;
	Wed, 7 Jan 2004 16:01:30 -0500 (EST)
Message-Id: <200401072101.QAA01497@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, 07 Jan 2004 16:01:30 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-pwe3-ethernet-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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--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		: Transport of Ethernet Frames over L2TPv3
	Author(s)	: R. Aggarwal
	Filename	: draft-ietf-l2tpext-pwe3-ethernet-01.txt
	Pages		: 10
	Date		: 2004-1-7
	
This document describes transport of Ethernet frames over Layer 2
Tunneling Protocol (L2TPv3). This includes the transport of Ethernet 
port to port frames as well as the transport of Ethernet VLAN frames. 
The mechanism described in this document can be used in the creation 
of Pseudo Wires to transport Ethernet frames over an IP network.

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

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

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

Content-Type: text/plain
Content-ID:	<2004-1-7152713.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 Jan 27 11:32:57 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12173
	for <l2tpext-archive@lists.ietf.org>; Tue, 27 Jan 2004 11:32:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlW88-0000La-7X; Tue, 27 Jan 2004 11:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlW80-0000Ko-BT
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 11:31:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12133
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 11:31:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlW7z-0004p3-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:31:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlW75-0004lh-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:30:55 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AlW6B-0004f0-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:30:00 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Tue, 27 Jan 2004 17:19:57 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <DN5RJ3PL>; Tue, 27 Jan 2004 17:18:22 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085FF4@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>,
        "'Paul W. Howard'"
	 <phoward@juniper.net>, l2tpext@ietf.org
Cc: Sasha Vainshtein <Sasha@AXERRA.com>, Gonen Zilber <gonen@AXERRA.com>
Date: Tue, 27 Jan 2004 17:18:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [L2tpext] RE: draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failov
 er-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>

Hello mark and all,
Thank you for the summery. 

Our draft was indeed written primary for the L2tpV3 and disregarded the
L2tpV2. 
As you mentioned the main difference between V2 and V3 is that the CC Id is
part of the Session ID.
This means that for V2 the CC Id need to be remembered (or recovered from
the data plane). 
I think that a rather small modification might make our draft V2 compatible
(i.e. enforce recovering of the CC Id). 
(See my reply to Paul W. Howard on the L2TP mailing list regarding CC Id). 

Regarding the "dynamic" vs. "static" - I don't quite understand what you
refer to. 
If you refer to  draft-ietf-l2vpn-l2tp-radius-vpls-00.txt, I don't
understand why one approach is better 
then the other (other then the reconnection speed issues which is a valid
concern for both normal and graceful restart). 
If you refer to something else, could you explain what did you mean ?

Sharon Galtzur

> -----Original Message-----
> From: W. Mark Townsley [mailto:townsley@cisco.com]
> Sent: Monday, January 26, 2004 10:27 PM
> To: Sharon Galtzur; 'Paul W. Howard'; l2tpext@ietf.org
> Subject: draft-galtzur-l2tpext-gr-01.txt and 
> draft-ietf-l2tpext-failover-02.txt
> 
> 
> 
> I would like to try and offer a level set here for continuing 
> the discussion.
> 
> I see that these two drafts are trying to solve similar 
> problems, though perhaps 
> optimized differently. Fundamentally, both intend to address 
> the restablishment 
> of control connection and session state for L2TP during a 
> failure scenario. That 
> may mean failover from an active to standby RP, or the 
> restart of an RP while 
> continuing to forward packets.
> 
> For the most part, either mechanism could be made to work for 
> L2TPv3 or L2TPv2. 
> I think there are obvious benefits if we can have a single 
> mechanism for both.
> 
> The only fundamental difference I see between the two 
> protocols themselves which 
> might affect the design of the associated restart method is 
> that in L2TPv3 the 
> Control Connection ID is *not* carried in the L2TP Data 
> Message Header, and in 
> L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data 
> Message Header. 
> Thus, v3 has the advantage over v2 in that it can restart 
> with a different 
> Control Connection ID without affecting the forwarding plane. 
> This difference is 
> tangible, but would hopefully not prohibit convergence on a 
> common mechanism.
> 
> I believe the more fundamental reason we see two divergent 
> solutions is that 
> each is being targeted to different deployment environments.
> 
> draft-galtzur-l2tpext-gr-01.txt is targeted at the current 
> L2TPv3 space, while 
> draft-ietf-l2tpext-failover-02.txt is targeted at the more 
> mature RFC2661 L2TPv2 
> space. As such,
> 
> draft-galtzur-l2tpext-gr-01.txt is optimized for an 
> environment which is:
> 
> - Provisioned in a relatively static manner
> - Has a fairly small number of sessions per LCCE
> - Largely addresses restart of a single RP while continuing 
> to forward traffic 
> on a separate dataplane
> 
> draft-ietf-l2tpext-failover-02.txt is optimized for an 
> environment which is:
> 
> - Provisioned in a largely dynamic manner
> - Has a large number of sessions per LCCE
> - Addresses restart of an RP, or failover to a secondary RP 
> or node, where some 
> amount of session and control connection state may be 
> checkpointed (e.g., beyond 
> that necessary for forwarding alone), and where traffic flow 
> may be interrupted 
> during failover.
> 
> One might argue that, over time, the deployment environment 
> of L2TPv3 will look 
> more and more like that of L2TPv2. e.g., higher density, more dynamic 
> provisioning via auto-discovery or NMS systems, etc. Thus, 
> some of the scaling 
> benefits of draft-ietf-l2tpext-failover-02.txt could become 
> more relevant as well.
> 
> That said, I don't believe the 
> draft-ietf-l2tpext-failover-02.txt has all the 
> kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has 
> the advantage of 
> being quite simple, is relatively complete, and requires very 
> little (if any) 
> state checkpointing beyond that which could be gleaned from 
> the still-active 
> forwarding plane which is assumed to be present. It's 
> perfectly adequate for 
> cases where you aren't concerned about how fast the sessions 
> recover (and if you 
> have a forwarding plane that is still passing packets for 
> fairly static 
> sessions, why should you care?).
> 
> Authors, please let me know if I have not articulated the 
> situation accurately.
> 
> Next step is to try and come up with a single method (or very 
> close to a single 
> method) that operates with both versions of L2TP.
> 
> Thanks,
> 
> - Mark
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

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


From exim@www1.ietf.org  Tue Jan 27 11:34:19 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12224
	for <l2tpext-archive@odin.ietf.org>; Tue, 27 Jan 2004 11:34:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlW9v-0000R4-J7
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 11:33:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0RGXprm001668
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 11:33:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlW9v-0000Qp-DR
	for l2tpext-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 11:33:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12207
	for <l2tpext-web-archive@ietf.org>; Tue, 27 Jan 2004 11:33:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlW9u-0004ws-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 11:33:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlW90-0004u4-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 11:32:55 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlW8a-0004qv-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 11:32:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlW88-0000La-7X; Tue, 27 Jan 2004 11:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlW80-0000Ko-BT
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 11:31:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12133
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 11:31:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlW7z-0004p3-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:31:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlW75-0004lh-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:30:55 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AlW6B-0004f0-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:30:00 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Tue, 27 Jan 2004 17:19:57 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <DN5RJ3PL>; Tue, 27 Jan 2004 17:18:22 +0200
Message-ID: <AF5018AC03D1D411ABB70002A509132601085FF4@TLV1>
From: Sharon Galtzur <sharon@AXERRA.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>,
        "'Paul W. Howard'"
	 <phoward@juniper.net>, l2tpext@ietf.org
Cc: Sasha Vainshtein <Sasha@AXERRA.com>, Gonen Zilber <gonen@AXERRA.com>
Date: Tue, 27 Jan 2004 17:18:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
Subject: [L2tpext] RE: draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failov
 er-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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60

Hello mark and all,
Thank you for the summery. 

Our draft was indeed written primary for the L2tpV3 and disregarded the
L2tpV2. 
As you mentioned the main difference between V2 and V3 is that the CC Id is
part of the Session ID.
This means that for V2 the CC Id need to be remembered (or recovered from
the data plane). 
I think that a rather small modification might make our draft V2 compatible
(i.e. enforce recovering of the CC Id). 
(See my reply to Paul W. Howard on the L2TP mailing list regarding CC Id). 

Regarding the "dynamic" vs. "static" - I don't quite understand what you
refer to. 
If you refer to  draft-ietf-l2vpn-l2tp-radius-vpls-00.txt, I don't
understand why one approach is better 
then the other (other then the reconnection speed issues which is a valid
concern for both normal and graceful restart). 
If you refer to something else, could you explain what did you mean ?

Sharon Galtzur

> -----Original Message-----
> From: W. Mark Townsley [mailto:townsley@cisco.com]
> Sent: Monday, January 26, 2004 10:27 PM
> To: Sharon Galtzur; 'Paul W. Howard'; l2tpext@ietf.org
> Subject: draft-galtzur-l2tpext-gr-01.txt and 
> draft-ietf-l2tpext-failover-02.txt
> 
> 
> 
> I would like to try and offer a level set here for continuing 
> the discussion.
> 
> I see that these two drafts are trying to solve similar 
> problems, though perhaps 
> optimized differently. Fundamentally, both intend to address 
> the restablishment 
> of control connection and session state for L2TP during a 
> failure scenario. That 
> may mean failover from an active to standby RP, or the 
> restart of an RP while 
> continuing to forward packets.
> 
> For the most part, either mechanism could be made to work for 
> L2TPv3 or L2TPv2. 
> I think there are obvious benefits if we can have a single 
> mechanism for both.
> 
> The only fundamental difference I see between the two 
> protocols themselves which 
> might affect the design of the associated restart method is 
> that in L2TPv3 the 
> Control Connection ID is *not* carried in the L2TP Data 
> Message Header, and in 
> L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data 
> Message Header. 
> Thus, v3 has the advantage over v2 in that it can restart 
> with a different 
> Control Connection ID without affecting the forwarding plane. 
> This difference is 
> tangible, but would hopefully not prohibit convergence on a 
> common mechanism.
> 
> I believe the more fundamental reason we see two divergent 
> solutions is that 
> each is being targeted to different deployment environments.
> 
> draft-galtzur-l2tpext-gr-01.txt is targeted at the current 
> L2TPv3 space, while 
> draft-ietf-l2tpext-failover-02.txt is targeted at the more 
> mature RFC2661 L2TPv2 
> space. As such,
> 
> draft-galtzur-l2tpext-gr-01.txt is optimized for an 
> environment which is:
> 
> - Provisioned in a relatively static manner
> - Has a fairly small number of sessions per LCCE
> - Largely addresses restart of a single RP while continuing 
> to forward traffic 
> on a separate dataplane
> 
> draft-ietf-l2tpext-failover-02.txt is optimized for an 
> environment which is:
> 
> - Provisioned in a largely dynamic manner
> - Has a large number of sessions per LCCE
> - Addresses restart of an RP, or failover to a secondary RP 
> or node, where some 
> amount of session and control connection state may be 
> checkpointed (e.g., beyond 
> that necessary for forwarding alone), and where traffic flow 
> may be interrupted 
> during failover.
> 
> One might argue that, over time, the deployment environment 
> of L2TPv3 will look 
> more and more like that of L2TPv2. e.g., higher density, more dynamic 
> provisioning via auto-discovery or NMS systems, etc. Thus, 
> some of the scaling 
> benefits of draft-ietf-l2tpext-failover-02.txt could become 
> more relevant as well.
> 
> That said, I don't believe the 
> draft-ietf-l2tpext-failover-02.txt has all the 
> kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has 
> the advantage of 
> being quite simple, is relatively complete, and requires very 
> little (if any) 
> state checkpointing beyond that which could be gleaned from 
> the still-active 
> forwarding plane which is assumed to be present. It's 
> perfectly adequate for 
> cases where you aren't concerned about how fast the sessions 
> recover (and if you 
> have a forwarding plane that is still passing packets for 
> fairly static 
> sessions, why should you care?).
> 
> Authors, please let me know if I have not articulated the 
> situation accurately.
> 
> Next step is to try and come up with a single method (or very 
> close to a single 
> method) that operates with both versions of L2TP.
> 
> Thanks,
> 
> - Mark
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

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



From l2tpext-admin@ietf.org  Tue Jan 27 11:51:38 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12928
	for <l2tpext-archive@lists.ietf.org>; Tue, 27 Jan 2004 11:51:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWQX-0001R8-8c; Tue, 27 Jan 2004 11:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWQM-0001Pv-CE
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 11:50:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12801
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 11:50:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWQL-0005xz-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:50:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlWPM-0005rZ-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:49:50 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AlWNy-0005ja-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:48:23 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Tue, 27 Jan 2004 17:51:31 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <DN5RJ3SJ>; Tue, 27 Jan 2004 17:49:56 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326D31B23@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: Sharon Galtzur <sharon@AXERRA.com>,
        "'W. Mark Townsley'"
	 <townsley@cisco.com>,
        "'Paul W. Howard'" <phoward@juniper.net>
Cc: Gonen Zilber <gonen@AXERRA.com>, "'l2tpext@ietf.org'"
	 <l2tpext@ietf.org>
Date: Tue, 27 Jan 2004 17:49:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [L2tpext] RE: draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failov
 er-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>

Mark, Sharon, Paul and all,
Just one brief remark on the subject.

When it comes to L2TPv3- and RADIUS-based VPLS, I'd say that
a graceful restart mechanism that passes through exactly the same
authentication stages as "normal" restart" is preferable since
it leaves less possibilities for security breaches. At the same
time, the number of sessions to be recovered in case of VPLS
(which is equal to the number of VPLS instances present in
the failed PE) should not be expected anywhere in the 
100,000 range mentioned by Paul.

Did I miss something?

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Sharon Galtzur 
> Sent: Tuesday, January 27, 2004 5:18 PM
> To: 'W. Mark Townsley'; 'Paul W. Howard'; l2tpext@ietf.org
> Cc: Sasha Vainshtein; Gonen Zilber
> Subject: RE: draft-galtzur-l2tpext-gr-01.txt and 
> draft-ietf-l2tpext-failover-02.txt
> 
> 
> Hello mark and all,
> Thank you for the summery. 
> 
> Our draft was indeed written primary for the L2tpV3 and 
> disregarded the L2tpV2. 
> As you mentioned the main difference between V2 and V3 is 
> that the CC Id is part of the Session ID.
> This means that for V2 the CC Id need to be remembered (or 
> recovered from the data plane). 
> I think that a rather small modification might make our draft 
> V2 compatible (i.e. enforce recovering of the CC Id). 
> (See my reply to Paul W. Howard on the L2TP mailing list 
> regarding CC Id). 
> 
> Regarding the "dynamic" vs. "static" - I don't quite 
> understand what you refer to. 
> If you refer to  draft-ietf-l2vpn-l2tp-radius-vpls-00.txt, I 
> don't understand why one approach is better 
> then the other (other then the reconnection speed issues 
> which is a valid concern for both normal and graceful restart). 
> If you refer to something else, could you explain what did you mean ?
> 
> Sharon Galtzur
> 
> > -----Original Message-----
> > From: W. Mark Townsley [mailto:townsley@cisco.com]
> > Sent: Monday, January 26, 2004 10:27 PM
> > To: Sharon Galtzur; 'Paul W. Howard'; l2tpext@ietf.org
> > Subject: draft-galtzur-l2tpext-gr-01.txt and 
> > draft-ietf-l2tpext-failover-02.txt
> > 
> > 
> > 
> > I would like to try and offer a level set here for continuing 
> > the discussion.
> > 
> > I see that these two drafts are trying to solve similar 
> > problems, though perhaps 
> > optimized differently. Fundamentally, both intend to address 
> > the restablishment 
> > of control connection and session state for L2TP during a 
> > failure scenario. That 
> > may mean failover from an active to standby RP, or the 
> > restart of an RP while 
> > continuing to forward packets.
> > 
> > For the most part, either mechanism could be made to work for 
> > L2TPv3 or L2TPv2. 
> > I think there are obvious benefits if we can have a single 
> > mechanism for both.
> > 
> > The only fundamental difference I see between the two 
> > protocols themselves which 
> > might affect the design of the associated restart method is 
> > that in L2TPv3 the 
> > Control Connection ID is *not* carried in the L2TP Data 
> > Message Header, and in 
> > L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data 
> > Message Header. 
> > Thus, v3 has the advantage over v2 in that it can restart 
> > with a different 
> > Control Connection ID without affecting the forwarding plane. 
> > This difference is 
> > tangible, but would hopefully not prohibit convergence on a 
> > common mechanism.
> > 
> > I believe the more fundamental reason we see two divergent 
> > solutions is that 
> > each is being targeted to different deployment environments.
> > 
> > draft-galtzur-l2tpext-gr-01.txt is targeted at the current 
> > L2TPv3 space, while 
> > draft-ietf-l2tpext-failover-02.txt is targeted at the more 
> > mature RFC2661 L2TPv2 
> > space. As such,
> > 
> > draft-galtzur-l2tpext-gr-01.txt is optimized for an 
> > environment which is:
> > 
> > - Provisioned in a relatively static manner
> > - Has a fairly small number of sessions per LCCE
> > - Largely addresses restart of a single RP while continuing 
> > to forward traffic 
> > on a separate dataplane
> > 
> > draft-ietf-l2tpext-failover-02.txt is optimized for an 
> > environment which is:
> > 
> > - Provisioned in a largely dynamic manner
> > - Has a large number of sessions per LCCE
> > - Addresses restart of an RP, or failover to a secondary RP 
> > or node, where some 
> > amount of session and control connection state may be 
> > checkpointed (e.g., beyond 
> > that necessary for forwarding alone), and where traffic flow 
> > may be interrupted 
> > during failover.
> > 
> > One might argue that, over time, the deployment environment 
> > of L2TPv3 will look 
> > more and more like that of L2TPv2. e.g., higher density, 
> more dynamic 
> > provisioning via auto-discovery or NMS systems, etc. Thus, 
> > some of the scaling 
> > benefits of draft-ietf-l2tpext-failover-02.txt could become 
> > more relevant as well.
> > 
> > That said, I don't believe the 
> > draft-ietf-l2tpext-failover-02.txt has all the 
> > kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has 
> > the advantage of 
> > being quite simple, is relatively complete, and requires very 
> > little (if any) 
> > state checkpointing beyond that which could be gleaned from 
> > the still-active 
> > forwarding plane which is assumed to be present. It's 
> > perfectly adequate for 
> > cases where you aren't concerned about how fast the sessions 
> > recover (and if you 
> > have a forwarding plane that is still passing packets for 
> > fairly static 
> > sessions, why should you care?).
> > 
> > Authors, please let me know if I have not articulated the 
> > situation accurately.
> > 
> > Next step is to try and come up with a single method (or very 
> > close to a single 
> > method) that operates with both versions of L2TP.
> > 
> > Thanks,
> > 
> > - Mark
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 

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


From exim@www1.ietf.org  Tue Jan 27 11:53:29 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13039
	for <l2tpext-archive@odin.ietf.org>; Tue, 27 Jan 2004 11:53:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWST-0001ZG-NS
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 11:53:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0RGr1bE006020
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 11:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWST-0001Z1-K7
	for l2tpext-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 11:53:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13003
	for <l2tpext-web-archive@ietf.org>; Tue, 27 Jan 2004 11:52:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWSS-0006AZ-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 11:53:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlWRt-00065t-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 11:52:27 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWQg-000616-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 11:51:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWQX-0001R8-8c; Tue, 27 Jan 2004 11:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWQM-0001Pv-CE
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 11:50:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12801
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 11:50:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWQL-0005xz-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:50:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlWPM-0005rZ-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:49:50 -0500
Received: from [80.74.100.67] (helo=antivir2)
	by ietf-mx with smtp (Exim 4.12)
	id 1AlWNy-0005ja-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 11:48:23 -0500
Received: from 192.168.254.14 by antivir2 (InterScan E-Mail VirusWall NT); Tue, 27 Jan 2004 17:51:31 +0200
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <DN5RJ3SJ>; Tue, 27 Jan 2004 17:49:56 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326D31B23@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: Sharon Galtzur <sharon@AXERRA.com>,
        "'W. Mark Townsley'"
	 <townsley@cisco.com>,
        "'Paul W. Howard'" <phoward@juniper.net>
Cc: Gonen Zilber <gonen@AXERRA.com>, "'l2tpext@ietf.org'"
	 <l2tpext@ietf.org>
Date: Tue, 27 Jan 2004 17:49:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-8"
Subject: [L2tpext] RE: draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failov
 er-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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

Mark, Sharon, Paul and all,
Just one brief remark on the subject.

When it comes to L2TPv3- and RADIUS-based VPLS, I'd say that
a graceful restart mechanism that passes through exactly the same
authentication stages as "normal" restart" is preferable since
it leaves less possibilities for security breaches. At the same
time, the number of sessions to be recovered in case of VPLS
(which is equal to the number of VPLS instances present in
the failed PE) should not be expected anywhere in the 
100,000 range mentioned by Paul.

Did I miss something?

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Sharon Galtzur 
> Sent: Tuesday, January 27, 2004 5:18 PM
> To: 'W. Mark Townsley'; 'Paul W. Howard'; l2tpext@ietf.org
> Cc: Sasha Vainshtein; Gonen Zilber
> Subject: RE: draft-galtzur-l2tpext-gr-01.txt and 
> draft-ietf-l2tpext-failover-02.txt
> 
> 
> Hello mark and all,
> Thank you for the summery. 
> 
> Our draft was indeed written primary for the L2tpV3 and 
> disregarded the L2tpV2. 
> As you mentioned the main difference between V2 and V3 is 
> that the CC Id is part of the Session ID.
> This means that for V2 the CC Id need to be remembered (or 
> recovered from the data plane). 
> I think that a rather small modification might make our draft 
> V2 compatible (i.e. enforce recovering of the CC Id). 
> (See my reply to Paul W. Howard on the L2TP mailing list 
> regarding CC Id). 
> 
> Regarding the "dynamic" vs. "static" - I don't quite 
> understand what you refer to. 
> If you refer to  draft-ietf-l2vpn-l2tp-radius-vpls-00.txt, I 
> don't understand why one approach is better 
> then the other (other then the reconnection speed issues 
> which is a valid concern for both normal and graceful restart). 
> If you refer to something else, could you explain what did you mean ?
> 
> Sharon Galtzur
> 
> > -----Original Message-----
> > From: W. Mark Townsley [mailto:townsley@cisco.com]
> > Sent: Monday, January 26, 2004 10:27 PM
> > To: Sharon Galtzur; 'Paul W. Howard'; l2tpext@ietf.org
> > Subject: draft-galtzur-l2tpext-gr-01.txt and 
> > draft-ietf-l2tpext-failover-02.txt
> > 
> > 
> > 
> > I would like to try and offer a level set here for continuing 
> > the discussion.
> > 
> > I see that these two drafts are trying to solve similar 
> > problems, though perhaps 
> > optimized differently. Fundamentally, both intend to address 
> > the restablishment 
> > of control connection and session state for L2TP during a 
> > failure scenario. That 
> > may mean failover from an active to standby RP, or the 
> > restart of an RP while 
> > continuing to forward packets.
> > 
> > For the most part, either mechanism could be made to work for 
> > L2TPv3 or L2TPv2. 
> > I think there are obvious benefits if we can have a single 
> > mechanism for both.
> > 
> > The only fundamental difference I see between the two 
> > protocols themselves which 
> > might affect the design of the associated restart method is 
> > that in L2TPv3 the 
> > Control Connection ID is *not* carried in the L2TP Data 
> > Message Header, and in 
> > L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data 
> > Message Header. 
> > Thus, v3 has the advantage over v2 in that it can restart 
> > with a different 
> > Control Connection ID without affecting the forwarding plane. 
> > This difference is 
> > tangible, but would hopefully not prohibit convergence on a 
> > common mechanism.
> > 
> > I believe the more fundamental reason we see two divergent 
> > solutions is that 
> > each is being targeted to different deployment environments.
> > 
> > draft-galtzur-l2tpext-gr-01.txt is targeted at the current 
> > L2TPv3 space, while 
> > draft-ietf-l2tpext-failover-02.txt is targeted at the more 
> > mature RFC2661 L2TPv2 
> > space. As such,
> > 
> > draft-galtzur-l2tpext-gr-01.txt is optimized for an 
> > environment which is:
> > 
> > - Provisioned in a relatively static manner
> > - Has a fairly small number of sessions per LCCE
> > - Largely addresses restart of a single RP while continuing 
> > to forward traffic 
> > on a separate dataplane
> > 
> > draft-ietf-l2tpext-failover-02.txt is optimized for an 
> > environment which is:
> > 
> > - Provisioned in a largely dynamic manner
> > - Has a large number of sessions per LCCE
> > - Addresses restart of an RP, or failover to a secondary RP 
> > or node, where some 
> > amount of session and control connection state may be 
> > checkpointed (e.g., beyond 
> > that necessary for forwarding alone), and where traffic flow 
> > may be interrupted 
> > during failover.
> > 
> > One might argue that, over time, the deployment environment 
> > of L2TPv3 will look 
> > more and more like that of L2TPv2. e.g., higher density, 
> more dynamic 
> > provisioning via auto-discovery or NMS systems, etc. Thus, 
> > some of the scaling 
> > benefits of draft-ietf-l2tpext-failover-02.txt could become 
> > more relevant as well.
> > 
> > That said, I don't believe the 
> > draft-ietf-l2tpext-failover-02.txt has all the 
> > kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has 
> > the advantage of 
> > being quite simple, is relatively complete, and requires very 
> > little (if any) 
> > state checkpointing beyond that which could be gleaned from 
> > the still-active 
> > forwarding plane which is assumed to be present. It's 
> > perfectly adequate for 
> > cases where you aren't concerned about how fast the sessions 
> > recover (and if you 
> > have a forwarding plane that is still passing packets for 
> > fairly static 
> > sessions, why should you care?).
> > 
> > Authors, please let me know if I have not articulated the 
> > situation accurately.
> > 
> > Next step is to try and come up with a single method (or very 
> > close to a single 
> > method) that operates with both versions of L2TP.
> > 
> > Thanks,
> > 
> > - Mark
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 

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



From l2tpext-admin@ietf.org  Tue Jan 27 12:13:38 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13800
	for <l2tpext-archive@lists.ietf.org>; Tue, 27 Jan 2004 12:13:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWlp-0002wF-1Q; Tue, 27 Jan 2004 12:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWld-0002ut-6G
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 12:12:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13775
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 12:12:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWlb-0007Oi-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 12:12:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlWkf-0007LX-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 12:11:50 -0500
Received: from westford-nat.juniper.net ([65.194.140.2] helo=pi-smtp.jnpr.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWjm-0007GB-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 12:10:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt
Date: Tue, 27 Jan 2004 12:10:22 -0500
Message-ID: <98F04BA831360C4FB5F7FC0118D9182801D00F46@pi.jnpr.net>
Thread-Topic: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt
Thread-Index: AcPkwIu+RE8ZQLt6R7ijWjyrQKGwoQANVGCg
From: "Tom Mistretta" <tmistretta@juniper.net>
To: "W. Mark Townsley" <townsley@cisco.com>, <l2tpext@ietf.org>,
        "Vipin Jain" <vipinietf@yahoo.com>,
        "Sharon Galtzur" <sharon@AXERRA.com>,
        "Paul Howard" <phoward@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
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: quoted-printable


Certainly failover-02 needed to benefit from feedback and refinement, =
but this is not unusual.  Vipin and Paul have made great progress =
offline.  I don't think the "newness" of the technology should be viewed =
as an obstacle. =20

That said, I don't believe it is possible to have a single mechanism =
that will satisfy the perspectives of both the "static" and "dynamic" =
models.  If the group believes with deep conviction that these two =
models should be defined as important separate applications of l2tp, =
important enough that each perspective warrants such satisfaction, then =
I think the only way to proceed is to allow two solutions.  Each =
solution would have to come with a clear explanation of the tradeoffs =
between them.  At a minimum, the failover-02 draft will have to be =
enhanced to take care of v3.

I think it is most unfortunate for the (nay, any) protocol to have more =
than one mechanism for failure recovery.  It sets a bad precedent, as =
someone in the future may think of another l2tp application that =
benefits from yet another recovery mechanism.

Tom

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


From exim@www1.ietf.org  Tue Jan 27 12:16:09 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13928
	for <l2tpext-archive@odin.ietf.org>; Tue, 27 Jan 2004 12:16:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWoQ-00032f-6Y
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 12:15:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0RHFgdB011687
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 12:15:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWoQ-00032Q-28
	for l2tpext-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 12:15:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13853
	for <l2tpext-web-archive@ietf.org>; Tue, 27 Jan 2004 12:15:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWoO-0007Yz-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 12:15:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlWmh-0007T7-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 12:13:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWly-0007Ps-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 12:13:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWlp-0002wF-1Q; Tue, 27 Jan 2004 12:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlWld-0002ut-6G
	for l2tpext@optimus.ietf.org; Tue, 27 Jan 2004 12:12:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13775
	for <l2tpext@ietf.org>; Tue, 27 Jan 2004 12:12:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWlb-0007Oi-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 12:12:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlWkf-0007LX-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 12:11:50 -0500
Received: from westford-nat.juniper.net ([65.194.140.2] helo=pi-smtp.jnpr.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlWjm-0007GB-00
	for l2tpext@ietf.org; Tue, 27 Jan 2004 12:10:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt
Date: Tue, 27 Jan 2004 12:10:22 -0500
Message-ID: <98F04BA831360C4FB5F7FC0118D9182801D00F46@pi.jnpr.net>
Thread-Topic: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt
Thread-Index: AcPkwIu+RE8ZQLt6R7ijWjyrQKGwoQANVGCg
From: "Tom Mistretta" <tmistretta@juniper.net>
To: "W. Mark Townsley" <townsley@cisco.com>, <l2tpext@ietf.org>,
        "Vipin Jain" <vipinietf@yahoo.com>,
        "Sharon Galtzur" <sharon@AXERRA.com>,
        "Paul Howard" <phoward@juniper.net>
Content-Transfer-Encoding: quoted-printable
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Certainly failover-02 needed to benefit from feedback and refinement, =
but this is not unusual.  Vipin and Paul have made great progress =
offline.  I don't think the "newness" of the technology should be viewed =
as an obstacle. =20

That said, I don't believe it is possible to have a single mechanism =
that will satisfy the perspectives of both the "static" and "dynamic" =
models.  If the group believes with deep conviction that these two =
models should be defined as important separate applications of l2tp, =
important enough that each perspective warrants such satisfaction, then =
I think the only way to proceed is to allow two solutions.  Each =
solution would have to come with a clear explanation of the tradeoffs =
between them.  At a minimum, the failover-02 draft will have to be =
enhanced to take care of v3.

I think it is most unfortunate for the (nay, any) protocol to have more =
than one mechanism for failure recovery.  It sets a bad precedent, as =
someone in the future may think of another l2tp application that =
benefits from yet another recovery mechanism.

Tom

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



From l2tpext-admin@ietf.org  Tue Jan 27 19:10:57 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02594
	for <l2tpext-archive@lists.ietf.org>; Tue, 27 Jan 2004 19:10:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AldHO-0001Wq-G3; Tue, 27 Jan 2004 19:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlDOS-0006wr-68
	for l2tpext@optimus.ietf.org; Mon, 26 Jan 2004 15:31:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19260
	for <l2tpext@ietf.org>; Mon, 26 Jan 2004 15:31:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlDOL-0002IG-00
	for l2tpext@ietf.org; Mon, 26 Jan 2004 15:31:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlDMN-0002Ca-00
	for l2tpext@ietf.org; Mon, 26 Jan 2004 15:29:28 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlDLF-00027H-00
	for l2tpext@ietf.org; Mon, 26 Jan 2004 15:28:18 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0QKRJ5g022979;
	Mon, 26 Jan 2004 15:27:19 -0500 (EST)
Received: from cisco.com (rtp-vpn2-490.cisco.com [10.82.241.234])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AWM71071;
	Mon, 26 Jan 2004 12:27:17 -0800 (PST)
Message-ID: <40157824.4080104@cisco.com>
Date: Mon, 26 Jan 2004 21:27:16 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sharon Galtzur <sharon@AXERRA.com>,
        "'Paul W. Howard'" <phoward@juniper.net>, l2tpext@ietf.org
References: <AF5018AC03D1D411ABB70002A509132601085FED@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A509132601085FED@TLV1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and 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>
Content-Transfer-Encoding: 7bit


I would like to try and offer a level set here for continuing the discussion.

I see that these two drafts are trying to solve similar problems, though perhaps 
optimized differently. Fundamentally, both intend to address the restablishment 
of control connection and session state for L2TP during a failure scenario. That 
may mean failover from an active to standby RP, or the restart of an RP while 
continuing to forward packets.

For the most part, either mechanism could be made to work for L2TPv3 or L2TPv2. 
I think there are obvious benefits if we can have a single mechanism for both.

The only fundamental difference I see between the two protocols themselves which 
might affect the design of the associated restart method is that in L2TPv3 the 
Control Connection ID is *not* carried in the L2TP Data Message Header, and in 
L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data Message Header. 
Thus, v3 has the advantage over v2 in that it can restart with a different 
Control Connection ID without affecting the forwarding plane. This difference is 
tangible, but would hopefully not prohibit convergence on a common mechanism.

I believe the more fundamental reason we see two divergent solutions is that 
each is being targeted to different deployment environments.

draft-galtzur-l2tpext-gr-01.txt is targeted at the current L2TPv3 space, while 
draft-ietf-l2tpext-failover-02.txt is targeted at the more mature RFC2661 L2TPv2 
space. As such,

draft-galtzur-l2tpext-gr-01.txt is optimized for an environment which is:

- Provisioned in a relatively static manner
- Has a fairly small number of sessions per LCCE
- Largely addresses restart of a single RP while continuing to forward traffic 
on a separate dataplane

draft-ietf-l2tpext-failover-02.txt is optimized for an environment which is:

- Provisioned in a largely dynamic manner
- Has a large number of sessions per LCCE
- Addresses restart of an RP, or failover to a secondary RP or node, where some 
amount of session and control connection state may be checkpointed (e.g., beyond 
that necessary for forwarding alone), and where traffic flow may be interrupted 
during failover.

One might argue that, over time, the deployment environment of L2TPv3 will look 
more and more like that of L2TPv2. e.g., higher density, more dynamic 
provisioning via auto-discovery or NMS systems, etc. Thus, some of the scaling 
benefits of draft-ietf-l2tpext-failover-02.txt could become more relevant as well.

That said, I don't believe the draft-ietf-l2tpext-failover-02.txt has all the 
kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has the advantage of 
being quite simple, is relatively complete, and requires very little (if any) 
state checkpointing beyond that which could be gleaned from the still-active 
forwarding plane which is assumed to be present. It's perfectly adequate for 
cases where you aren't concerned about how fast the sessions recover (and if you 
have a forwarding plane that is still passing packets for fairly static 
sessions, why should you care?).

Authors, please let me know if I have not articulated the situation accurately.

Next step is to try and come up with a single method (or very close to a single 
method) that operates with both versions of L2TP.

Thanks,

- Mark
















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


From exim@www1.ietf.org  Tue Jan 27 20:45:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09427
	for <l2tpext-archive@odin.ietf.org>; Tue, 27 Jan 2004 20:45:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlelQ-0002Rl-6n
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 20:45:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S1j80b009401
	for l2tpext-archive@odin.ietf.org; Tue, 27 Jan 2004 20:45:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlelQ-0002RY-2k
	for l2tpext-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 20:45:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09392
	for <l2tpext-web-archive@ietf.org>; Tue, 27 Jan 2004 20:45:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlelN-00009l-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 20:45:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlekS-00005S-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 20:44:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlejT-00001f-00
	for l2tpext-web-archive@ietf.org; Tue, 27 Jan 2004 20:43:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AldHO-0001Wq-G3; Tue, 27 Jan 2004 19:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlDOS-0006wr-68
	for l2tpext@optimus.ietf.org; Mon, 26 Jan 2004 15:31:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19260
	for <l2tpext@ietf.org>; Mon, 26 Jan 2004 15:31:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlDOL-0002IG-00
	for l2tpext@ietf.org; Mon, 26 Jan 2004 15:31:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlDMN-0002Ca-00
	for l2tpext@ietf.org; Mon, 26 Jan 2004 15:29:28 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlDLF-00027H-00
	for l2tpext@ietf.org; Mon, 26 Jan 2004 15:28:18 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0QKRJ5g022979;
	Mon, 26 Jan 2004 15:27:19 -0500 (EST)
Received: from cisco.com (rtp-vpn2-490.cisco.com [10.82.241.234])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AWM71071;
	Mon, 26 Jan 2004 12:27:17 -0800 (PST)
Message-ID: <40157824.4080104@cisco.com>
Date: Mon, 26 Jan 2004 21:27:16 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sharon Galtzur <sharon@AXERRA.com>,
        "'Paul W. Howard'" <phoward@juniper.net>, l2tpext@ietf.org
References: <AF5018AC03D1D411ABB70002A509132601085FED@TLV1>
In-Reply-To: <AF5018AC03D1D411ABB70002A509132601085FED@TLV1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and 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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I would like to try and offer a level set here for continuing the discussion.

I see that these two drafts are trying to solve similar problems, though perhaps 
optimized differently. Fundamentally, both intend to address the restablishment 
of control connection and session state for L2TP during a failure scenario. That 
may mean failover from an active to standby RP, or the restart of an RP while 
continuing to forward packets.

For the most part, either mechanism could be made to work for L2TPv3 or L2TPv2. 
I think there are obvious benefits if we can have a single mechanism for both.

The only fundamental difference I see between the two protocols themselves which 
might affect the design of the associated restart method is that in L2TPv3 the 
Control Connection ID is *not* carried in the L2TP Data Message Header, and in 
L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data Message Header. 
Thus, v3 has the advantage over v2 in that it can restart with a different 
Control Connection ID without affecting the forwarding plane. This difference is 
tangible, but would hopefully not prohibit convergence on a common mechanism.

I believe the more fundamental reason we see two divergent solutions is that 
each is being targeted to different deployment environments.

draft-galtzur-l2tpext-gr-01.txt is targeted at the current L2TPv3 space, while 
draft-ietf-l2tpext-failover-02.txt is targeted at the more mature RFC2661 L2TPv2 
space. As such,

draft-galtzur-l2tpext-gr-01.txt is optimized for an environment which is:

- Provisioned in a relatively static manner
- Has a fairly small number of sessions per LCCE
- Largely addresses restart of a single RP while continuing to forward traffic 
on a separate dataplane

draft-ietf-l2tpext-failover-02.txt is optimized for an environment which is:

- Provisioned in a largely dynamic manner
- Has a large number of sessions per LCCE
- Addresses restart of an RP, or failover to a secondary RP or node, where some 
amount of session and control connection state may be checkpointed (e.g., beyond 
that necessary for forwarding alone), and where traffic flow may be interrupted 
during failover.

One might argue that, over time, the deployment environment of L2TPv3 will look 
more and more like that of L2TPv2. e.g., higher density, more dynamic 
provisioning via auto-discovery or NMS systems, etc. Thus, some of the scaling 
benefits of draft-ietf-l2tpext-failover-02.txt could become more relevant as well.

That said, I don't believe the draft-ietf-l2tpext-failover-02.txt has all the 
kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has the advantage of 
being quite simple, is relatively complete, and requires very little (if any) 
state checkpointing beyond that which could be gleaned from the still-active 
forwarding plane which is assumed to be present. It's perfectly adequate for 
cases where you aren't concerned about how fast the sessions recover (and if you 
have a forwarding plane that is still passing packets for fairly static 
sessions, why should you care?).

Authors, please let me know if I have not articulated the situation accurately.

Next step is to try and come up with a single method (or very close to a single 
method) that operates with both versions of L2TP.

Thanks,

- Mark
















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



From l2tpext-admin@ietf.org  Wed Jan 28 05:14:39 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23528
	for <l2tpext-archive@lists.ietf.org>; Wed, 28 Jan 2004 05:14:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Almhv-0000Xq-N2; Wed, 28 Jan 2004 05:14:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Almha-0000Vq-0s
	for l2tpext@optimus.ietf.org; Wed, 28 Jan 2004 05:13:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23441
	for <l2tpext@ietf.org>; Wed, 28 Jan 2004 05:13:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlmhW-0000TW-00
	for l2tpext@ietf.org; Wed, 28 Jan 2004 05:13:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlmgU-0000Lp-00
	for l2tpext@ietf.org; Wed, 28 Jan 2004 05:12:37 -0500
Received: from web41315.mail.yahoo.com ([66.218.93.64])
	by ietf-mx with smtp (Exim 4.12)
	id 1Almfy-0000DV-00
	for l2tpext@ietf.org; Wed, 28 Jan 2004 05:12:03 -0500
Message-ID: <20040128101133.55265.qmail@web41315.mail.yahoo.com>
Received: from [66.17.149.13] by web41315.mail.yahoo.com via HTTP; Wed, 28 Jan 2004 02:11:33 PST
Date: Wed, 28 Jan 2004 02:11:33 -0800 (PST)
From: Vipin Jain <vipinietf@yahoo.com>
Subject: Re: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt
To: "W. Mark Townsley" <townsley@cisco.com>, l2tpext@ietf.org,
        Sharon Galtzur <sharon@AXERRA.com>,
        "Paul W. Howard" <phoward@juniper.net>
In-Reply-To: <40163CC3.5050405@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-683355829-1075284693=:52645"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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>

--0-683355829-1075284693=:52645
Content-Type: text/plain; charset=us-ascii
Content-Id: 
Content-Disposition: inline

My comments:

I think both drafts are complete (I am attaching
draft-ietf-l2tpext-failover-03.txt for everyone's review).

However, the main trade-off seems to be the simplicity vs. scalability, as
identified as goals in in Appendix A of draft-ietf-l2tpext-failover-03.txt.

Just wondering: Why the mechanism described in
draft-ietf-l2tpext-failover-03.txt would not work (and scale) for L2TPv3 as
well?

thanks,
-- vipin


--- "W. Mark Townsley" <townsley@cisco.com> wrote:
> 
> I would like to try and offer a level set here for continuing the discussion.
> 
> I see that these two drafts are trying to solve similar problems, though
> perhaps 
> optimized differently. Fundamentally, both intend to address the
> restablishment 
> of control connection and session state for L2TP during a failure scenario.
> That 
> may mean failover from an active to standby RP, or the restart of an RP while
> 
> continuing to forward packets.
> 
> For the most part, either mechanism could be made to work for L2TPv3 or
> L2TPv2. 
> I think there are obvious benefits if we can have a single mechanism for
> both.
> 
> The only fundamental difference I see between the two protocols themselves
> which 
> might affect the design of the associated restart method is that in L2TPv3
> the 
> Control Connection ID is *not* carried in the L2TP Data Message Header, and
> in 
> L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data Message Header. 
> Thus, v3 has the advantage over v2 in that it can restart with a different 
> Control Connection ID without affecting the forwarding plane. This difference
> is 
> tangible, but would hopefully not prohibit convergence on a common mechanism.
> 
> I believe the more fundamental reason we see two divergent solutions is that 
> each is being targeted to different deployment environments.
> 
> draft-galtzur-l2tpext-gr-01.txt is targeted at the current L2TPv3 space,
> while 
> draft-ietf-l2tpext-failover-02.txt is targeted at the more mature RFC2661
> L2TPv2 
> space. As such,
> 
> draft-galtzur-l2tpext-gr-01.txt is optimized for an environment which is:
> 
> - Provisioned in a relatively static manner
> - Has a fairly small number of sessions per LCCE
> - Largely addresses restart of a single RP while continuing to forward
> traffic 
> on a separate dataplane
> 
> draft-ietf-l2tpext-failover-02.txt is optimized for an environment which is:
> 
> - Provisioned in a largely dynamic manner
> - Has a large number of sessions per LCCE
> - Addresses restart of an RP, or failover to a secondary RP or node, where
> some 
> amount of session and control connection state may be checkpointed (e.g.,
> beyond 
> that necessary for forwarding alone), and where traffic flow may be
> interrupted 
> during failover.
> 
> One might argue that, over time, the deployment environment of L2TPv3 will
> look 
> more and more like that of L2TPv2. e.g., higher density, more dynamic 
> provisioning via auto-discovery or NMS systems, etc. Thus, some of the
> scaling 
> benefits of draft-ietf-l2tpext-failover-02.txt could become more relevant as
> well.
> 
> That said, I don't believe the draft-ietf-l2tpext-failover-02.txt has all the
> 
> kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has the advantage of 
> being quite simple, is relatively complete, and requires very little (if any)
> 
> state checkpointing beyond that which could be gleaned from the still-active 
> forwarding plane which is assumed to be present. It's perfectly adequate for 
> cases where you aren't concerned about how fast the sessions recover (and if
> you 
> have a forwarding plane that is still passing packets for fairly static 
> sessions, why should you care?).
> 
> Authors, please let me know if I have not articulated the situation
> accurately.
> 
> Next step is to try and come up with a single method (or very close to a
> single 
> method) that operates with both versions of L2TP.
> 
> Thanks,
> 
> - Mark
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
--0-683355829-1075284693=:52645
Content-Type: text/plain; name="draft-ietf-l2tpext-failover-03.txt"
Content-Description: draft-ietf-l2tpext-failover-03.txt
Content-Disposition: inline; filename="draft-ietf-l2tpext-failover-03.txt"


Network Working Group                                         Vipin Jain
Internet-Draft                                       Riverstone Networks
Expires July 2004                                                 Editor

                                                            January 2004


                Fail Over extensions for L2TP "failover"

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026.

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026 except that the right to produce derivative
   works is not granted.

   This document is an Internet-Draft and is NOT offered in accordance
   with Section 10 of RFC2026, and the author does not provide the IETF
   with any rights other than to publish as an Internet-Draft


   The distribution of this memo is unlimited. Please send comments to
   the L2TP mailing list (l2tpext@ietf.org).

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.


Abstract

   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.





Jain                        expires July 2004                   [Page 1]

INTERNET DRAFT                  FAILOVER                     August 2003


Contributors

   Following is the complete list of contributors to this document.

   Paul Howard
   Juniper Networks
   Mark Townsley
   Cisco Systems
   Vipin Jain
   Riverstone Networks
   Sam Henderson
   Cisco Systems
   Ly Loi
   Tahoe Networks
   Leo Huber
   Extreme Networks
   Keyur Parikh
   Sentito Networks

Table of Contents

   Status of this Memo ..........................................    1
   1.0 Introduction .............................................    2
   2.0 Protocol Operation .......................................    3
   2.1 Pre Failover Operation ...................................    4
   2.2 Failover Recovery Process ................................    5
   2.2.1 Recovery Tunnel Establishment ..........................    6
   2.2.2 Control and Data Channel Reset .........................    6
   2.2.3 Begin Session Synchronization Timer ....................    7
   2.3 Failover Recovery Process ................................    8
   2.4 Post Failover Cleanup ....................................    9
   2.5 Procedure to Reset Only Data Channel .....................   10
   3.0 IANA Considerations ......................................   11
   4.0 Security Considerations ..................................   11
   5.0 Acknowledgements .........................................   11
   6.0 Author Addresses .........................................   11
   9.0 References................................................   13

   Appendix A ..................................................    14
   Appendix B ..................................................    15

Terminology

   Endpoint: An L2TP control connection endpoint, either LAC or LNS.

      Active Endpoint: An endpoint that is currently providing service.

      Backup Endpoint: A redundant endpoint standing by for the active endpoint.



Jain                        expires July 2004                   [Page 2]

INTERNET DRAFT                  FAILOVER                     August 2003


      Recovered Tunnel: An old tunnel that has been recovered using the
      mechanism described in this document.

      Recovery Tunnel: A new tunnel that is established only to recover an
      old tunnel.

      Failover: The action of a Backup Endpoint taking over the service of an
      Active Endpoint. This could be due to administrative action or failure
      of the Active Endpoint.

1.0 Introduction

   The goal of this draft is to aid the overall resiliency of an L2TP
   endpoint by introducing extensions to RFC 2661 [L2TP] that will
   minimize the recovery time of the L2TP layer after a failover, while
   minimizing the impact on its performance. Therefore it is assumed that
   the endpoint's overall architecture is also supportive in the
   resiliency effort.

   To ensure proper operation of a L2TP endpoint after a failover, the
   associated information of the tunnels and sessions between them must be
   correct and consistent. This includes both the configured and dynamic
   information. The configured information is assumed to be correct and
   consistent after a failover, otherwise the tunnels and sessions would
   not have been setup in the first place. The dynamic information, which
   is also referred to as stateful information, changes with the
   processing of tunnel's control and data packets. Currently, the only
   such information that is essential to the tunnel's operation is its
   sequence numbers. For the tunnel control channel, the inconsistencies
   in its sequence numbers can result in the termination of the entire
   tunnel. For tunnel sessions, the inconsistency in its sequence, when
   used, can cause significant data loss thus giving perception of "service
   loss" to the end user.

   Thus, an optimal resilient architecture that aims to minimize  "service
   loss" after a failover must make provision for the tunnel's essential
   stateful information - i.e. its sequence numbers. Currently, there are
   two options available: the first option is to ensure that the backup
   endpoint is in complete sync with the active with respect to the
   control and data sessions sequence numbers. The other option is to
   simply re-establish all the tunnels and its sessions after a failover.
   The drawback of the first option is that it adds significant
   performance and complexity impact to the endpoint's architecture,
   especially as tunnel and session aggregation increases. The drawback of
   the second option is that it increases the "service loss"  time,
   especially as the architecture scales.




Jain                        expires July 2004                   [Page 3]

INTERNET DRAFT                  FAILOVER                     August 2003


   To alleviate the above-mentioned drawbacks of the current options, this
   draft introduces a mechanism to bring the dynamic stateful information
   of a tunnel to correct and consistent state after a failure. Proposed
   mechanism, currently, defines the recovery of tunnels and sessions that
   were in established state prior to the failure.

2.0 Protocol Operation

   The control channel protocol recovery consists of four phases - pre failover,
   failover recovery, session state synchronization, and post failover cleanup.

   Pre failover operation allows an endpoint to specify its failover
   capabilities and timer values, attributes that are used when failover
   occurs.

   Failover recovery is started at the failed endpoint when it initiates
   a new L2TP tunnel (called recovery tunnel), for every old tunnel that
   needs recovery. The recovery tunnel serves four purposes: 1) It provides
   a means of authentication and a three-way handshake to ensure both ends
   agree on the failover for a given tunnel. 2) It identifies the old
   tunnel that needs recovery.  3) It identifies if the failed endpoint
   would like to recover control and/or data path. 4) It identifies
   the Ns and Nr values to be used in the recovered tunnel on both ends.
   Upon establishing the recovery tunnel, two endpoints reset their control
   and data channel, after which the new tunnel could be torn down.
   The sessions that were in established state resume traffic and new
   sessions could be established on the recovered tunnel.

   Session state synchronization process gets rid of the sessions
   that resulted into inconsistent states due to the failure on one of
   the endpoints. Two endpoints utilize FSQ/FSR messages over the
   recovered tunnel to agree upon the state of various sessions within
   the tunnel.

   Post failover cleanup concludes the failover process by doing three
   actions: 1) Cleanup the sessions that were not in established state.
   2) Teardown various tunnels established for the purpose of recovery.
   3) Stop accepting FSQ and FSR messages.

   Data channel failure without control channel failure could avoid
   recovery tunnel establishment, and indicate the reset by simply sending
   Data Channel Failure message over the existing control channel.

   2.1 Pre Failover Operation

      An endpoint that supports the failover protocol defined in this
      document MUST include Failover Capability AVP in SCCRQ or SCCRP
      during tunnel establishment.




Jain                        expires July 2004                   [Page 4]

INTERNET DRAFT                  FAILOVER                     August 2003


      Failover Capability AVP

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Attribute Type [TBD]  |         Reserved          |D|C|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              Recovery Time (in milliseconds)                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is not
      mandatory (the M-bit MUST be set to 0).

      The D bit, when set indicates that an endpoint is capable of
      supporting its peer's data channel failure.  The C bit, when set
      indicates that an endpoint is capable of supporting its peer's
      control channel failure.

      Recovery Time is the time in milliseconds an endpoint asks its
      peer to wait before assuming the failure recovery to fail.  This
      time includes the control channel timeout period as described in
      [L2TP]. A value of zero indicates that the endpoint is not capable
      of failing over the control channel. For example, and endpoint MAY
      set it to zero if it can not preserve the state sessions within
      the tunnel.


   2.2 Failover Recovery Procedure

      Failover recovery procedure consists of three steps: 1) Recovery
      tunnel establishment 2) Control and/or data channel reset 3) Begin
      Session Synchronization timer.

      2.2.1 Recovery tunnel establishment

         Failed endpoint establishes a new tunnel, called recovery
         tunnel, for every old tunnel it wishes to recover. The purpose
         of the recovery tunnel is solely to recover the corresponding
         old tunnel. An endpoint MUST not send any control message on
         this tunnel except mentioned in this document. To indicate
         failure on its end, the recovery tunnel MUST include Tunnel
         Recovery AVP in its SCCRQ message.







Jain                        expires July 2004                   [Page 5]

INTERNET DRAFT                  FAILOVER                     August 2003


         Tunnel Recovery AVP

          0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |         Attribute Type [TBD]  |          Reserved         |D|C|
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |       Recover Tunnel Id       |    Recover Remote Tunnel Id   |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |           Session Sync Wait Time (in milliseconds)            |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

         This AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is
         mandatory (the M-bit is set to 1).

         The D bit is set when a failed endpoint would like to recover
         the data channel for sessions within the tunnel. Where the C
         bit is set when the failed endpoint would like to recover the
         control channel.

         Recover Tunnel Id encodes the tunnel id that is subjected to
         recovery.  Similarly, Recover Remote Tunnel Id encodes the
         remote tunnel id corresponding to the old tunnel.

         Session Sync Wait Time is the time in milliseconds an endpoint
         asks its peer to wait before starting post failure operation
         related cleanup. This value is derived from the time an
         endpoint would take to clean up session inconsistencies with
         respect to resources required. A zero value, though not
         recommended, indicates that peer could start the post failure
         cleanup immediately after the tunnel is recovered.

         Upon getting an SCCRQ with Tunnel Recovery AVP the non failed
         endpoint validates Recover Tunnel Id values and responds with
         SCCRP. It MUST terminate the tunnel if Recover Tunnel Id or
         Remote Recover Tunnel Id is unknown.

         If non failed endpoint accepts the SCCRQ, it MAY include
         Suggested Control Channel Sequence AVP in the SCCRP.










Jain                        expires July 2004                   [Page 6]

INTERNET DRAFT                  FAILOVER                     August 2003


         Suggested Control Sequence AVP

          0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |         Attribute Type [TBD]  |            Reserved           |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |        Suggested Ns           |         Suggested Nr          |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

         This AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is
         not mandatory (the M-bit is set to 0).

         This is an optional AVP, suggesting the Ns and Nr values to be
         used by the failed endpoint. If this AVP is  present in an
         SCCRP message, the failed endpoint MUST set the Ns and Nr
         values of the recovered tunnel to the suggested values. When
         this AVP is not sent in SCCRP or not present in an incoming
         SCCRP, the Ns and Nr values for the recovery tunnel are set to
         zero. It is RECOMMENDED that the non failed endpoint suggests
         the Ns and Nr values to help avoid the interference in
         recovered tunnel's control channel with old control packets.

         To authenticate the peer during tunnel recovery, an endpoint
         MUST follow the procedure described in [L2TP] section 5.1.1
         using the same secret used to authenticate the old tunnel.  Not
         being able to authenticate could be a reason to terminate then
         new tunnel. For any reason if failed endpoint could not
         establish the new tunnel could then it MUST assume that
         recovery has failed and cleanup the tunnel and sessions within.

         Any control packet received on the tunnel that has not been
         recovered (i.e. till control channel has not been reset) is
         siliently discarded.

         The procedure described in this document does not specifically
         consider the scenario of both endpoints failing simultaneously.
         In such situations, an endpoint MAY assume that the recovery
         has failed.


      2.2.2 Control and Data Channel Reset

         Failed endpoint in Tunnel Recovery AVP (SCCRQ) indicates if it
         would like to reset control channel, and optionally data
         channel along with.  Data channel reset without control channel



Jain                        expires July 2004                   [Page 7]

INTERNET DRAFT                  FAILOVER                     August 2003


         reset uses the mechanism described in section 3.0 of this
         document.

         Control channel reset means flushing the transmit and receive
         windows, and resetting the control channel sequence numbers
         (i.e. Ns and/or Nr values). The control channel on failed
         endpoint is reset upon getting a valid SCCRP, whereas control
         path on non failed endpoint is reset upon getting a valid
         SCCCN. If an endpoint does not receive Suggested sequence
         number AVP in SCCRP then it MUST reset Ns and Nr values to
         zero. Similarly if non failed endpoint opts not to send
         suggested sequence number AVP then it MUST reset Ns and Nr
         values to zero.

         Data channel reset requires no action if data channel doesn't
         use sequence numbers. Whereas if data channel were using
         sequence numbers then the sequence numbers are reset as
         follows: - Failed endpoint MUST stop receiving and transmitting
         data packets on all sessions, before sending SCCRQ on the
         recovery tunnel.  - Failed endpoint resets Ns to zero. It also
         sets Nr from the Ns received in the first data packet after
         sending SCCCN on the recovery tunnel.  - After resetting Ns and
         Nr values, failed endpoint can start transmitting and receiving
         the data.  - Non failed endpoint reset the Nr to zero upon
         receipt of a valid SCCN.  It doesn't reset the Ns value.

         After resetting the control channel, it MUST allow sending and
         receiving various control messages including new session
         establishments.

      2.2.3 Begin Session Synchronization Timer

         Once the tunnel recovery is done i.e. control/data channel
         is(are) reset, each endpoint starts Session Synchronization
         Timer, value of which is indicated by the peer in Tunnel
         Recovery AVP. When this time expires it starts the Post
         Failover process described in section 2.4


   2.3 Session State Synchronization

      During failure it is likely to have two endpoints disagree on the
      existence/state of a session. Therefore it becomes very important
      for the two endpoints to agree upon the sessions that they are
      going to preserve in a tunnel. If failover happens while a session
      is being established or being torn down, it is possible that one
      of the endpoints consider the session in the established state
      where as its peer consider the same session to be down or non



Jain                        expires July 2004                   [Page 8]

INTERNET DRAFT                  FAILOVER                     August 2003


      existent.  Two such situations occur when an endpoint fails after
      sending:
      - A CDN message that never made to the peer.
      - An ICCN message that never made to to the peer.

      Session State inconsistency applies only for control channel
      failure not data channel failure.

      Following mechanism is proposed to identify and clear the sessions
      that exists on an endpoint but non existent on its peer.

      - After the recovery tunnel is established, the sessions that were
      not in established state are silently cleared i.e. without sending
      a CDN message to the peer.

      - Both endpoints SHOULD identify the sessions that might have been
      in inconsistent states, perhaps based on data channel inactivity.

      - After identifying the suspect sessions, an endpoint requests its
      peer the state of these sessions by sending a new message, message
      type [TBD], called as Failover Session Query (FSQ) message.  This
      message MUST include at least one Failover Session State AVPs.  An
      endpoint may send another FSQ messages on the recovered tunnel
      before getting a response for the first FSQ.  Failover Session
      State AVP is described as follows:

      While the set of established sessions is synchronized among two
      endpoints, it is possible to get an ICRQ for a session an endpoint
      beleive is already in established state. It MUST respond it with a
      CDN and clear the session on its end.

      Failover Session State AVP

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |      Attribute Type [TBD]     |            Session Id         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        Remote Session Id      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      This AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is
      mandatory (the M-bit is set to 1).

      Session Id identifies the local session id sender had assigned,
      for which it would like to query the state on its peer.  Remote
      Session Id is the remote session id for the same session.



Jain                        expires July 2004                   [Page 9]

INTERNET DRAFT                  FAILOVER                     August 2003



      - If an endpoint receives an FSQ message, it responds with
      Failover Session Response (FSR) message, message type [TBD], that
      has one Failover Session State AVP for each requested AVP in FSQ.
      For each Failover Session State AVP received in FSQ message, it
      MUST find out if the Remote Session Id is a valid existing local
      session id and that it is paired with the Session Id specified in
      the message.  If it discovers that the session is non-existing it
      MUST respond back with a Failover Session State AVP in FSR message
      with Session Id field set to zero, and Remote Session Id value set
      to the received value of Session Id in the corresponding AVP in
      the FSQ message.

      - When an endpoint receives an FSR message, it MUST use the Remote
      Session Id field to identify the local session and silently
      (without sending a CDN) clean the session if Session Id is set to
      zero. Otherwise it considers the session to be in established
      state and recovered.

      - FSQ and FSR messages SHOULD not be entertained after Recovery
      time has elapsed.

      - FSQ and FSR Messages MAY include Challenge and Challenge
      Response AVPs as defined by section 5.1.1 [L2TP] to authenticate
      the peer.


   2.4 Post Failover Cleanup

      This process is triggered when Recovery time has elapsed since the
      control and data channel were reset. Cleanup process does
      following:
      - Teardown recovery tunnels if they are still established.
      - Stop receiving FSQ and FSR messages from the peer.
      - Cleanup any remaining stale sessions. Sessions that are
      responded by the peer in FSR message to be up, are not considered
      stale even when data channel inactivity is observed.
      - Other resources acquired to start failover process.


   3.0 Data Channel Only Failure

      Mechanism described in section 2.0 MUST not be used to reset the
      data channel failure alone. If an endpoint receives an SCCRQ with
      Tunnel Recovery AVP that doesn't have 'C' bit set then it MUST
      terminate the tunnel.




Jain                        expires July 2004                  [Page 10]

INTERNET DRAFT                  FAILOVER                     August 2003


      Data failure channel reset is not needed when sequence numbers are
      not used. Two endpoints reset the data channel failure by sending
      a new message, Data Channel Failure (DCF) message over the
      existing control channel.


4. IANA Considerations

   This document requires four new "AVP Attributes" and three new
   messages to be assigned through IETF Consensus [RFC2434] as indicated
   in Section 10.1 of [RFC2661]. These are:

         Failover Capability AVP (section 2.1)

         Tunnel Recovery AVP (section 2.2.1)

         Suggested Control Sequence AVP (section 2.2.1)

         Failover Session State AVP (section 2.3)

         Failover Session Query Message (FSQ) (section 2.3)

         Failover Session Response Message (FSR) (section 2.3)

         Data Channel Failure Message (section 3.0)

5. Security Considerations

   The failover mechanism described here leaves a some room (1 in 2^32)
   for an intruder to discover the old tunnel id of an existing tunnel
   by trying out various possibilities in Recovery Tunnel Id and
   Recovery Remote Tunnel Id AVP.

   It also introduces an opportunity for an intruder to spoof the
   FSQ/FSR messages and know the active sessions.

6. Acknowledgements

   Leo Huber of Extreme Networks provided valuable suggestions to help
   define the failover concept.  Ly Loi reviewd the draft and provided
   suggestions on improving it.

8. Author Information


      Vipin Jain
      Riverstone Networks
      5200 Great America Parkway
      Santa Clara, CA 95054
      Phone: +1 408.655.9115
      Email: vipinietf@yahoo.com



Jain                        expires July 2004                  [Page 11]

INTERNET DRAFT                  FAILOVER                     August 2003



      Paul W. Howard
      Juniper Networks
      10 Technology Park Drive
      Westford, MA 01886
      Email: phoward@juniper.net

      Keyur Parikh
      Sentito Networks
      238 Littleton Road Suite 101
      Westford, MA 01886
      Phone: +1 978.399.0223
      Email: kparikh@sentito.com

      W. Mark Townsley
      Cisco Systems
      7025 Kit Creek Road
      PO Box 14987
      Research Triangle Park, NC 27709
      Email: townsley@cisco.com


8. References

   [L2TP] Townsley, et. al., "Layer Two Tunneling Protocol L2TP", RFC2661


Appendix A

This section describes some design considerations that came up during
discussions when developing the proposal:

   A.1  Backward compatibility and extensibility

      -  The mechanism should be backwards compatible; i.e. it should
      not redefine existing behavior of [L2TP] compliant systems.

      - The protocol should allow a peer to detect failover capabilities
      in advance, for it to fall back to other failover mechanisms
      should peer does not support proposed failover protocol.

      - The protocol should allow future extensions to fail-over
      mechanism at ease.





Jain                        expires July 2004                  [Page 12]

INTERNET DRAFT                  FAILOVER                     August 2003


   A.2  Less failover recovery time

   The mechanism should have least possible time to recover from
   failover (target of 3-5 seconds for 30k tunnels). Specifically it
   should take following into consideration:

      - Faster recovery: by utilizing less number of messages exchanged
      to recover from failover

      - CPU intensiveness: less cpu intensive a proposal is, better are
      the changes of faster recovery

      - Parallel establishment of various tunnels: by keeping different
      tunnel reestablishments independent of one another.

   A.3  Less Payload data loss

   The mechanism should have least possible impact on data flows for
   sessions with sequencing enabled.

   A.4  Minimum interference with pre-failure control traffic

   The mechanism should define a way of clearly distinguishing the
   messages that were sent before failover from that which are sent
   after.  Specifically, it should define a mechanism that avoid
   confusion between sequence numbers that were used before and after if
   the same Tunnel Id is used.

   A.5  Simplicity

   Simpler the protocol is, better are the changes of being adopted by
   everybody. Following would help achieve this:

      - Use of existing AVPs, messages and packet formats.

      - Avoid introducing special considerations and mechanisms a new
      implementation would have to deal with.

      - Simpler post fail-over synchronization mechanism.


   A.6  Security

   The mechanism should provide a mechanism to authenticate peers when
   resynchronization is happening after a failover.





Jain                        expires July 2004                  [Page 13]

INTERNET DRAFT                  FAILOVER                     August 2003


   A.7 Scalability

   It is very important for a proposed protocol to work well for a
   scalable deployment. This includes dealing with all design
   considerations discussed above for scalable deployments, having
   thousands of tunnels or sessions or mix of the two.

   A target of 30,000 tunnels carrying 150,000 to 200,000 sessions from
   300 peers was considered during the design.


Appendix B

   Figure below outlines the the failover protocol operation for an
   example tunnel. The failover protocol does not preclude an endpoint
   from recovering multiple tunnels in parallel. It also allows an
   endpoint from sending multiple FSQs to recover quickly.

      Pre Failover Exchange (section 2.1):

      Endpoint                                             Peer
                   (assigned tid = x, failover capable)
      SCCRQ       -------------------------------------->  validate SCCRQ

                   (assigned tid = y, failover capable)
      validate    <--------------------------------------  send SCCRP
      SCCRP, etc.

      .... <after tunnel gets created, sessions are established> ....


      < This Node fails >

      Failed endpoint establishes recovery tunnel (section 2.2.1).
      Initiate recovery tunnel establishment for the old tunnel 'x':

      Failed Endpoint                                      Peer

                (assigned tid = z, Recovery AVP)
      SCCRQ     ----------------------------------->  Detects failover
              (recover tid = x, recover remote tid = y)  validate SCCRQ


               (assigned tid = w, opt. Suggested Seqence AVP)
      validate <-----------------------------------   send SCCRP
      SCCRP    (recover tid = y, recover remote tid = x)
      reset Ns/Nr

      SCCN      ----------------------------------->  validate and reset
                                                      the old tunnel.



Jain                        expires July 2004                  [Page 14]

INTERNET DRAFT                  FAILOVER                     August 2003


      Start session synchronization timer (section 2.2.3)

      Session states are synchronized both endpoints may send FSQs and
      cleanup stale sessions (section 2.3)

                 (FSS AVP for sessions s1, s2, s3..)
      send FSQ  -------------------------------------> compute the state
                                                       of sessions in FSQ

                 (FSS AVP for sessions s1, s2, s3...)
      deletes  <-------------------------------------- send FSR
      stale sessions, if any


                 (FSS AVP for sessions s7, s8, s9...)
      compute  <-------------------------------------- send FSQ
      the sate of
      sessions in FSQ


                 (FSS AVP for sessions s7, s8, s9...)
      send FSR --------------------------------------> delete stale sessions,
                                                       if any


      Session Sync Time expires, Start Post Failover process (section 2.4)

      Cleanup and terminate tid = 'z'
      StopCCN  --------------------------------------> Cleanup 'w'

      Stop receiving and sending FSQs and FSRs.
      Cleanup sessions that are still stale within the tunnel.



















Jain                        expires July 2004                  [Page 15]

--0-683355829-1075284693=:52645--

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


From exim@www1.ietf.org  Wed Jan 28 05:17:20 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23828
	for <l2tpext-archive@odin.ietf.org>; Wed, 28 Jan 2004 05:17:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlmkC-0000qK-1L
	for l2tpext-archive@odin.ietf.org; Wed, 28 Jan 2004 05:16:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SAGNXg003238
	for l2tpext-archive@odin.ietf.org; Wed, 28 Jan 2004 05:16:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlmkB-0000pq-NN
	for l2tpext-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 05:16:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23770
	for <l2tpext-web-archive@ietf.org>; Wed, 28 Jan 2004 05:16:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Almk8-0000xp-00
	for l2tpext-web-archive@ietf.org; Wed, 28 Jan 2004 05:16:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Almj7-0000kc-00
	for l2tpext-web-archive@ietf.org; Wed, 28 Jan 2004 05:15:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Almi1-0000Xc-00
	for l2tpext-web-archive@ietf.org; Wed, 28 Jan 2004 05:14:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Almhv-0000Xq-N2; Wed, 28 Jan 2004 05:14:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Almha-0000Vq-0s
	for l2tpext@optimus.ietf.org; Wed, 28 Jan 2004 05:13:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23441
	for <l2tpext@ietf.org>; Wed, 28 Jan 2004 05:13:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlmhW-0000TW-00
	for l2tpext@ietf.org; Wed, 28 Jan 2004 05:13:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlmgU-0000Lp-00
	for l2tpext@ietf.org; Wed, 28 Jan 2004 05:12:37 -0500
Received: from web41315.mail.yahoo.com ([66.218.93.64])
	by ietf-mx with smtp (Exim 4.12)
	id 1Almfy-0000DV-00
	for l2tpext@ietf.org; Wed, 28 Jan 2004 05:12:03 -0500
Message-ID: <20040128101133.55265.qmail@web41315.mail.yahoo.com>
Received: from [66.17.149.13] by web41315.mail.yahoo.com via HTTP; Wed, 28 Jan 2004 02:11:33 PST
Date: Wed, 28 Jan 2004 02:11:33 -0800 (PST)
From: Vipin Jain <vipinietf@yahoo.com>
Subject: Re: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt
To: "W. Mark Townsley" <townsley@cisco.com>, l2tpext@ietf.org,
        Sharon Galtzur <sharon@AXERRA.com>,
        "Paul W. Howard" <phoward@juniper.net>
In-Reply-To: <40163CC3.5050405@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-683355829-1075284693=:52645"
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

--0-683355829-1075284693=:52645
Content-Type: text/plain; charset=us-ascii
Content-Id: 
Content-Disposition: inline

My comments:

I think both drafts are complete (I am attaching
draft-ietf-l2tpext-failover-03.txt for everyone's review).

However, the main trade-off seems to be the simplicity vs. scalability, as
identified as goals in in Appendix A of draft-ietf-l2tpext-failover-03.txt.

Just wondering: Why the mechanism described in
draft-ietf-l2tpext-failover-03.txt would not work (and scale) for L2TPv3 as
well?

thanks,
-- vipin


--- "W. Mark Townsley" <townsley@cisco.com> wrote:
> 
> I would like to try and offer a level set here for continuing the discussion.
> 
> I see that these two drafts are trying to solve similar problems, though
> perhaps 
> optimized differently. Fundamentally, both intend to address the
> restablishment 
> of control connection and session state for L2TP during a failure scenario.
> That 
> may mean failover from an active to standby RP, or the restart of an RP while
> 
> continuing to forward packets.
> 
> For the most part, either mechanism could be made to work for L2TPv3 or
> L2TPv2. 
> I think there are obvious benefits if we can have a single mechanism for
> both.
> 
> The only fundamental difference I see between the two protocols themselves
> which 
> might affect the design of the associated restart method is that in L2TPv3
> the 
> Control Connection ID is *not* carried in the L2TP Data Message Header, and
> in 
> L2TPv2 the analogous Tunnel ID *is* carried in the L2TP Data Message Header. 
> Thus, v3 has the advantage over v2 in that it can restart with a different 
> Control Connection ID without affecting the forwarding plane. This difference
> is 
> tangible, but would hopefully not prohibit convergence on a common mechanism.
> 
> I believe the more fundamental reason we see two divergent solutions is that 
> each is being targeted to different deployment environments.
> 
> draft-galtzur-l2tpext-gr-01.txt is targeted at the current L2TPv3 space,
> while 
> draft-ietf-l2tpext-failover-02.txt is targeted at the more mature RFC2661
> L2TPv2 
> space. As such,
> 
> draft-galtzur-l2tpext-gr-01.txt is optimized for an environment which is:
> 
> - Provisioned in a relatively static manner
> - Has a fairly small number of sessions per LCCE
> - Largely addresses restart of a single RP while continuing to forward
> traffic 
> on a separate dataplane
> 
> draft-ietf-l2tpext-failover-02.txt is optimized for an environment which is:
> 
> - Provisioned in a largely dynamic manner
> - Has a large number of sessions per LCCE
> - Addresses restart of an RP, or failover to a secondary RP or node, where
> some 
> amount of session and control connection state may be checkpointed (e.g.,
> beyond 
> that necessary for forwarding alone), and where traffic flow may be
> interrupted 
> during failover.
> 
> One might argue that, over time, the deployment environment of L2TPv3 will
> look 
> more and more like that of L2TPv2. e.g., higher density, more dynamic 
> provisioning via auto-discovery or NMS systems, etc. Thus, some of the
> scaling 
> benefits of draft-ietf-l2tpext-failover-02.txt could become more relevant as
> well.
> 
> That said, I don't believe the draft-ietf-l2tpext-failover-02.txt has all the
> 
> kinks worked out in it. draft-galtzur-l2tpext-gr-01.txt has the advantage of 
> being quite simple, is relatively complete, and requires very little (if any)
> 
> state checkpointing beyond that which could be gleaned from the still-active 
> forwarding plane which is assumed to be present. It's perfectly adequate for 
> cases where you aren't concerned about how fast the sessions recover (and if
> you 
> have a forwarding plane that is still passing packets for fairly static 
> sessions, why should you care?).
> 
> Authors, please let me know if I have not articulated the situation
> accurately.
> 
> Next step is to try and come up with a single method (or very close to a
> single 
> method) that operates with both versions of L2TP.
> 
> Thanks,
> 
> - Mark
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
--0-683355829-1075284693=:52645
Content-Type: text/plain; name="draft-ietf-l2tpext-failover-03.txt"
Content-Description: draft-ietf-l2tpext-failover-03.txt
Content-Disposition: inline; filename="draft-ietf-l2tpext-failover-03.txt"


Network Working Group                                         Vipin Jain
Internet-Draft                                       Riverstone Networks
Expires July 2004                                                 Editor

                                                            January 2004


                Fail Over extensions for L2TP "failover"

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026.

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026 except that the right to produce derivative
   works is not granted.

   This document is an Internet-Draft and is NOT offered in accordance
   with Section 10 of RFC2026, and the author does not provide the IETF
   with any rights other than to publish as an Internet-Draft


   The distribution of this memo is unlimited. Please send comments to
   the L2TP mailing list (l2tpext@ietf.org).

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.


Abstract

   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.





Jain                        expires July 2004                   [Page 1]

INTERNET DRAFT                  FAILOVER                     August 2003


Contributors

   Following is the complete list of contributors to this document.

   Paul Howard
   Juniper Networks
   Mark Townsley
   Cisco Systems
   Vipin Jain
   Riverstone Networks
   Sam Henderson
   Cisco Systems
   Ly Loi
   Tahoe Networks
   Leo Huber
   Extreme Networks
   Keyur Parikh
   Sentito Networks

Table of Contents

   Status of this Memo ..........................................    1
   1.0 Introduction .............................................    2
   2.0 Protocol Operation .......................................    3
   2.1 Pre Failover Operation ...................................    4
   2.2 Failover Recovery Process ................................    5
   2.2.1 Recovery Tunnel Establishment ..........................    6
   2.2.2 Control and Data Channel Reset .........................    6
   2.2.3 Begin Session Synchronization Timer ....................    7
   2.3 Failover Recovery Process ................................    8
   2.4 Post Failover Cleanup ....................................    9
   2.5 Procedure to Reset Only Data Channel .....................   10
   3.0 IANA Considerations ......................................   11
   4.0 Security Considerations ..................................   11
   5.0 Acknowledgements .........................................   11
   6.0 Author Addresses .........................................   11
   9.0 References................................................   13

   Appendix A ..................................................    14
   Appendix B ..................................................    15

Terminology

   Endpoint: An L2TP control connection endpoint, either LAC or LNS.

      Active Endpoint: An endpoint that is currently providing service.

      Backup Endpoint: A redundant endpoint standing by for the active endpoint.



Jain                        expires July 2004                   [Page 2]

INTERNET DRAFT                  FAILOVER                     August 2003


      Recovered Tunnel: An old tunnel that has been recovered using the
      mechanism described in this document.

      Recovery Tunnel: A new tunnel that is established only to recover an
      old tunnel.

      Failover: The action of a Backup Endpoint taking over the service of an
      Active Endpoint. This could be due to administrative action or failure
      of the Active Endpoint.

1.0 Introduction

   The goal of this draft is to aid the overall resiliency of an L2TP
   endpoint by introducing extensions to RFC 2661 [L2TP] that will
   minimize the recovery time of the L2TP layer after a failover, while
   minimizing the impact on its performance. Therefore it is assumed that
   the endpoint's overall architecture is also supportive in the
   resiliency effort.

   To ensure proper operation of a L2TP endpoint after a failover, the
   associated information of the tunnels and sessions between them must be
   correct and consistent. This includes both the configured and dynamic
   information. The configured information is assumed to be correct and
   consistent after a failover, otherwise the tunnels and sessions would
   not have been setup in the first place. The dynamic information, which
   is also referred to as stateful information, changes with the
   processing of tunnel's control and data packets. Currently, the only
   such information that is essential to the tunnel's operation is its
   sequence numbers. For the tunnel control channel, the inconsistencies
   in its sequence numbers can result in the termination of the entire
   tunnel. For tunnel sessions, the inconsistency in its sequence, when
   used, can cause significant data loss thus giving perception of "service
   loss" to the end user.

   Thus, an optimal resilient architecture that aims to minimize  "service
   loss" after a failover must make provision for the tunnel's essential
   stateful information - i.e. its sequence numbers. Currently, there are
   two options available: the first option is to ensure that the backup
   endpoint is in complete sync with the active with respect to the
   control and data sessions sequence numbers. The other option is to
   simply re-establish all the tunnels and its sessions after a failover.
   The drawback of the first option is that it adds significant
   performance and complexity impact to the endpoint's architecture,
   especially as tunnel and session aggregation increases. The drawback of
   the second option is that it increases the "service loss"  time,
   especially as the architecture scales.




Jain                        expires July 2004                   [Page 3]

INTERNET DRAFT                  FAILOVER                     August 2003


   To alleviate the above-mentioned drawbacks of the current options, this
   draft introduces a mechanism to bring the dynamic stateful information
   of a tunnel to correct and consistent state after a failure. Proposed
   mechanism, currently, defines the recovery of tunnels and sessions that
   were in established state prior to the failure.

2.0 Protocol Operation

   The control channel protocol recovery consists of four phases - pre failover,
   failover recovery, session state synchronization, and post failover cleanup.

   Pre failover operation allows an endpoint to specify its failover
   capabilities and timer values, attributes that are used when failover
   occurs.

   Failover recovery is started at the failed endpoint when it initiates
   a new L2TP tunnel (called recovery tunnel), for every old tunnel that
   needs recovery. The recovery tunnel serves four purposes: 1) It provides
   a means of authentication and a three-way handshake to ensure both ends
   agree on the failover for a given tunnel. 2) It identifies the old
   tunnel that needs recovery.  3) It identifies if the failed endpoint
   would like to recover control and/or data path. 4) It identifies
   the Ns and Nr values to be used in the recovered tunnel on both ends.
   Upon establishing the recovery tunnel, two endpoints reset their control
   and data channel, after which the new tunnel could be torn down.
   The sessions that were in established state resume traffic and new
   sessions could be established on the recovered tunnel.

   Session state synchronization process gets rid of the sessions
   that resulted into inconsistent states due to the failure on one of
   the endpoints. Two endpoints utilize FSQ/FSR messages over the
   recovered tunnel to agree upon the state of various sessions within
   the tunnel.

   Post failover cleanup concludes the failover process by doing three
   actions: 1) Cleanup the sessions that were not in established state.
   2) Teardown various tunnels established for the purpose of recovery.
   3) Stop accepting FSQ and FSR messages.

   Data channel failure without control channel failure could avoid
   recovery tunnel establishment, and indicate the reset by simply sending
   Data Channel Failure message over the existing control channel.

   2.1 Pre Failover Operation

      An endpoint that supports the failover protocol defined in this
      document MUST include Failover Capability AVP in SCCRQ or SCCRP
      during tunnel establishment.




Jain                        expires July 2004                   [Page 4]

INTERNET DRAFT                  FAILOVER                     August 2003


      Failover Capability AVP

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Attribute Type [TBD]  |         Reserved          |D|C|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              Recovery Time (in milliseconds)                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is not
      mandatory (the M-bit MUST be set to 0).

      The D bit, when set indicates that an endpoint is capable of
      supporting its peer's data channel failure.  The C bit, when set
      indicates that an endpoint is capable of supporting its peer's
      control channel failure.

      Recovery Time is the time in milliseconds an endpoint asks its
      peer to wait before assuming the failure recovery to fail.  This
      time includes the control channel timeout period as described in
      [L2TP]. A value of zero indicates that the endpoint is not capable
      of failing over the control channel. For example, and endpoint MAY
      set it to zero if it can not preserve the state sessions within
      the tunnel.


   2.2 Failover Recovery Procedure

      Failover recovery procedure consists of three steps: 1) Recovery
      tunnel establishment 2) Control and/or data channel reset 3) Begin
      Session Synchronization timer.

      2.2.1 Recovery tunnel establishment

         Failed endpoint establishes a new tunnel, called recovery
         tunnel, for every old tunnel it wishes to recover. The purpose
         of the recovery tunnel is solely to recover the corresponding
         old tunnel. An endpoint MUST not send any control message on
         this tunnel except mentioned in this document. To indicate
         failure on its end, the recovery tunnel MUST include Tunnel
         Recovery AVP in its SCCRQ message.







Jain                        expires July 2004                   [Page 5]

INTERNET DRAFT                  FAILOVER                     August 2003


         Tunnel Recovery AVP

          0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |         Attribute Type [TBD]  |          Reserved         |D|C|
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |       Recover Tunnel Id       |    Recover Remote Tunnel Id   |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |           Session Sync Wait Time (in milliseconds)            |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

         This AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is
         mandatory (the M-bit is set to 1).

         The D bit is set when a failed endpoint would like to recover
         the data channel for sessions within the tunnel. Where the C
         bit is set when the failed endpoint would like to recover the
         control channel.

         Recover Tunnel Id encodes the tunnel id that is subjected to
         recovery.  Similarly, Recover Remote Tunnel Id encodes the
         remote tunnel id corresponding to the old tunnel.

         Session Sync Wait Time is the time in milliseconds an endpoint
         asks its peer to wait before starting post failure operation
         related cleanup. This value is derived from the time an
         endpoint would take to clean up session inconsistencies with
         respect to resources required. A zero value, though not
         recommended, indicates that peer could start the post failure
         cleanup immediately after the tunnel is recovered.

         Upon getting an SCCRQ with Tunnel Recovery AVP the non failed
         endpoint validates Recover Tunnel Id values and responds with
         SCCRP. It MUST terminate the tunnel if Recover Tunnel Id or
         Remote Recover Tunnel Id is unknown.

         If non failed endpoint accepts the SCCRQ, it MAY include
         Suggested Control Channel Sequence AVP in the SCCRP.










Jain                        expires July 2004                   [Page 6]

INTERNET DRAFT                  FAILOVER                     August 2003


         Suggested Control Sequence AVP

          0                   1                   2                   3
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |         Attribute Type [TBD]  |            Reserved           |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         |        Suggested Ns           |         Suggested Nr          |
         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

         This AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is
         not mandatory (the M-bit is set to 0).

         This is an optional AVP, suggesting the Ns and Nr values to be
         used by the failed endpoint. If this AVP is  present in an
         SCCRP message, the failed endpoint MUST set the Ns and Nr
         values of the recovered tunnel to the suggested values. When
         this AVP is not sent in SCCRP or not present in an incoming
         SCCRP, the Ns and Nr values for the recovery tunnel are set to
         zero. It is RECOMMENDED that the non failed endpoint suggests
         the Ns and Nr values to help avoid the interference in
         recovered tunnel's control channel with old control packets.

         To authenticate the peer during tunnel recovery, an endpoint
         MUST follow the procedure described in [L2TP] section 5.1.1
         using the same secret used to authenticate the old tunnel.  Not
         being able to authenticate could be a reason to terminate then
         new tunnel. For any reason if failed endpoint could not
         establish the new tunnel could then it MUST assume that
         recovery has failed and cleanup the tunnel and sessions within.

         Any control packet received on the tunnel that has not been
         recovered (i.e. till control channel has not been reset) is
         siliently discarded.

         The procedure described in this document does not specifically
         consider the scenario of both endpoints failing simultaneously.
         In such situations, an endpoint MAY assume that the recovery
         has failed.


      2.2.2 Control and Data Channel Reset

         Failed endpoint in Tunnel Recovery AVP (SCCRQ) indicates if it
         would like to reset control channel, and optionally data
         channel along with.  Data channel reset without control channel



Jain                        expires July 2004                   [Page 7]

INTERNET DRAFT                  FAILOVER                     August 2003


         reset uses the mechanism described in section 3.0 of this
         document.

         Control channel reset means flushing the transmit and receive
         windows, and resetting the control channel sequence numbers
         (i.e. Ns and/or Nr values). The control channel on failed
         endpoint is reset upon getting a valid SCCRP, whereas control
         path on non failed endpoint is reset upon getting a valid
         SCCCN. If an endpoint does not receive Suggested sequence
         number AVP in SCCRP then it MUST reset Ns and Nr values to
         zero. Similarly if non failed endpoint opts not to send
         suggested sequence number AVP then it MUST reset Ns and Nr
         values to zero.

         Data channel reset requires no action if data channel doesn't
         use sequence numbers. Whereas if data channel were using
         sequence numbers then the sequence numbers are reset as
         follows: - Failed endpoint MUST stop receiving and transmitting
         data packets on all sessions, before sending SCCRQ on the
         recovery tunnel.  - Failed endpoint resets Ns to zero. It also
         sets Nr from the Ns received in the first data packet after
         sending SCCCN on the recovery tunnel.  - After resetting Ns and
         Nr values, failed endpoint can start transmitting and receiving
         the data.  - Non failed endpoint reset the Nr to zero upon
         receipt of a valid SCCN.  It doesn't reset the Ns value.

         After resetting the control channel, it MUST allow sending and
         receiving various control messages including new session
         establishments.

      2.2.3 Begin Session Synchronization Timer

         Once the tunnel recovery is done i.e. control/data channel
         is(are) reset, each endpoint starts Session Synchronization
         Timer, value of which is indicated by the peer in Tunnel
         Recovery AVP. When this time expires it starts the Post
         Failover process described in section 2.4


   2.3 Session State Synchronization

      During failure it is likely to have two endpoints disagree on the
      existence/state of a session. Therefore it becomes very important
      for the two endpoints to agree upon the sessions that they are
      going to preserve in a tunnel. If failover happens while a session
      is being established or being torn down, it is possible that one
      of the endpoints consider the session in the established state
      where as its peer consider the same session to be down or non



Jain                        expires July 2004                   [Page 8]

INTERNET DRAFT                  FAILOVER                     August 2003


      existent.  Two such situations occur when an endpoint fails after
      sending:
      - A CDN message that never made to the peer.
      - An ICCN message that never made to to the peer.

      Session State inconsistency applies only for control channel
      failure not data channel failure.

      Following mechanism is proposed to identify and clear the sessions
      that exists on an endpoint but non existent on its peer.

      - After the recovery tunnel is established, the sessions that were
      not in established state are silently cleared i.e. without sending
      a CDN message to the peer.

      - Both endpoints SHOULD identify the sessions that might have been
      in inconsistent states, perhaps based on data channel inactivity.

      - After identifying the suspect sessions, an endpoint requests its
      peer the state of these sessions by sending a new message, message
      type [TBD], called as Failover Session Query (FSQ) message.  This
      message MUST include at least one Failover Session State AVPs.  An
      endpoint may send another FSQ messages on the recovered tunnel
      before getting a response for the first FSQ.  Failover Session
      State AVP is described as follows:

      While the set of established sessions is synchronized among two
      endpoints, it is possible to get an ICRQ for a session an endpoint
      beleive is already in established state. It MUST respond it with a
      CDN and clear the session on its end.

      Failover Session State AVP

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |M|H| rsvd  |      Length       |           Vendor Id [IETF]    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |      Attribute Type [TBD]     |            Session Id         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        Remote Session Id      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      This AVP MAY be hidden (the H-bit set to 0 or 1). The AVP is
      mandatory (the M-bit is set to 1).

      Session Id identifies the local session id sender had assigned,
      for which it would like to query the state on its peer.  Remote
      Session Id is the remote session id for the same session.



Jain                        expires July 2004                   [Page 9]

INTERNET DRAFT                  FAILOVER                     August 2003



      - If an endpoint receives an FSQ message, it responds with
      Failover Session Response (FSR) message, message type [TBD], that
      has one Failover Session State AVP for each requested AVP in FSQ.
      For each Failover Session State AVP received in FSQ message, it
      MUST find out if the Remote Session Id is a valid existing local
      session id and that it is paired with the Session Id specified in
      the message.  If it discovers that the session is non-existing it
      MUST respond back with a Failover Session State AVP in FSR message
      with Session Id field set to zero, and Remote Session Id value set
      to the received value of Session Id in the corresponding AVP in
      the FSQ message.

      - When an endpoint receives an FSR message, it MUST use the Remote
      Session Id field to identify the local session and silently
      (without sending a CDN) clean the session if Session Id is set to
      zero. Otherwise it considers the session to be in established
      state and recovered.

      - FSQ and FSR messages SHOULD not be entertained after Recovery
      time has elapsed.

      - FSQ and FSR Messages MAY include Challenge and Challenge
      Response AVPs as defined by section 5.1.1 [L2TP] to authenticate
      the peer.


   2.4 Post Failover Cleanup

      This process is triggered when Recovery time has elapsed since the
      control and data channel were reset. Cleanup process does
      following:
      - Teardown recovery tunnels if they are still established.
      - Stop receiving FSQ and FSR messages from the peer.
      - Cleanup any remaining stale sessions. Sessions that are
      responded by the peer in FSR message to be up, are not considered
      stale even when data channel inactivity is observed.
      - Other resources acquired to start failover process.


   3.0 Data Channel Only Failure

      Mechanism described in section 2.0 MUST not be used to reset the
      data channel failure alone. If an endpoint receives an SCCRQ with
      Tunnel Recovery AVP that doesn't have 'C' bit set then it MUST
      terminate the tunnel.




Jain                        expires July 2004                  [Page 10]

INTERNET DRAFT                  FAILOVER                     August 2003


      Data failure channel reset is not needed when sequence numbers are
      not used. Two endpoints reset the data channel failure by sending
      a new message, Data Channel Failure (DCF) message over the
      existing control channel.


4. IANA Considerations

   This document requires four new "AVP Attributes" and three new
   messages to be assigned through IETF Consensus [RFC2434] as indicated
   in Section 10.1 of [RFC2661]. These are:

         Failover Capability AVP (section 2.1)

         Tunnel Recovery AVP (section 2.2.1)

         Suggested Control Sequence AVP (section 2.2.1)

         Failover Session State AVP (section 2.3)

         Failover Session Query Message (FSQ) (section 2.3)

         Failover Session Response Message (FSR) (section 2.3)

         Data Channel Failure Message (section 3.0)

5. Security Considerations

   The failover mechanism described here leaves a some room (1 in 2^32)
   for an intruder to discover the old tunnel id of an existing tunnel
   by trying out various possibilities in Recovery Tunnel Id and
   Recovery Remote Tunnel Id AVP.

   It also introduces an opportunity for an intruder to spoof the
   FSQ/FSR messages and know the active sessions.

6. Acknowledgements

   Leo Huber of Extreme Networks provided valuable suggestions to help
   define the failover concept.  Ly Loi reviewd the draft and provided
   suggestions on improving it.

8. Author Information


      Vipin Jain
      Riverstone Networks
      5200 Great America Parkway
      Santa Clara, CA 95054
      Phone: +1 408.655.9115
      Email: vipinietf@yahoo.com



Jain                        expires July 2004                  [Page 11]

INTERNET DRAFT                  FAILOVER                     August 2003



      Paul W. Howard
      Juniper Networks
      10 Technology Park Drive
      Westford, MA 01886
      Email: phoward@juniper.net

      Keyur Parikh
      Sentito Networks
      238 Littleton Road Suite 101
      Westford, MA 01886
      Phone: +1 978.399.0223
      Email: kparikh@sentito.com

      W. Mark Townsley
      Cisco Systems
      7025 Kit Creek Road
      PO Box 14987
      Research Triangle Park, NC 27709
      Email: townsley@cisco.com


8. References

   [L2TP] Townsley, et. al., "Layer Two Tunneling Protocol L2TP", RFC2661


Appendix A

This section describes some design considerations that came up during
discussions when developing the proposal:

   A.1  Backward compatibility and extensibility

      -  The mechanism should be backwards compatible; i.e. it should
      not redefine existing behavior of [L2TP] compliant systems.

      - The protocol should allow a peer to detect failover capabilities
      in advance, for it to fall back to other failover mechanisms
      should peer does not support proposed failover protocol.

      - The protocol should allow future extensions to fail-over
      mechanism at ease.





Jain                        expires July 2004                  [Page 12]

INTERNET DRAFT                  FAILOVER                     August 2003


   A.2  Less failover recovery time

   The mechanism should have least possible time to recover from
   failover (target of 3-5 seconds for 30k tunnels). Specifically it
   should take following into consideration:

      - Faster recovery: by utilizing less number of messages exchanged
      to recover from failover

      - CPU intensiveness: less cpu intensive a proposal is, better are
      the changes of faster recovery

      - Parallel establishment of various tunnels: by keeping different
      tunnel reestablishments independent of one another.

   A.3  Less Payload data loss

   The mechanism should have least possible impact on data flows for
   sessions with sequencing enabled.

   A.4  Minimum interference with pre-failure control traffic

   The mechanism should define a way of clearly distinguishing the
   messages that were sent before failover from that which are sent
   after.  Specifically, it should define a mechanism that avoid
   confusion between sequence numbers that were used before and after if
   the same Tunnel Id is used.

   A.5  Simplicity

   Simpler the protocol is, better are the changes of being adopted by
   everybody. Following would help achieve this:

      - Use of existing AVPs, messages and packet formats.

      - Avoid introducing special considerations and mechanisms a new
      implementation would have to deal with.

      - Simpler post fail-over synchronization mechanism.


   A.6  Security

   The mechanism should provide a mechanism to authenticate peers when
   resynchronization is happening after a failover.





Jain                        expires July 2004                  [Page 13]

INTERNET DRAFT                  FAILOVER                     August 2003


   A.7 Scalability

   It is very important for a proposed protocol to work well for a
   scalable deployment. This includes dealing with all design
   considerations discussed above for scalable deployments, having
   thousands of tunnels or sessions or mix of the two.

   A target of 30,000 tunnels carrying 150,000 to 200,000 sessions from
   300 peers was considered during the design.


Appendix B

   Figure below outlines the the failover protocol operation for an
   example tunnel. The failover protocol does not preclude an endpoint
   from recovering multiple tunnels in parallel. It also allows an
   endpoint from sending multiple FSQs to recover quickly.

      Pre Failover Exchange (section 2.1):

      Endpoint                                             Peer
                   (assigned tid = x, failover capable)
      SCCRQ       -------------------------------------->  validate SCCRQ

                   (assigned tid = y, failover capable)
      validate    <--------------------------------------  send SCCRP
      SCCRP, etc.

      .... <after tunnel gets created, sessions are established> ....


      < This Node fails >

      Failed endpoint establishes recovery tunnel (section 2.2.1).
      Initiate recovery tunnel establishment for the old tunnel 'x':

      Failed Endpoint                                      Peer

                (assigned tid = z, Recovery AVP)
      SCCRQ     ----------------------------------->  Detects failover
              (recover tid = x, recover remote tid = y)  validate SCCRQ


               (assigned tid = w, opt. Suggested Seqence AVP)
      validate <-----------------------------------   send SCCRP
      SCCRP    (recover tid = y, recover remote tid = x)
      reset Ns/Nr

      SCCN      ----------------------------------->  validate and reset
                                                      the old tunnel.



Jain                        expires July 2004                  [Page 14]

INTERNET DRAFT                  FAILOVER                     August 2003


      Start session synchronization timer (section 2.2.3)

      Session states are synchronized both endpoints may send FSQs and
      cleanup stale sessions (section 2.3)

                 (FSS AVP for sessions s1, s2, s3..)
      send FSQ  -------------------------------------> compute the state
                                                       of sessions in FSQ

                 (FSS AVP for sessions s1, s2, s3...)
      deletes  <-------------------------------------- send FSR
      stale sessions, if any


                 (FSS AVP for sessions s7, s8, s9...)
      compute  <-------------------------------------- send FSQ
      the sate of
      sessions in FSQ


                 (FSS AVP for sessions s7, s8, s9...)
      send FSR --------------------------------------> delete stale sessions,
                                                       if any


      Session Sync Time expires, Start Post Failover process (section 2.4)

      Cleanup and terminate tid = 'z'
      StopCCN  --------------------------------------> Cleanup 'w'

      Stop receiving and sending FSQs and FSRs.
      Cleanup sessions that are still stale within the tunnel.



















Jain                        expires July 2004                  [Page 15]

--0-683355829-1075284693=:52645--

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



