Re: Advancing the Protocol and Morin Drafts

"Paul Wall" <pauldotwall@gmail.com> Thu, 09 October 2008 00:55 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 DE7303A6889; Wed, 8 Oct 2008 17:55:39 -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 927533A6889 for <l3vpn@core3.amsl.com>; Wed, 8 Oct 2008 17:55:38 -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 MKIt99jq8o54 for <l3vpn@core3.amsl.com>; Wed, 8 Oct 2008 17:55:37 -0700 (PDT)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.176]) by core3.amsl.com (Postfix) with ESMTP id C15B73A6805 for <l3vpn@ietf.org>; Wed, 8 Oct 2008 17:55:37 -0700 (PDT)
Received: by el-out-1112.google.com with SMTP id v27so886370ele.13 for <l3vpn@ietf.org>; Wed, 08 Oct 2008 17:56:19 -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=aHnxH1NcTc8QYlg959r7vygdxRRHpVIBaQWfe7YTWzg=; b=Eb9ZCU+1/0QbZwg7+FI5nHujWxuMblJyuMdhKAPzyyBpeSUoeTs5qUdilLAGHrgTd/ ljrC2CTD3p8drDUZzaghNyCc1zZ++xa5s+6BbkgrH2Y+edzAUIC4cS0SMBXM2AEm3We6 NRN0F/l/1Jn497Fp1xL1s6+fxXx/LkusiIhbc=
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=FWQA0lo2h5p1+O6MuVTJVtsaF+pTix1+KygYSuV5X6hCLS/CLMYPxdCxYX/2rmbRpA vX2rJpfK4Y1yvcWS+bDow5mRX1Eqx96gPcsrYaOYZmPNrKX0UBujXfuEHIL7sDESSM13 jOzkpHlt97DnqB4j2jFeFjYOwOxTC2OyTVt44=
Received: by 10.90.119.20 with SMTP id r20mr10201662agc.74.1223513779232; Wed, 08 Oct 2008 17:56:19 -0700 (PDT)
Received: by 10.90.84.3 with HTTP; Wed, 8 Oct 2008 17:56:19 -0700 (PDT)
Message-ID: <620fd17c0810081756v48b389dar3624d8e153ced0@mail.gmail.com>
Date: Wed, 08 Oct 2008 20:56:19 -0400
From: Paul Wall <pauldotwall@gmail.com>
To: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: Advancing the Protocol and Morin Drafts
In-Reply-To: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.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>
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

Support.

Drive slow,

Paul Wall.


On 10/1/08, Marshall Eubanks <tme@multicasttech.com> wrote:
> 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
>
>