RE: New Version Notification for draft-gs-vpn-scaling-02.txt

"George, Wes" <wesley.george@twcable.com> Thu, 21 March 2013 19:36 UTC

Return-Path: <wesley.george@twcable.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4CF321F857E for <l3vpn@ietfa.amsl.com>; Thu, 21 Mar 2013 12:36:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.487
X-Spam-Level:
X-Spam-Status: No, score=0.487 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwtgxkSkD9-w for <l3vpn@ietfa.amsl.com>; Thu, 21 Mar 2013 12:36:41 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id C64DD21F856E for <l3vpn@ietf.org>; Thu, 21 Mar 2013 12:36:40 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,888,1355115600"; d="scan'208";a="45260247"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 21 Mar 2013 15:36:09 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Thu, 21 Mar 2013 15:36:39 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "l3vpn@ietf.org" <l3vpn@ietf.org>
Date: Thu, 21 Mar 2013 15:36:38 -0400
Subject: RE: New Version Notification for draft-gs-vpn-scaling-02.txt
Thread-Topic: New Version Notification for draft-gs-vpn-scaling-02.txt
Thread-Index: Ac3frcXbuYRlrsEzSiW1a4+SulKhpQg5PFGACXYYHNA=
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923041FC41729@PRVPEXVS15.corp.twcable.com>
References: <20121221190248.7928.43288.idtracker@ietfa.amsl.com> <2671C6CDFBB59E47B64C10B3E0BD5923033DAE7041@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033DAE7041@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 19:36:41 -0000

Hello all -

After our presentation at IETF86, we wanted to follow up with a request for feedback on this draft.

We think it would make sense as an L3VPN WG document, but didn't get good guidance as to whether it's ready for that or not.

Thanks,

Wes



> -----Original Message-----
> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
> Of George, Wes
> Sent: Friday, February 01, 2013 10:47 AM
> To: l3vpn@ietf.org
> Subject: FW: New Version Notification for draft-gs-vpn-scaling-02.txt
>
> Rob Shakir and I updated this draft last month, but I just realized that
> we never sent notification to the list that we had done so. We believe
> that this incorporates all of the feedback we've received thus far, and
> would like to discuss the future of the draft - whether it should be
> adopted as a WG doc in L3VPN, or if perhaps it is better off as an
> individual document, or an OpsArea document or something. It's also
> worth asking whether there is value in discussing it in Orlando or if we
> can just continue discussion on-list.
>
> I'd also like to solicit help bolstering the multicast scale section of
> the document, either in text contributions or in pointers on areas we
> need to cover, things we should read, etc.
>
> And of course additional review comments are always welcome. :-)
>
> Thanks
> Wes George and Rob Shakir
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, December 21, 2012 2:03 PM
> To: George, Wes
> Cc: rob.shakir@bt.com
> Subject: New Version Notification for draft-gs-vpn-scaling-02.txt
>
>
> A new version of I-D, draft-gs-vpn-scaling-02.txt has been successfully
> submitted by Wesley George and posted to the IETF repository.
>
> Filename:        draft-gs-vpn-scaling
> Revision:        02
> Title:           IP VPN Scaling Considerations
> Creation date:   2012-12-21
> WG ID:           Individual Submission
> Number of pages: 29
> URL:             http://www.ietf.org/internet-drafts/draft-gs-vpn-
> scaling-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-gs-vpn-scaling
> Htmlized:        http://tools.ietf.org/html/draft-gs-vpn-scaling-02
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-gs-vpn-scaling-
> 02
>
> Abstract:
>    This document discusses scaling considerations unique to
>    implementation of Layer 3 (IP) Virtual Private Networks, discusses a
>    few best practices, and identifies gaps in the current tools and
>    techniques which are making it more difficult for operators to cost-
>    effectively scale and manage their L3VPN deployments.
>
>
>
>
> The IETF Secretariat
>


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.