Re: Advancing the Protocol and Morin Drafts

"Alia Atlas" <akatlas@gmail.com> Thu, 09 October 2008 10:03 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 906AB3A6944; Thu, 9 Oct 2008 03:03:59 -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 16A293A69E0 for <l3vpn@core3.amsl.com>; Thu, 9 Oct 2008 03:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 5qGcxgO8Q9+0 for <l3vpn@core3.amsl.com>; Thu, 9 Oct 2008 03:03:57 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by core3.amsl.com (Postfix) with ESMTP id C98F33A69B4 for <l3vpn@ietf.org>; Thu, 9 Oct 2008 03:03:56 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so2932669fga.41 for <l3vpn@ietf.org>; Thu, 09 Oct 2008 03:04:39 -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:in-reply-to:mime-version:content-type:references; bh=0OY4/tdbd5Z4noTzP7eBzXoB9jNnZRg44Q4OBgl+qWY=; b=S8sDG0lThlTDfNeD975STVBLAm7ASSmtWVoqfu1b2M4nkQhYKXCqOjKHXm/e7UfYWL ufG3CYMCMYoh7CIenEKJEL5tHN/A3TO4hL0TjjecGiJ4ZYDva2YQNrz4zsCfyTQwm3bq QQfMU4WaUkQ8pNneQl6AkSQUB63PlGGmgdS4c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=QcfmcnRj0ztzjsRdotG1ongqtc43mstb36cdq//w/s3Fy61oPoucZOwZwZAsSyTcOX n5SHkVEbRpnrByssZSATEx9J61Tv6jCGV7HuB59VQ/zS8d9y9OqQIutoEIsdoPoweGc4 XxCBwfBswIKU8tpauedVmLObxxLm7O1D3/MWc=
Received: by 10.86.26.11 with SMTP id 11mr15412fgz.12.1223546679102; Thu, 09 Oct 2008 03:04:39 -0700 (PDT)
Received: by 10.86.35.17 with HTTP; Thu, 9 Oct 2008 03:04:38 -0700 (PDT)
Message-ID: <6280db520810090304j5943526bub0c5629a97127f53@mail.gmail.com>
Date: Thu, 09 Oct 2008 06:04:39 -0400
From: Alia Atlas <akatlas@gmail.com>
To: l3vpn@ietf.org
Subject: Re: Advancing the Protocol and Morin Drafts
In-Reply-To: <620fd17c0810081756v48b389dar3624d8e153ced0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_20986_4903170.1223546679113"
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com> <620fd17c0810081756v48b389dar3624d8e153ced0@mail.gmail.com>
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.

Alia


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