Re: L3VPN WG Status/Action Register
Marshall Eubanks <tme@multicasttech.com> Thu, 04 September 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 66A883A696E; Thu, 4 Sep 2008 10:51:38 -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 77D143A67AC for <l3vpn@core3.amsl.com>; Thu, 4 Sep 2008 10:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.844
X-Spam-Level:
X-Spam-Status: No, score=-102.844 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 42YkSTT-5Kwt for <l3vpn@core3.amsl.com>; Thu, 4 Sep 2008 10:51:35 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 3E6823A696E for <l3vpn@ietf.org>; Thu, 4 Sep 2008 10:51:35 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 12817423; Thu, 04 Sep 2008 13:51:28 -0400
Message-Id: <6337F31A-C29C-4985-AA42-B646C5A30350@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
In-Reply-To: <8c99930d0809041015p33d1c7a7g628416382c469d97@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: L3VPN WG Status/Action Register
Date: Thu, 04 Sep 2008 13:51:27 -0400
References: <1CDCBD5B-D3F8-4250-9EE3-F23D2C056891@tcb.net> <8c99930d0809041015p33d1c7a7g628416382c469d97@mail.gmail.com>
X-Mailer: Apple Mail (2.926)
Cc: l3vpn@ietf.org, Danny McPherson <danny@tcb.net>
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
Dear Andy; On Sep 4, 2008, at 1:15 PM, Andrew G. Malis wrote: > Danny, > > Regarding draft-ietf-l3vpn-ipsec-2547, while I can understand the > motivation, in the absence of deployments I certainly wouldn't mind to > see it killed as an unneccessary distraction for the WG and an > unnecessary option in vendor equipment. But if there are operational > deployments, We are not aware of any deployments of this draft. If anyone knows differently, now would be a good time to speak up. Regards Marshall > then I see the usefulness of having an RFC to allow > multivendor interoperability. > > Cheers, > Andy > > On Thu, Sep 4, 2008 at 12:27 PM, Danny McPherson <danny@tcb.net> > wrote: >> Team, >> A few of you have nudged Marshall and I over the past >> couple weeks, either about drafts that have finished some >> form of call for feedback, or the lack of queries to the >> mailing list for accepting other documents, or precisely how >> to phrase questions related to tough MVPN issues, or some >> mix of the above. >> >> Given the wrap-up of the Dublin meeting at the beginning >> of August, and the perception that a heavy IETF work hiatus >> occurs cyclicly during the month of August, well, by request >> of both the ADs, and many within the WG, we've decided to >> extend current calls for feedback until SEP 12. We're also >> figuring out just how to approach the MVPN issues, working >> to determine what will be plausible to progress within the IETF >> framework and the IESG will support, with constant consult >> from the relative ADs. >> >> That said, just as a reminder we're on top of this, here's the >> list of the outstanding calls to the list, and if you have opinions >> that you have not shared already you should go back to the >> archives (or revisit your l3vpn unread message list) and comment >> appropriately. >> >> --- >> Call for adoption as WG document: >> >> o draft-mnapierala-mvpn-part-reqt-02 >> o draft-pmohapat-l3vpn-acceptown-community-00 >> o draft-pillay-esnault-moyer-ospfv3-pece-00 >> o *draft-rekhter-v6-ext-communities-02 >> o *draft-rekhter-as4octet-ext-community-03 >> >> * Some concerns about why not IDR, will discuss with >> relevant ADs and WG chairs. >> >> --- >> Call to kill this document: >> >> o draft-ietf-l3vpn-ipsec-2547 >> >> --- >> Action forthcoming: >> >> o Clarify any charter issues with "profiles" >> o Call to adopt draft-morin- as WG item >> o Proposal for progress path for MVPN - questions, etc.. >> >> --- >> If you have concerns about anything discussed above, or any >> documents or items that may be missing, please email Marshall >> and I ASAP. >> >> Thanks! >> >> -danny & Marshall >>
- L3VPN WG Status/Action Register Danny McPherson
- RE: L3VPN WG Status/Action Register Drake, John E
- Re: L3VPN WG Status/Action Register Andrew G. Malis
- Re: L3VPN WG Status/Action Register Marshall Eubanks
- Re: L3VPN WG Status/Action Register Danny McPherson