IETF Logo Mail Archive

Re: Advancing the Protocol and Morin Drafts

"Paul Wall" <pauldotwall@gmail.com> Fri, 10 October 2008 17:51 UTC

Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7915B3A697B; Fri, 10 Oct 2008 10:51:09 -0700 (PDT)
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C7773A697B for <l3vpn@core3.amsl.com>; Fri, 10 Oct 2008 10:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ruLNcMWoEQqB for <l3vpn@core3.amsl.com>; Fri, 10 Oct 2008 10:51:07 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com [209.85.217.16]) by core3.amsl.com (Postfix) with ESMTP id 9AFBD3A689F for <l3vpn@ietf.org>; Fri, 10 Oct 2008 10:51:07 -0700 (PDT)
Received: by gxk9 with SMTP id 9so1055929gxk.13 for <l3vpn@ietf.org>; Fri, 10 Oct 2008 10:51:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=L8RmbbzLDgZVa+hu+QqB3jhhQDjIeECCLLL2Mbrq9l0=; b=aaP71dgUxHS67PXWtcH19FuJ1eH/wNqrdY/YiCxNtS2FHkzsIBOxpQEmyj7frBiFOl 6gqDwJAkgI+50TT8fxfmDcGhbwd4LDG9xXur9SxqhIMsBlrkM6C45nWVMZptaPqyBr0+ gShRF7T8ae/llgYtrLKae3qHsBZIROCHtixis=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=KNgmqifmrtC0Gwwg9Nt0GK32r0vYxo/g6juU9xEoviMCD8ubILotQ4te4pCpmR+FRA VokPGi9J3aorBMvLuWsFVPEzRDc+ZLW5aySr0TMxNuFIByfL/W+yTUvSqk9BkiXGZsD6 Ep80kpBcjuQhy6V3g1pxwB/Iy8kjpyb48+D+Q=
Received: by 10.90.68.20 with SMTP id q20mr2062204aga.93.1223661112524; Fri, 10 Oct 2008 10:51:52 -0700 (PDT)
Received: by 10.90.84.3 with HTTP; Fri, 10 Oct 2008 10:51:51 -0700 (PDT)
Message-ID: <620fd17c0810101051waf03f8cse85cfacd17f38eb4@mail.gmail.com>
Date: Fri, 10 Oct 2008 13:51:51 -0400
From: Paul Wall <pauldotwall@gmail.com>
To: "SZELA, MATEUSZ W (MATT), ATTLABS" <mszela@att.com>
Subject: Re: Advancing the Protocol and Morin Drafts
In-Reply-To: <36DFD543D58B094ABD058E71793263E6E1803B@misout7msgusr7b.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com> <36DFD543D58B094ABD058E71793263E6E1803B@misout7msgusr7b.ugd.att.com>
Cc: Ross Callon <rcallon@juniper.net>, l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

I'm not sure this draft is worth advancing either.

In fact, I'm not sure it's worth the paper it's printed on.

Drive Slow,
Paul Wall

On 10/9/08, SZELA, MATEUSZ W (MATT), ATTLABS <mszela@att.com> wrote:
>  Marshall & Danny et al,
>
> I do NOT SUPPORT this draft.
>
> The proposed draft, does not consider the needs and requirements of
> large Service Providers with huge MVPN deployed base that services
> critical business customers.
>
> The correct approach is to poll Service Providers, who use MVPN now,
> first and agree on a set of requirements that consider the needs of the
> SP and end customers.
> The requirements must consider the needs of the Business Customers who
> use large SP MVPN networks.
>
>
> Tx,
>
> Matt W. Szela
> Director,
> New Technology Product Dev. Eng.
> AT&T Laboratories
> mszela@att.com
> v: 732-420-6828
> c: 732-208-5341
>
> -----Original Message-----
> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
> Of Marshall Eubanks
> Sent: Wednesday, October 01, 2008 10:04 AM
> To: l3vpn@ietf.org
> Cc: Ross Callon
> Subject: Advancing the Protocol and Morin Drafts
>
> This email starts a 3 week call for input, to expire October 23, 2008,
> for the following steps:
>
> 1.) To accept draft-morin-l3vpn-mvpn-considerations-03 as a working
> group document;  and
>
> 2.) To turn this document into a requirements draft, with mandatory to
> implement features for an interoperable implementation. The authors
> have indicated that they are willing to do this.
>
> Our intention is, if this approach is accepted, to then begin WG last
> call to submit to the IESG for publication:
>
> draft-ietf-l3vpn-2547bis-mcast
> draft-ietf-l3vpn-2547bis-mcast-bgp
>
> We expect that these two documents will be submitted more or less as is
> (i.e., certainly with any new bug fixes or other necessary corrections
> and
> improvements, but without specific mandatory to implement feature
> description in those drafts).
>
> Please respond to the list with your recommendations for these two
> courses of action.
>
> Regards
> Marshall & Danny
>
>

v2.39.1 | Report a Bug | By Email | System Status