RE: [L2tpext] draft-galtzur-l2tpext-gr-01.txt and draft-ietf-l2tpext-failover-02.txt

"Tom Mistretta" <tmistretta@juniper.net> Tue, 27 January 2004 17:13 UTC

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.  

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