[Gen-art] Gen-ART Review of draft-ietf-l3vpn-ce-based-03.txt

Harald Alvestrand <hta@google.com> Thu, 14 September 2006 10:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GNo1b-0002Wz-1O; Thu, 14 Sep 2006 06:00:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GNmaf-0005P8-Jl for gen-art@ietf.org; Thu, 14 Sep 2006 04:28:57 -0400
Received: from smtp-out.google.com ([216.239.45.12]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNmae-0006tI-7N for gen-art@ietf.org; Thu, 14 Sep 2006 04:28:57 -0400
Received: from zps76.corp.google.com (zps76.corp.google.com [172.25.146.76]) by smtp-out.google.com with ESMTP id k8E8S919007089; Thu, 14 Sep 2006 01:28:10 -0700
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:user-agent:mime-version:to:cc: subject:content-type:content-transfer-encoding; b=UMqLrOqW3/xCltu6AoUe4mZ2pGpAk1S2SqpiiBRJYo7gWi2qkBDkxJivxLdfDIX6w kTvW/SBZKWobk1olsveQg==
Received: from [172.28.60.15] (hod.trd.corp.google.com [172.28.60.15]) by zps76.corp.google.com with ESMTP id k8E8Rvm7005413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 Sep 2006 01:27:59 -0700
Message-ID: <4509128D.1050104@google.com>
Date: Thu, 14 Sep 2006 01:27:57 -0700
From: Harald Alvestrand <hta@google.com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060719)
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.3 (----)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-Mailman-Approved-At: Thu, 14 Sep 2006 06:00:50 -0400
Cc: jeremy.de_clercq@alcatel.be, Rick Wilder <rick.wilder@alcatel.com>, cliff.wang@us.army.mil, olivier.paridaens@alcatel.be, Mark Townsley <townsley@cisco.com>
Subject: [Gen-art] Gen-ART Review of draft-ietf-l3vpn-ce-based-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

I am the Gen-ART assigned Last Call reviewer for 
this draft pair: draft-ietf-l3vpn-ce-based-03 and draft-declercq-dl3vpn-ce-based-as

	For background on Gen-ART, please see the FAQ at:

	http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-l3vpn-ce-based-03.txt, draft-declercq-l3vpn-ce-based-as-00.txt
Reviewer: Harald Alvestrand
Date: September 14, 2006
Summary: Mostly harmless

My biggest concern with this class of specification is that it doesn't specify anything.
As I read it, it's basically a primer on the things you have to think about when creating a VPN based on Customer Edge equipment - you have to provision them from somewhere (using an unspecified protocol), you have to think about how to give them Internet access, you have to secure traffic between the devices so that nobody else can snoop on them, and you have to throw away traffic that isn't what you expected it to be. Motherhood and apple pie, and I'm sure there's a target audience for this stuff.

But there is no protocol here, there is no requirements language, there is nothing by which one can test that a particular implementation of such a VPN behaves like an "IETF-defined CE-based PPVPN", and there is not even the beginning of requirements for interoperability between vendors of CE-based VPN equipment.
The most you can say is that some approaches (such as VPN over SSH) aren't part of this model.

I think the documents are coherent, well written, readable, and probably useful for some target audience.

But I am hard pressed to figure out why such documents belong even in the vicinity of the IETF standards track.
I'm happy to let these two documents out as Informational. I think any such document belongs in that class.

But I suspect the political waters here are deep and troubled. I wish the WG chairs and the ADs the best of luck in navigating them.

No nits worth mentioning.

                          Harald




_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art