[Mavs] (no subject)

"David Page" <dpage@nexagent.com> Fri, 03 February 2006 18:44 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F55vF-0004y9-Am; Fri, 03 Feb 2006 13:44:41 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F55vC-0004py-Sg for MAVS@megatron.ietf.org; Fri, 03 Feb 2006 13:44:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28197 for <mavs@ietf.org>; Fri, 3 Feb 2006 13:42:39 -0500 (EST)
Received: from hostedexchange.hostedservice.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F566T-000724-SK for mavs@ietf.org; Fri, 03 Feb 2006 13:56:20 -0500
Received: from THHS2EXBE2X.hostedservice2.net ([]) by hostedexchange.hostedservice.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 3 Feb 2006 18:44:12 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 03 Feb 2006 18:44:12 -0000
Message-ID: <B2B4D3618441D941B811329A672FD64E081AEA@THHS2EXBE2X.hostedservice2.net>
Thread-Index: AcYo8dI1zT//PnmRTki1l0FCS+nlSQ==
From: David Page <dpage@nexagent.com>
To: mavs@ietf.org
X-OriginalArrivalTime: 03 Feb 2006 18:44:12.0182 (UTC) FILETIME=[D32D2B60:01C628F1]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: [Mavs] (no subject)
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>
Content-Type: multipart/mixed; boundary="===============0032992998=="
Sender: mavs-bounces@ietf.org
Errors-To: mavs-bounces@ietf.org

I am interested in this alias' view of the following observation:
"Some operators tend to think of an MPLS interconnect as an NNI. Accordingly, they ascribe MPLS interconnects with commonly held attributes of NNIs; namely that NNIs are core network constructs that ideally maintain little or no customer-specific state or configuration. Diametrically opposed to this view are other operators. They see MPLS interconnect as a multi-enterprise hub site, an outsource of hub site capabilities, and therefore a point of customer-specific service creation and control. Both refer to MPLS interconnect; each are solving different problems."
Mavs mailing list