L2VPN (Re-)charter: Inter-AS (+ multicast)
Shane Amante <shane@castlepoint.net> Wed, 02 April 2008 22:46 UTC
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D8F43A695E; Wed, 2 Apr 2008 15:46:49 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB93F3A68EE for <l2vpn@core3.amsl.com>; Wed, 2 Apr 2008 15:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.866
X-Spam-Level:
X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
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 EzPaJDvZQVX6 for <l2vpn@core3.amsl.com>; Wed, 2 Apr 2008 15:46:47 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 0A9333A6951 for <l2vpn@ietf.org>; Wed, 2 Apr 2008 15:46:47 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id DF423268496; Wed, 2 Apr 2008 16:46:45 -0600 (MDT)
Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133]) (authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Wed, 02 Apr 2008 16:46:45 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133; client-port=34230; data-bytes=0
Message-ID: <47F40CD5.3000003@castlepoint.net>
Date: Wed, 02 Apr 2008 16:46:45 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: l2vpn@ietf.org
Subject: L2VPN (Re-)charter: Inter-AS (+ multicast)
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org
Hi Loa, Florin, ------Loa wrote------ > - for discovery specifiactions > -- does this include automated Inter-AS discovery I'm not sure I understand what part of the charter you're asking about. Can you point out what section(s) you referring to, (scope, tasks worked on, etc.)? > - I would split the > > Jul 2010 Submit Inter-AS VPLS and VPWS solutions to IESG > milestone into two different mailstones This may not be necessary. See below. ------Florin wrote------ > Goals and Milestones: > [..] > FB> We are missing here L2VPN Auto-discovery, Signaling and Inter-AS > (see draft-ietf-l2vpn-signaling-08.txt). This was already submitted to > IESG and is waiting in the RFC queue. Suggest adding the following item: > > "Done Submit L2VPN Auto-discovery, Signaling and Inter-AS to IESG" > [..] > > Jul 2010 Submit Inter-AS VPLS and VPWS solutions to IESG > FB> I thought we already have these items addressed in > draft-ietf-l2vpn-signaling-08.txt ("Provisioning, Autodiscovery, and > Signaling in L2VPNs"), currently in the RFC queue. Good point, however that draft largely only covers signaling for Inter-AS unicast L2VPN's. It does not cover optimized forwarding of multicast within Inter-AS VPLS or VPMS. What about the following suggestion? In "Scope", we change #8 to be as follows: ---cut here--- 8. Define requirements and solutions for Auto-Discovery and Signaling of Inter-AS unicast VPLS and VPWS L2VPN's, in addition to Inter-AS multicast VPLS and VPMS Layer-2 VPN's. ---cut here--- The above would capture the existing, completed work in draft-ietf-l2vpn-signaling-08 for Auto-Discovery and Signaling of Intra- and Inter-AS VPWS and VPLS L2VPN's. In addition, it should also capture the in-flight work on optimized multicast, both Intra- and Inter-AS, for VPLS and VPMS in the following drafts: - draft-ietf-l2vpn-vpls-mcast-reqts-05 - draft-ietf-l2vpn-vpls-mcast-03 - draft-raggarwa-l2vpn-p2mp-pw-00 -- assuming PWE3 & L2VPN successfully charter work on p2mp PW's and l2vpn's - TBD draft for VPMS l2vpn requirements I really don't think it's necessary to create separate goals/milestones for every solution calling out that it's specific for Intra- or Inter-AS, since most (all?) existing work has included Inter-AS anyway. (Of course, I am making a minor exception for the l2vpn-signaling draft down below). In "Goals and Milestones": ---cut here--- As you suggested, add this: Done Submit Auto-Discovery and Signaling for Intra-AS and Inter-AS VPLS and VPWS Layer-2 VPN's [..] Also, as you suggested, delete this milestone: Jul 2010 Submit Inter-AS VPLS and VPWS solutions to IESG ---cut here--- The Intra- and Inter-AS multicast work should already be reflected in these milestones, (no changes to these): ---cut here--- Nov 2008 Submit multicast optimization solutions for VPLS to IESG Mar 2009 Submit I-D on Virtual Private Multicast Service (VPMS) requirements to IESG Nov 2009 Submit Auto-Discovery solution for VPMS to IESG ---cut here--- Thanks, -shane
- L2VPN (Re-)charter: Inter-AS (+ multicast) Shane Amante
- RE: L2VPN (Re-)charter: Inter-AS (+ multicast) BALUS Florin
- Re: L2VPN (Re-)charter: Inter-AS (+ multicast) Shane Amante