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

"George Swallow (swallow)" <swallow@cisco.com> Fri, 01 February 2013 17:52 UTC

Return-Path: <swallow@cisco.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 A062721E80CD for <l3vpn@ietfa.amsl.com>; Fri, 1 Feb 2013 09:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.299
X-Spam-Level:
X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lnCW0eQKN+uT for <l3vpn@ietfa.amsl.com>; Fri, 1 Feb 2013 09:52:44 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id BC3EE21E808C for <l3vpn@ietf.org>; Fri, 1 Feb 2013 09:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3289; q=dns/txt; s=iport; t=1359741165; x=1360950765; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=xn3DZwAN/H5b1lG4KNPb8ZeMhZoU+7Gr24JNl4ozb4I=; b=aKADoMB6PlIVd5JutPjKQxqfx83FTNJySyBuCM8KlpU+7g8sDbMF4Vq9 Q6MACLqa3Ddty52pO9tgSJyhlEOX8qru8WtYIOvv29JjOK6BUwer7Npbq fdErQt0WOrMyzu96YUF/wqZgQgM9G77mlqjQSzBeYlrCyjw34OS1WIQm4 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAK7/C1GtJV2Z/2dsb2JhbABFg3e7NhZzgh4BAQEEOjgFAgwGAQgRBAEBCxQJORQJCAEBBAENBQgBiAgHBcMLjQsbg0dhA5c0jzOCfIFvNQ
X-IronPort-AV: E=Sophos;i="4.84,579,1355097600"; d="scan'208";a="171845896"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 01 Feb 2013 17:52:44 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r11HqhHO022497 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Feb 2013 17:52:44 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.229]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Fri, 1 Feb 2013 11:52:43 -0600
From: "George Swallow (swallow)" <swallow@cisco.com>
To: "George, Wes" <wesley.george@twcable.com>, "l3vpn@ietf.org" <l3vpn@ietf.org>
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+SulKhpQg5PFGAAAamMYA=
Date: Fri, 01 Feb 2013 17:52:43 +0000
Message-ID: <2FE467D3673DCE409A84D67EC2F607BB0F72C81F@xmb-rcd-x10.cisco.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:
user-agent: Microsoft-MacOutlook/14.3.0.121105
x-originating-ip: [10.86.244.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <188660367DC90545B31E3B1E516C28AC@cisco.com>
Content-Transfer-Encoding: quoted-printable
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: Fri, 01 Feb 2013 17:52:45 -0000

George -

The convention for naming drafts is that the third word (as delineated by
hyphens) is the name of the Working Group that the draft is targeted to.
If you follow the convention then notifications are automatically sent.

In you case you could call it either

draft-gs-l3vpn-scaling or

draft-gs-l3vpn-vpn-scaling


George

On 2/1/13 10:47 AM, "George, Wes" <wesley.george@twcable.com> wrote:

>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.