[Mavs] Additional comments to the requirements draft

Christian Jacquenet <christian.jacquenet@gmail.com> Thu, 20 October 2005 12:46 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESZoN-0004co-UX; Thu, 20 Oct 2005 08:46:24 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESYGX-0005v5-TP for MAVS@megatron.ietf.org; Thu, 20 Oct 2005 07:07:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02517 for <mavs@ietf.org>; Thu, 20 Oct 2005 07:07:12 -0400 (EDT)
Received: from qproxy.gmail.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESYSR-0003xB-FB for mavs@ietf.org; Thu, 20 Oct 2005 07:19:41 -0400
Received: by qproxy.gmail.com with SMTP id a10so2285qbd for <mavs@ietf.org>; Thu, 20 Oct 2005 04:07:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=JMeAVhUw0x7mBTag+sX63Akc8bBALe4uAWEPh1lRPaWSDK6+ekxNwd8f1tYv/1iF4JWXsrDiIo7N8/2c1AkxrErVsMOt96830EJ9wLEf7bKTGDsqLaIMXd7LXYzknKPkJHSHsMpDJR9MYFwr/oQXVbNG92hTKQQdaYuCMNJph7s=
Received: by with SMTP id r6mr1389311qbp; Thu, 20 Oct 2005 04:07:16 -0700 (PDT)
Received: by with HTTP; Thu, 20 Oct 2005 04:07:16 -0700 (PDT)
Message-ID: <642f97440510200407x5171a274r@mail.gmail.com>
Date: Thu, 20 Oct 2005 13:07:16 +0200
From: Christian Jacquenet <christian.jacquenet@gmail.com>
To: mavs@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_680_17078442.1129806436079"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6a34278ad1b4706c4fcd262770db55c8
X-Mailman-Approved-At: Thu, 20 Oct 2005 08:46:22 -0400
Cc: Christian - GMail <christian.jacquenet@gmail.com>
Subject: [Mavs] Additional comments to the requirements draft
X-BeenThere: mavs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiprovider End-to-end VPN Services <mavs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mavs>, <mailto:mavs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mavs>
List-Post: <mailto:mavs@ietf.org>
List-Help: <mailto:mavs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mavs>, <mailto:mavs-request@ietf.org?subject=subscribe>
Sender: mavs-bounces@ietf.org
Errors-To: mavs-bounces@ietf.org

Dear all,

Please find herein another shot of comments to the aforementioned document,
in addition to those provided by Dimitri (Word revision marks and colored
text). In a nutshell:

1. I strongly encourage the co-authorship of this document by one or more SP
2. Some of the terminology is rather confusing: e.g. I think the notion of
"MNE operator" is highly arguable, because I don't think there will be such
a meta-organization. Rather, I would replace this notion by "a community of
(VPN) service providers that use and operate the (entwork) resources of a
MNE facility to deploy and exploit a VPN service offering".
3. The "E2E" wording is also confusing in several places of the document:
for example, I don't understand the notion of "E2E service policy". I'd
rather talk about the enforcement of a set of (hopefully) consistent
policies (including but not necessarily limited to) addressing, routing,
QoS, security policies) for the provisioning of an inter-domain VPN service
that will comply with the requirements that may have been negotiated between
a customer and the aforementioned community.

Finally, I can see as per the latest version of the IETF64 agenda that there
won't be a mavs BoF in Vancouver: shall we arrange a "bar BoF" instead,
discuss the charter and agree upon Dallas as the milestone for setting up
the IESG-approved BoF? I'll be in Vancouver from Nov. 5 and leave on Nov.


Mavs mailing list