Re: [scale] Welcome to the MPLS VPN Scaling BoF preparation work

"Russ White" <russw@riw.us> Tue, 03 December 2013 17:05 UTC

Return-Path: <russw@riw.us>
X-Original-To: scale@ietfa.amsl.com
Delivered-To: scale@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA1A21A1F66 for <scale@ietfa.amsl.com>; Tue, 3 Dec 2013 09:05:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNUF-9kliG6s for <scale@ietfa.amsl.com>; Tue, 3 Dec 2013 09:05:12 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB651A1F4A for <scale@ietf.org>; Tue, 3 Dec 2013 09:05:12 -0800 (PST)
Received: from cpe-098-122-144-218.nc.res.rr.com ([98.122.144.218]:63417 helo=RussPC) by server.riw.us with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1VntP9-0006j3-Ql; Tue, 03 Dec 2013 17:05:00 +0000
From: "Russ White" <russw@riw.us>
To: "'Loa Andersson'" <loa@pi.nu>, <scale@ietf.org>, "'Lou Berger'" <lberger@labn.net>, "'Vero Zheng'" <vero.zheng@huawei.com>
References: <5296B02C.5090205@pi.nu>
In-Reply-To: <5296B02C.5090205@pi.nu>
Date: Tue, 3 Dec 2013 12:05:06 -0500
Message-ID: <04e201cef049$d1d3f190$757bd4b0$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQILtnVUN3nvWAsGsigg91eg1oO8gZnJI+Qw
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [scale] Welcome to the MPLS VPN Scaling BoF preparation work
X-BeenThere: scale@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MPLS VPN Scaling <scale.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scale>, <mailto:scale-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scale/>
List-Post: <mailto:scale@ietf.org>
List-Help: <mailto:scale-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scale>, <mailto:scale-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Dec 2013 17:05:15 -0000

> I've updated slide 2 mentioning number of pairwise associations and the
> management and configuration aspects.

You should also add rate of change, as that can actually be more important
than the number of tunnels, etc. The problem is going to be taking a
bulleted list and building it into a solid problem statement:

> We will need to converge on a problem statement, a tentative starting
point
> would be slide 2. We will need to help to create the problem statement.

Maybe:

Define and address scaling issues and solutions for large VPN deployments,
including the number of end points, number of reachable destinations, number
of multicast trees, length of path, and rate of change in the control plane
state.

The only thing is I don't know if the list needs to be this specific, or if
there should be a general description with specifics defined by the set of
drafts being proposed.

:-)

Russ