From l2vpn-bounces@ietf.org  Fri Jul  4 02:42:54 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2060A3A6B5E;
	Fri,  4 Jul 2008 02:42:54 -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 C57F93A6AF8;
	Fri,  4 Jul 2008 02:42:51 -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, UNPARSEABLE_RELAY=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 Y8KNuy22vDW3; Fri,  4 Jul 2008 02:42:50 -0700 (PDT)
Received: from mgw2.noc.ntt.com (mgw2.noc.ntt.com [210.160.15.6])
	by core3.amsl.com (Postfix) with ESMTP id A72123A67AB;
	Fri,  4 Jul 2008 02:42:50 -0700 (PDT)
Received: from mop2.noc.ntt.com
	by mgw2.noc.ntt.com (NTT-Com MailSV) with ESMTP id m649gvH2016230;
	Fri, 4 Jul 2008 18:42:57 +0900 (JST)
Received: from mip1.noc.ntt.com (mvi2.noc.ntt.com)
	by mop2.noc.ntt.com (NTT-Com MailSV) with ESMTP id
	<0K3H007BJ6ZLIR@ntt.com>; Fri, 04 Jul 2008 18:42:57 +0900 (JST)
Date: Fri, 04 Jul 2008 18:42:57 +0900
From: "Yuji KAMITE" <y.kamite@ntt.com>
Subject: FW: I-D Action:draft-kamite-l2vpn-vpms-frmwk-requirements-00.txt
To: l2vpn@ietf.org
Message-id: <011801c8ddba$56ee9130$fd45320a@coe.ntt.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcjdttznyxAfKbL1Q2Kq1bW5G9Sz7wAA13lw
Keywords: draft-??
Cc: pwe3@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 all,

We published a new draft that introduces "VPMS" service model.
(point-to-multipoint L2VPN, for unidirectional multicast service delivery).

Authors would like this to be a base document for several potential solutions near future: it would include "P2MP PW"
currently discussed in pwe3, and others (auto-discovery etc.).

I'd appreciate your comments and feedbacks.

Best regards,
-Yuji 

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, July 04, 2008 6:15 PM
To: i-d-announce@ietf.org
Subject: I-D Action:draft-kamite-l2vpn-vpms-frmwk-requirements-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Framework and Requirements for Virtual Private Multicast Service (VPMS)
	Author(s)       : Y. Kamite, F. JOUNAY
	Filename        : draft-kamite-l2vpn-vpms-frmwk-requirements-00.txt
	Pages           : 21
	Date            : 2008-07-04

This document provides a framework and service level requirements for Virtual Private Multicast Service (VPMS).  VPMS is defined as
a Layer
2 VPN service that provides point-to-multipoint connectivity for a variety of Layer 2 link layers across an IP or MPLS-enabled PSN.
This document outlines architectural service models of VPMS and states generic and high level requirements.  This is intended to aid
in developing protocols and mechanisms to support VPMS.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kamite-l2vpn-vpms-frmwk-requirements-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the
Internet-Draft.



From l2vpn-bounces@ietf.org  Tue Jul  8 20:16:44 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7ED7B3A67F3;
	Tue,  8 Jul 2008 20:16:44 -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 81F1D3A67F3
	for <l2vpn@core3.amsl.com>; Tue,  8 Jul 2008 20:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.517
X-Spam-Level: 
X-Spam-Status: No, score=-0.517 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482,
	J_CHICKENPOX_13=0.6]
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 ZxWewL81I71d for <l2vpn@core3.amsl.com>;
	Tue,  8 Jul 2008 20:16:42 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 22B383A67D6
	for <l2vpn@ietf.org>; Tue,  8 Jul 2008 20:16:42 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id DDA902684EA; Tue,  8 Jul 2008 21:16:50 -0600 (MDT)
Received: from pmac.castlepoint.net (71-218-97-64.hlrn.qwest.net
	[71.218.97.64]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	for l2vpn@ietf.org; Tue, 08 Jul 2008 21:16:50 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.218.97.64;
	client-port=4404; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: l2vpn@ietf.org
Content-Type: multipart/mixed; boundary=Apple-Mail-6-1042993349
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Tue, 8 Jul 2008 21:16:34 -0600
X-Mailer: Apple Mail (2.924)
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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


--Apple-Mail-6-1042993349
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi all,

It seems that the PWE3 WG has completed their re-charter activity,  
which now includes defining P2MP PW's:
http://www.ietf.org/html.charters/pwe3-charter.html

As a result, we would like to conduct a short call for interest to  
include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG  
charter, before submitting it to the IESG.  Please indicate to the  
mailing list whether you agree that it should be included in the new  
L2VPN charter.  (Silence will not count as support).  Also, please  
speak up if you have comments or clarifications with respect to the  
proposed wording of VPMS.

Copied below is a full copy of the proposed charter, including VPMS.

We will close discussion and gauge consensus on this issue in 2 weeks,  
on Wednesday, 7/23, at 17:00 MDT, UTC -6.

Finally, this call *is not* re-opening the entire charter for  
discussion, rather this is narrowly focused strictly on whether, or  
not, to add VPMS to the previously agreed upon L2VPN charter.

-shane & Vach


--Apple-Mail-6-1042993349
Content-Disposition: attachment;
	filename=l2vpn-milestones-10.txt
Content-Type: text/plain;
	x-unix-mode=0644;
	name="l2vpn-milestones-10.txt"
Content-Transfer-Encoding: quoted-printable

The L2VPN working group is responsible for defining and specifying a=0D
limited number of solutions for supporting provider-provisioned Layer-2 =0D=

Virtual Private Networks (L2VPNs).  Layer-2 VPN's comprise the =
following:=0D
=0D
1. Virtual Private LAN Service (VPLS) -- A Layer-2 service that emulates=0D=

   an Ethernet (V)LAN across an IP or an MPLS-enabled IP Packet Switched =
=0D
   Network (PSN).=0D
=0D
2. Virtual Private Wire Service (VPWS) -- A Layer 2 service that =
provides =0D
   point-to-point connectivity for a variety of link layers, including =0D=

   Frame Relay, ATM, Ethernet, PPP, etc., across an IP or MPLS-enabled =
IP =0D
   PSN. =0D
=0D
3. Virtual Private Multicast Service (VPMS) -- A Layer 2 service that=0D
   Provides point-to-multipoint connectivity for a variety of link =
layers, =0D
   including Frame Relay, ATM, Ethernet, PPP, etc., across an IP or =0D
   MPLS-enabled IP PSN.=0D
=0D
4. IP-only L2VPN -- A point-to-point or point-to-multipoint "IP-only" =0D=

   service over an IP or MPLS-enabled PSN.  This service is similar to =0D=

   VPWS because it supports a variety of link-layer protocols on the =0D
   Attachment Circuits, including Frame Relay, ATM, Ethernet, PPP, etc.  =
=0D
   IP-only L2VPN's are different from both VPLS and VPWS because unicast=0D=

   Layer-2 frames containing IP data packets, either IPv4 or IPv6, are =
de-=0D
   encapsulated leaving only the IP data packet to be transmitted over =0D=

   the PSN.  An IP-only L2VPN service also differs from L3VPN service, =0D=

   since no routing protocol operates between the PE and CE; =
furthermore, =0D
   connectivity from CE to CE is provided via an emulated Layer-2 =
service =0D
   over the PSN, which results in the CE's appearing to be directly =0D
   attached to each other at Layer-2.  The WG will address two specific =0D=

   types of IP-only L2VPN:=0D
=0D
   a) Those with Attachment Circuits (ACs) that use the same Layer 2 =0D
   framing at all attachment points in the same L2VPN; and,=0D
=0D
   b) Those with ACs that use different Layer 2 framing at various =0D
   attachment points in the same L2VPN. For (b), inter-working between =0D=

   link-layers is strictly out of scope beyond that which is minimally =0D=

   necessary to ensure that IP packets are transported from an AC of one =
=0D
   type, across the IP or MPLS-enabled IP PSN, and to an AC of another =0D=

   type in as transparent a manner as possible to the CEs on both sides =0D=

   of the service.=0D
=0D
VPLS, VPWS and VPMS operate over Pseudowires (PWs) as defined by the=0D
PWE3 WG.  As with a single PW, an L2VPN emulates a "native" service=0D
over a PSN that is reasonably faithful to, but may not be entirely=0D
indistinguishable from, the native service itself. Further, following=0D
in the "edge-to-edge" nature of the PWs that it uses, the L2VPN WG=0D
will not define any new mechanisms which exert control over the=0D
underlying PSN.  When necessary it may, however, recommend or require=0D
the use of existing PSN QoS and path control mechanisms between PW=0D
endpoints which make up the L2VPN.=0D
=0D
L2VPN's will make use of existing IETF specified mechanisms unless there =
=0D
are technical reasons why the existing mechanisms are insufficient or =0D=

unnecessary.=0D
=0D
The L2VPN WG is responsible for specification of the discovery and =0D
membership of PE's participating in a VPLS, VPWS or IP-only L2VPN as =
well =0D
as the membership of CE devices to a specific instance of a L2VPN.=0D
=0D
The L2VPN WG will provide extensions of existing protocols that will be =0D=

discussed in protocol-specific WG's.  In particular, the L2VPN WG =0D
may define extensions to pseudowire management mechanisms (including=0D
OAM), specifically Pseudowire Virtual Circuit Connectivity Verification=0D=

(VCCV), for VPLS.  Those VCCV extensions will be reviewed by PWE3 to=0D
ensure they are inline with the overall design/architecture of VCCV=0D
and MPLS.=0D
=0D
The L2VPN WG will not define new encapsulations, control (set-up, =0D
configuration, maintenance or tear-down), or resiliency mechanisms=0D
specifically related to pseudowires, because those must be defined by =
the =0D
PWE3 WG.  Furthermore, the L2VPN WG will not define protocol inter-=0D
working between a VPLS or VPWS and native service-layer control, OAM or =0D=

or resiliency mechanisms, as those will be defined by the PWE3 WG.  On =0D=

the other hand, the L2VPN WG may define how to operate native service-=0D=

layer control, OAM or resiliency mechanisms on top of a VPLS or VPWS =0D
service.=0D
=0D
The L2VPN WG scope includes the following:=0D
=0D
1. Discovery of PE's participating in a Layer-2 VPN and the associated=0D=

   topology required for connectivity of the VPLS or VPWS service.=0D
=0D
2. Signaling of information related to the discovery and membership of =0D=

   PE's within a L2VPN.  These procedures must use PWE3 control and =0D
   management procedures, or define requirements for extensions of PWE3 =0D=

   protocols to suit the needs of an L2VPN.  Once those requirements are =
=0D
   reviewed by the L2VPN WG, they should be provided to the PWE3 WG to =0D=

   derive solutions.=0D
=0D
3. MIB's for Layer-2 VPN solutions.=0D
=0D
4. Specification of requirements and framework that will define =
Operations=0D
   Administration and Management (OAM) procedures for VPLS and VPWS =
VPN's,=0D
   related to the operation of VPLS and VPWS VPN's over IP/MPLS PSN's.  =0D=

   In addition, the L2VPN WG will define OAM solutions for VPLS and VPWS=0D=

   VPN's.=0D
=0D
5. Mechanisms to permit optimization of multicast data traffic within=0D
   a VPLS or VPWS VPN over an IP/MPLS PSN. =0D
=0D
6. Improved service convergence for multi-homed CE's to VPLS PE's.  =0D
   Specifically, upon failure of a primary path from a CE to VPLS PE, =0D=

   initiate a rapid switch-over to an alternate path.  If required, =0D
   interactions with native service-layer resiliency mechanisms will be =0D=

   provided via solutions from other IETF WG's such as PWE3.=0D
=0D
7. Enhancements to increase the scalability of the Control Plane and=0D
   Data Plane (e.g.: number of PW's and MAC Forwarding Database, =0D
   respectively) of VPLS PE nodes.=0D
=0D
8. Define requirements and solutions for Auto-Discovery and Signaling=0D
   of Inter-AS VPLS and VPWS L2VPN's, in addition to Inter-AS solutions=0D=

   for multicast-optimized VPLS and VPMS Layer-2 VPN's.=0D
=0D
The L2VPN WG currently works on the following tasks:=0D
=0D
- Define MIB's appropriate for each type of Layer-2 VPN.=0D
=0D
- Specification of Operations Administration and Management (OAM)=0D
  mechanisms for VPLS, VPWS and IP-only VPN's.=0D
=0D
- Specification of procedures to permit optimization of L2VPN multicast =0D=

  data traffic within the PSN.=0D
=0D
- Define enhancements to increase scalability of VPLS PE nodes, to=0D
  provide aggregation of learned customer MAC addresses at VPLS PE's.=0D
=0D
- Identify requirements for multi-homing of CE's to VPLS PE's. =0D
  elements.  Based on these requirements, define solutions for achieving=0D=

  fast convergence after a switchover to an alternate path, for example=0D=

  through optimized MAC flushing within a VPLS domain.=0D
=0D
- Identify requirements for Inter-AS VPLS and VPWS services.  Define=0D
  Inter-AS enhancements to VPLS and VPWS based on these requirements.=0D
=0D
Where necessary, the WG will coordinate its activities with IEEE 802.1.=0D=

=0D
Goals and Milestones:=0D
=0D
Done   Submit L2 requirements to IESG for publication as Informational =
RFC=0D
Done   Identify VPLS and VPWS solutions for the WG=0D
Done   Submit L2 framework to IESG for publication as Informational RFC=0D=

Done   Submit VPLS solution documents to IESG=0D
Done   Submit VPWS solution documents to IESG=0D
Done   Submit an I-D on OAM requirements for VPLS=0D
Done   Submit an I-D on OAM requirements for VPWS=0D
Done   Submit an I-D describing MIB for VPLS=0D
Done   Submit an I-D describing MIB for VPWS=0D
Done   Submit Auto-Discovery and Signaling for Intra-AS and Inter-AS=0D
          VPLS and VPWS Layer-2 VPN's=0D
=0D
Nov 2008    Submit IP-only L2VPN solution documents to IESG=0D
=0D
Mar 2009    Submit signaling solution for multicast-optimized VPLS to =
IESG=0D
=0D
Mar 2009    Submit I-D on Virtual Private Multicast Service (VPMS)=0D
            requirements to IESG=0D
=0D
Mar 2009    Submit PIM snooping solution for VPLS to IESG=0D
=0D
Mar 2009    Submit OAM solutions for VPWS to IESG=0D
Mar 2009    Submit OAM solutions for VPLS to IESG=0D
Mar 2009    Submit OAM solutions for IP-only L2VPN to IESG=0D
=0D
Jul 2009    Submit MIB for VPLS to IESG=0D
Jul 2009    Submit MIB for VPWS to IESG=0D
Jul 2009    Submit MIB for IP-only L2VPN to IESG=0D
=0D
Nov 2009    Submit scalability solutions for VPLS Control-Plane to IESG=0D=

Nov 2009    Submit scalability solutions for VPLS Data-Plane to IESG=0D
=0D
Nov 2009    Submit Auto-Discovery solution for VPMS to IESG=0D
=0D
Jul 2010    Submit VPLS service convergence improvement solutions to =
IESG=0D
=0D
Jul 2010    Submit VPLS multi-homing solutions to IESG=0D

--Apple-Mail-6-1042993349
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit



--Apple-Mail-6-1042993349--


From l2vpn-bounces@ietf.org  Wed Jul  9 00:06:56 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46C6F3A67DB;
	Wed,  9 Jul 2008 00:06:56 -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 826443A67D8
	for <l2vpn@core3.amsl.com>; Wed,  9 Jul 2008 00:06:54 -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, UNPARSEABLE_RELAY=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 suS1PhDnMVAq for <l2vpn@core3.amsl.com>;
	Wed,  9 Jul 2008 00:06:53 -0700 (PDT)
Received: from mgw2.noc.ntt.com (mgw2.noc.ntt.com [210.160.15.6])
	by core3.amsl.com (Postfix) with ESMTP id 887C83A6782
	for <l2vpn@ietf.org>; Wed,  9 Jul 2008 00:06:53 -0700 (PDT)
Received: from mop2.noc.ntt.com
	by mgw2.noc.ntt.com (NTT-Com MailSV) with ESMTP id m6975HEc029915
	for <l2vpn@ietf.org>; Wed, 9 Jul 2008 16:07:00 +0900 (JST)
Received: from mip1.noc.ntt.com (mvi1.noc.ntt.com)
	by mop2.noc.ntt.com (NTT-Com MailSV) with ESMTP id
	<0K3Q00FV78YYHO@ntt.com>
	for l2vpn@ietf.org; Wed, 09 Jul 2008 16:04:11 +0900 (JST)
Date: Wed, 09 Jul 2008 16:04:09 +0900
From: "Yuji KAMITE" <y.kamite@ntt.com>
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
In-reply-to: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
To: l2vpn@ietf.org
Message-id: <017301c8e191$fc837400$fd45320a@coe.ntt.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcjhckIB5fUBv8e4TbKJxS6snBOKzwAGVF2A
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Yes, I support this should be in the charter item.

Regards,
-Yuji

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
> On Behalf Of Shane Amante
> Sent: Wednesday, July 09, 2008 12:17 PM
> To: l2vpn@ietf.org
> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
> 
> Hi all,
> 
> It seems that the PWE3 WG has completed their re-charter 
> activity, which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
> 
> As a result, we would like to conduct a short call for 
> interest to include VPMS (likely utilizing P2MP PW's) into 
> the new L2VPN WG charter, before submitting it to the IESG.  
> Please indicate to the mailing list whether you agree that it 
> should be included in the new L2VPN charter.  (Silence will 
> not count as support).  Also, please speak up if you have 
> comments or clarifications with respect to the proposed 
> wording of VPMS.
> 
> Copied below is a full copy of the proposed charter, including VPMS.
> 
> We will close discussion and gauge consensus on this issue in 
> 2 weeks, on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> 
> Finally, this call *is not* re-opening the entire charter for 
> discussion, rather this is narrowly focused strictly on 
> whether, or not, to add VPMS to the previously agreed upon 
> L2VPN charter.
> 
> -shane & Vach
> 
> 



From l2vpn-bounces@ietf.org  Wed Jul  9 00:10:45 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A1033A68E7;
	Wed,  9 Jul 2008 00:10:45 -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 5FA423A68E7
	for <l2vpn@core3.amsl.com>; Wed,  9 Jul 2008 00:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	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 WVy9sYXSe0Ik for <l2vpn@core3.amsl.com>;
	Wed,  9 Jul 2008 00:10:42 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net
	[217.115.75.234])
	by core3.amsl.com (Postfix) with ESMTP id 5F65A3A67D8
	for <l2vpn@ietf.org>; Wed,  9 Jul 2008 00:10:42 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56])
	by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m697AcbR018397
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 9 Jul 2008 09:10:38 +0200
Received: from demuexc023.nsn-intra.net (webmail.nsn-intra.net [10.150.128.36])
	by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m697AZ7o015205; Wed, 9 Jul 2008 09:10:36 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by
	demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 9 Jul 2008 09:10:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Wed, 9 Jul 2008 09:10:33 +0200
Message-ID: <9FF5BDAD88B9D84881609E89AC92FB83F3EDE0@DEMUEXC014.nsn-intra.net>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: AcjhckWvzrNgTP+4Qt2YIUR9shJxyQAIG1tg
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Shane Amante" <shane@castlepoint.net>
X-OriginalArrivalTime: 09 Jul 2008 07:10:35.0078 (UTC)
	FILETIME=[E1DB4E60:01C8E192]
X-TM-AS-Product-Ver: SMEX-7.0.0.1584-5.5.1027-16020.005
X-TM-AS-Result: No--13.603400-8.000000-31
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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,
I would like to see VPMS included in the charter of L2VPN.
Best regards,
Nurit=20

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of ext Shane Amante
Sent: Wednesday, July 09, 2008 06:17
To: l2vpn@ietf.org
Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)

Hi all,

It seems that the PWE3 WG has completed their re-charter activity, which
now includes defining P2MP PW's:
http://www.ietf.org/html.charters/pwe3-charter.html

As a result, we would like to conduct a short call for interest to
include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG charter,
before submitting it to the IESG.  Please indicate to the mailing list
whether you agree that it should be included in the new L2VPN charter.
(Silence will not count as support).  Also, please speak up if you have
comments or clarifications with respect to the proposed wording of VPMS.

Copied below is a full copy of the proposed charter, including VPMS.

We will close discussion and gauge consensus on this issue in 2 weeks,
on Wednesday, 7/23, at 17:00 MDT, UTC -6.

Finally, this call *is not* re-opening the entire charter for
discussion, rather this is narrowly focused strictly on whether, or not,
to add VPMS to the previously agreed upon L2VPN charter.

-shane & Vach



From l2vpn-bounces@ietf.org  Wed Jul  9 00:39:18 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6AA6C3A68B2;
	Wed,  9 Jul 2008 00:39:18 -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 20EA83A6935
	for <l2vpn@core3.amsl.com>; Wed,  9 Jul 2008 00:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 8lG50tr-ISQC for <l2vpn@core3.amsl.com>;
	Wed,  9 Jul 2008 00:39:16 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id D57883A68B1
	for <l2vpn@ietf.org>; Wed,  9 Jul 2008 00:39:15 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jul 2008 09:39:26 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Wed, 9 Jul 2008 09:39:24 +0200
Message-ID: <BBBE5BAA3B351C488C415EA662EA8840053E1796@ftrdmel2>
In-Reply-To: <017301c8e191$fc837400$fd45320a@coe.ntt.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: AcjhckIB5fUBv8e4TbKJxS6snBOKzwAGVF2AAALKy/A=
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
	<017301c8e191$fc837400$fd45320a@coe.ntt.com>
From: <philippe.niger@orange-ftgroup.com>
To: <l2vpn@ietf.org>
X-OriginalArrivalTime: 09 Jul 2008 07:39:26.0644 (UTC)
	FILETIME=[E9F34F40:01C8E196]
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 all,

Support also.

Regards,
Philippe.

-----Message d'origine-----
De : l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] De la part =
de Yuji KAMITE
Envoy=E9 : mercredi 9 juillet 2008 09:04
=C0 : l2vpn@ietf.org
Objet : RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)

Yes, I support this should be in the charter item.

Regards,
-Yuji

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf =

> Of Shane Amante
> Sent: Wednesday, July 09, 2008 12:17 PM
> To: l2vpn@ietf.org
> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
>=20
> Hi all,
>=20
> It seems that the PWE3 WG has completed their re-charter activity,=20
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>=20
> As a result, we would like to conduct a short call for interest to=20
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG=20
> charter, before submitting it to the IESG.
> Please indicate to the mailing list whether you agree that it should=20
> be included in the new L2VPN charter.  (Silence will not count as=20
> support).  Also, please speak up if you have comments or=20
> clarifications with respect to the proposed wording of VPMS.
>=20
> Copied below is a full copy of the proposed charter, including VPMS.
>=20
> We will close discussion and gauge consensus on this issue in
> 2 weeks, on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>=20
> Finally, this call *is not* re-opening the entire charter for=20
> discussion, rather this is narrowly focused strictly on whether, or=20
> not, to add VPMS to the previously agreed upon L2VPN charter.
>=20
> -shane & Vach
>=20
>=20



From l2vpn-bounces@ietf.org  Wed Jul  9 00:39:25 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFA1628C12E;
	Wed,  9 Jul 2008 00:39:25 -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 6831428C12E
	for <l2vpn@core3.amsl.com>; Wed,  9 Jul 2008 00:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 sK3SqQYydRfw for <l2vpn@core3.amsl.com>;
	Wed,  9 Jul 2008 00:39:23 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id 2E4C828C12B
	for <l2vpn@ietf.org>; Wed,  9 Jul 2008 00:39:23 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jul 2008 09:39:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Wed, 9 Jul 2008 09:39:32 +0200
Message-ID: <8AA97249241F7148BE6D3D8B93D83F5A1256CF61@ftrdmel2>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: Acjhcj/zklfqrN1sS9usxVkYsIBBUgAJHhAw
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
From: <frederic.jounay@orange-ftgroup.com>
To: <shane@castlepoint.net>,
	<l2vpn@ietf.org>
X-OriginalArrivalTime: 09 Jul 2008 07:39:33.0566 (UTC)
	FILETIME=[EE1385E0:01C8E196]
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 all,
I'm in favor to include this new item in the charter

Fred.=20

-----Message d'origine-----
De : l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] De la part =
de Shane Amante
Envoy=E9 : mercredi 9 juillet 2008 05:17
=C0 : l2vpn@ietf.org
Objet : Re-charter Take 2: Virtual Private Multicast Service (VPMS)

Hi all,

It seems that the PWE3 WG has completed their re-charter activity, which =
now includes defining P2MP PW's:
http://www.ietf.org/html.charters/pwe3-charter.html

As a result, we would like to conduct a short call for interest to =
include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG charter, =
before submitting it to the IESG.  Please indicate to the mailing list =
whether you agree that it should be included in the new L2VPN charter.  =
(Silence will not count as support).  Also, please speak up if you have =
comments or clarifications with respect to the proposed wording of VPMS.

Copied below is a full copy of the proposed charter, including VPMS.

We will close discussion and gauge consensus on this issue in 2 weeks, =
on Wednesday, 7/23, at 17:00 MDT, UTC -6.

Finally, this call *is not* re-opening the entire charter for =
discussion, rather this is narrowly focused strictly on whether, or not, =
to add VPMS to the previously agreed upon L2VPN charter.

-shane & Vach



From l2vpn-bounces@ietf.org  Wed Jul  9 01:33:21 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F8D63A6A1F;
	Wed,  9 Jul 2008 01:33:21 -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 29D683A6A07
	for <l2vpn@core3.amsl.com>; Wed,  9 Jul 2008 01:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 eoeYpXaH14Cv for <l2vpn@core3.amsl.com>;
	Wed,  9 Jul 2008 01:33:19 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138])
	by core3.amsl.com (Postfix) with ESMTP id 2830E3A699F
	for <l2vpn@ietf.org>; Wed,  9 Jul 2008 01:33:19 -0700 (PDT)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.108]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jul 2008 09:33:29 +0100
Received: from 10.215.40.109 ([10.215.40.109]) by
	E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.32]) with
	Microsoft Exchange Server HTTP-DAV ; Wed,  9 Jul 2008 08:33:28 +0000
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Wed, 09 Jul 2008 09:33:15 +0100
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Shane Amante <shane@castlepoint.net>,
	<l2vpn@ietf.org>
Message-ID: <C49A365B.8246%benjamin.niven-jenkins@bt.com>
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: Acjhnm4z71kfdaUOeUODmJ7rmFVWqA==
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2008 08:33:29.0541 (UTC)
	FILETIME=[76DE1F50:01C8E19E]
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

I support the inclusion of VPMS into the WG charter.

Ben



On 09/07/2008 04:16, "Shane Amante" <shane@castlepoint.net> wrote:

> Hi all,
> 
> It seems that the PWE3 WG has completed their re-charter activity,
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
> 
> As a result, we would like to conduct a short call for interest to
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG
> charter, before submitting it to the IESG.  Please indicate to the
> mailing list whether you agree that it should be included in the new
> L2VPN charter.  (Silence will not count as support).  Also, please
> speak up if you have comments or clarifications with respect to the
> proposed wording of VPMS.
> 
> Copied below is a full copy of the proposed charter, including VPMS.
> 
> We will close discussion and gauge consensus on this issue in 2 weeks,
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> 
> Finally, this call *is not* re-opening the entire charter for
> discussion, rather this is narrowly focused strictly on whether, or
> not, to add VPMS to the previously agreed upon L2VPN charter.
> 
> -shane & Vach
> 
> 



From l2vpn-bounces@ietf.org  Thu Jul 10 04:41:59 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5A613A695B;
	Thu, 10 Jul 2008 04:41:58 -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 5EB163A695B;
	Thu, 10 Jul 2008 04:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[AWL=0.397, 
	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 kBhppm7ohXv4; Thu, 10 Jul 2008 04:41:57 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id E482D3A68D0;
	Thu, 10 Jul 2008 04:41:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 7ED4E1C2C0;
	Thu, 10 Jul 2008 13:42:07 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 17172-10; Thu, 10 Jul 2008 13:42:02 +0200 (CEST)
Received: from [127.0.0.1] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id 0C7B61C2BB;
	Thu, 10 Jul 2008 13:42:02 +0200 (CEST)
Message-ID: <4875F57C.4040002@pi.nu>
Date: Thu, 10 Jul 2008 13:41:48 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org, mpls-tp@ietf.org, MEAD team <mpls-interop@ietf.org>, 
	jwt@testbed.se, ahtmpls@itu.int, ccamp <ccamp@ops.ietf.org>, 
	pwe3 <pwe3@ietf.org>, L2VPN <l2vpn@ietf.org>
Subject: First version of the first MPLS-TP documents
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at viciousnest.net
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

All,

the MPLS-TP work that started after the ITU-T acceptance of the JWT
advice to work with the iETF, using IETF processes, to create a MPLS
Transport Profile (MPLS-TP) within the IETF MPLS architecture.

This effort has now produced a set of documents available in their
first versions. In IETF terminology the documents are still
"individual drafts", but will after discussion, review and updates
hopefully become working groups documents.

First I'd like to thank all the people that has put in efforts to
make this possible, we are actually a bit better of than we planned.
Thanks to all editors and contributing authors!

When accepting documents as working group documents there are two
criteria that working groups are looking at:

- is this document addressing a problem that needs to be solved
- is this document a good starting point in solving this problem

The MPLS-TP documents are in some aspects special with respect to
the IETF process, the JWT produced guidelines on which documents
that needs to be included in the MPLS-TP. The MEAD team has since
"improved and extended" the document list. This makes us pretty
sure that the documents address problems that needs to be solved.

However it is usually beneficial to have documents reviewed early in
order to create a the starting point needed for solving the problem.

We therefore now invite both IETF working groups (CCAMP, MPLS, L2VPN
and PWE3), the MPLS Interoperability (MEAD) team, the JWT and the
ITU-T Ad Hoc MPLS group to participate in this review.


The newly produced documents are:

1. A Framework for MPLS in Transport Networks
     <draft-blb-mpls-tp-framework-00.txt>

2. MPLS Generic Associated Channel
    <draft-bocci-pwe3-mpls-tp-ge-ach-00.txt>

3. MPLS TP Network Management Requirements
    <draft-gray-mpls-tp-nm-req-00.txt>

4. MPLS-TP Requirements
    <draft-jenkins-mpls-mpls-tp-requirements-00.txt>

5. MPLS-TP OAM Analysis
    <draft-sprecher-mpls-tp-oam-analysis-00.txt>

6. Multiprotocol Label Switching Transport Profile Survivability
    Framework
    <draft-sprecher-mpls-tp-survive-fwk-00.txt>

7. Assignment of the Generic Associated Channel Header Label (GAL)
    <draft-vigoureux-mpls-tp-gal-00.txt>

8. Requirements for OAM in MPLS Transport Networks
    <draft-vigoureux-mpls-tp-oam-requirements-00.txt>

9. JWT Report on MPLS Architectural Considerations for a Transport
    Profile
    <draft-bryant-mpls-tp-jwt-report-00.txt>

    Note: This is a document is created to an easily referencable and
    permanent storage for the JWT conclusions and advice. The major
    part of the document are the JWT slides, since it is not possible
    to change the slides it is only the commentary part of the
    document that is possible to comment on.

It is always possible to to send comments on these documents to the
MPLS working group mailing list, for document #2 (The Generic MPLS
Associated Channel) comments could also go to the PWE3 mailing list.

However, we are setting up a dedicated mailing list for the MPLS-TP
discussions:

mpls-tp@ietf.org

To subscribe to this list send a mail to mpls-tp-request@ietf.org,
and confirm by replying or visiting the indicated web-page.

The easiest way to find all the MPLS-TP documents is to use the IETF
ID Tracker:

https://datatracker.ietf.org/idtracker/

and put "mpls-tp" in the filename field.

There is also a 10th document that people from the JWT has pointed
out to us would be beneficial if it did go through the same review
process.

10. "EXP field" renamed to  "CoS Field"
     <draft-ietf-mpls-cosfield-def-04.txt>

The document has been progressed within the IETF as a normal MPLS
document, and has passed MPLS working group last call. However, we
need to run it through working group last call in the working groups
with RFCs that is updated by this document. The ITU-T Ad Hoc MPLS
group will be invited to participate in this wg last call. A mail
will go out shortly with details of this working group last call.

The process in the future will be that when a MPLS-TP document is
published or updated a note will be sent to the relevant working
group (this is an automated IETF process), this note will also be
forwarded to the ITU-T Ad Hoc MPLS group.

Receiving such a note indicates that it is time to review and
comment on the document. When a document goes into working group
last call the mail initiating the last call will also be sent to the
ITU-T Ad Hoc MPLS group. Receiving such a last call REQUIRES, as per
the agreement within the JWT, that the ITU-T respond formally,
indicating either that the document is accepted or indicating
necessary changes.

To test this process we'd appreciate very much if the ITU-T
treated the upcoming last call on this document the same way.

/Loa (chair of the MEAD team)



-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.nu


From l2vpn-bounces@ietf.org  Thu Jul 10 04:59:32 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 807E03A6A04;
	Thu, 10 Jul 2008 04:59:32 -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 0FF2E3A6932;
	Thu, 10 Jul 2008 04:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433, 
	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 Ky+loTHdXEpF; Thu, 10 Jul 2008 04:59:31 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id F08203A69E0;
	Thu, 10 Jul 2008 04:59:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id C39E81C2C5;
	Thu, 10 Jul 2008 13:59:44 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 22062-01; Thu, 10 Jul 2008 13:59:43 +0200 (CEST)
Received: from [127.0.0.1] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id 0FA7F1C2BC;
	Thu, 10 Jul 2008 13:59:43 +0200 (CEST)
Message-ID: <4875F9A1.5070408@pi.nu>
Date: Thu, 10 Jul 2008 13:59:29 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: tsvwg@ietf.org, ahtmpls@itu.int, ccamp <ccamp@ops.ietf.org>, 
	L2VPN <l2vpn@ietf.org>, pwe3 <pwe3@ietf.org>, mpls@ietf.org
Subject: multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at viciousnest.net
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

All,

this mail initiates a two week multiple-working group last call on

draft-ietf-mpls-cosfield-def-04.txt

Background:

The name "EXP field" of a three bit field in the MPLS shim header,
and the statement in RFC3032 "For experimental use" has led other
SDOs to believe that this field could be used for any type of
experiments. The field has however from the start been intended to
carry Class of Service (CoS) information.

The draft therefore renames the field "Class of Service (CoS) Field".

This is an update of RFC3032, and also of drafts that builds on
RFC3032. This multiple-working group last call is therefore sent to
working groups with RFCs that has been updated.

The document has been through wg last call in the mpls working group,
which I don't think will stop that wg producing new comments now,
nor should it :) .

This working group last call is for CCAMP, L2VPN, PWE3 and TSVWG.

Since this is also of interest in the work we started on a
Transport Profile for MPLS (MPLS-TP) we are also sending it to the
Ad HoC Team on MPLS in the ITU-T.

Please review and send comments to the mpls wg mailing list, or to
the mailing list for mpls-tp discussion that just been set up:

mpls-tp@ietf.org

or directly to the mpls wg co-chairs before e.o.b. July 24.

/Loa

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.nu


From l2vpn-bounces@ietf.org  Thu Jul 10 12:43:46 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABE303A69EB;
	Thu, 10 Jul 2008 12:43:46 -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 C1A4E3A692A
	for <l2vpn@core3.amsl.com>; Thu, 10 Jul 2008 12:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 0G8UOg9kudti for <l2vpn@core3.amsl.com>;
	Thu, 10 Jul 2008 12:43:44 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163])
	by core3.amsl.com (Postfix) with ESMTP id C21C53A6A01
	for <l2vpn@ietf.org>; Thu, 10 Jul 2008 12:43:39 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob105.postini.com
	([64.18.6.12]) with SMTP; Thu, 10 Jul 2008 12:41:58 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp03.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 10 Jul 2008 12:43:54 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 10 Jul 2008 12:43:53 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 Jul 2008 12:43:53 -0700
Received: from sapphire.juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m6AJhrx60799;
	Thu, 10 Jul 2008 12:43:53 -0700 (PDT)
	(envelope-from rahul@juniper.net)
Date: Thu, 10 Jul 2008 12:43:53 -0700 (PDT)
From: Rahul Aggarwal <rahul@juniper.net>
To: Shane Amante <shane@castlepoint.net>
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
Message-ID: <20080710124233.R86571@sapphire.juniper.net>
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 10 Jul 2008 19:43:53.0250 (UTC)
	FILETIME=[487AC820:01C8E2C5]
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 Shane,

Please see below:

On Tue, 8 Jul 2008, Shane Amante wrote:

> Hi all,
>
> It seems that the PWE3 WG has completed their re-charter activity,
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>
> As a result, we would like to conduct a short call for interest to
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG
> charter, before submitting it to the IESG.  Please indicate to the
> mailing list whether you agree that it should be included in the new
> L2VPN charter.

Yes. I believe VPMS should be included in the new L2VPN charter.

rahul

> (Silence will not count as support).  Also, please
> speak up if you have comments or clarifications with respect to the
> proposed wording of VPMS.
>
> Copied below is a full copy of the proposed charter, including VPMS.
>
> We will close discussion and gauge consensus on this issue in 2 weeks,
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>
> Finally, this call *is not* re-opening the entire charter for
> discussion, rather this is narrowly focused strictly on whether, or
> not, to add VPMS to the previously agreed upon L2VPN charter.
>
> -shane & Vach
>
>


From l2vpn-bounces@ietf.org  Thu Jul 10 12:55:08 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B54993A6A80;
	Thu, 10 Jul 2008 12:55:08 -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 0DD063A6A7C
	for <l2vpn@core3.amsl.com>; Thu, 10 Jul 2008 12:55:07 -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 mrtrSAPjctnL for <l2vpn@core3.amsl.com>;
	Thu, 10 Jul 2008 12:55:06 -0700 (PDT)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28])
	by core3.amsl.com (Postfix) with ESMTP id 599203A6A89
	for <l2vpn@ietf.org>; Thu, 10 Jul 2008 12:55:02 -0700 (PDT)
Received: by yx-out-2324.google.com with SMTP id 8so985540yxg.49
	for <l2vpn@ietf.org>; Thu, 10 Jul 2008 12:55:15 -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=lJRxn8BHsA43NtxOhxKM+ARxHkm+e86oNJqxMDt9oe0=;
	b=w4AS8QaetGkMSSuwi85tl5NONtUt77b/emVV1d7XVuNXOWq4S7QSy2PtNcNysjvA1G
	YcuvEHAOWWdhjdqfqep8YlrDdM77kI6TTzvuY/tMU4Asxn+mbG4yEALMWpUuPqEjM22p
	FMCNZA+7c329ScFgZe+GAnpo81d0/+0jFVSEw=
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=UlOL5xPC4jcb0qZNMfxb96S9gn1Wrlou6ndeCKhqNb7GlD/m0EszypoVeXyWNycwk1
	VxJsm9ezvtD0jZAN3a55dJMIwrJVa1ZX+jX+X+0ZcrsXgBQPeu3xBd+3O3N6kCtJ+M0U
	NbPMxxlyXBmPO2DQibpg1eL1WU04Upv+4dOs8=
Received: by 10.114.25.19 with SMTP id 19mr11910666way.225.1215719714904;
	Thu, 10 Jul 2008 12:55:14 -0700 (PDT)
Received: by 10.114.254.9 with HTTP; Thu, 10 Jul 2008 12:55:14 -0700 (PDT)
Message-ID: <ef61db5f0807101255w4b371828kab3c772bb927ac1c@mail.gmail.com>
Date: Fri, 11 Jul 2008 05:55:14 +1000
From: "Simon Delord" <simon.delord@gmail.com>
To: "Shane Amante" <shane@castlepoint.net>, l2vpn@ietf.org
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
In-Reply-To: <C49A365B.8246%benjamin.niven-jenkins@bt.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_14205_28923054.1215719714913"
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
	<C49A365B.8246%benjamin.niven-jenkins@bt.com>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

------=_Part_14205_28923054.1215719714913
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I support VPMS to be included in the WG charter.
Simon



On 09/07/2008 04:16, "Shane Amante" <shane@castlepoint.net> wrote:

> Hi all,
>
> It seems that the PWE3 WG has completed their re-charter activity,
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>
> As a result, we would like to conduct a short call for interest to
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG
> charter, before submitting it to the IESG.  Please indicate to the
> mailing list whether you agree that it should be included in the new
> L2VPN charter.  (Silence will not count as support).  Also, please
> speak up if you have comments or clarifications with respect to the
> proposed wording of VPMS.
>
> Copied below is a full copy of the proposed charter, including VPMS.
>
> We will close discussion and gauge consensus on this issue in 2 weeks,
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>
> Finally, this call *is not* re-opening the entire charter for
> discussion, rather this is narrowly focused strictly on whether, or
> not, to add VPMS to the previously agreed upon L2VPN charter.
>
> -shane & Vach
>
>

------=_Part_14205_28923054.1215719714913
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>I support VPMS to be included in the WG charter.<br>Simon<br><br><br><br>On 09/07/2008 04:16, &quot;Shane Amante&quot; &lt;<a href="mailto:shane@castlepoint.net">shane@castlepoint.net</a>&gt; wrote:<br><br>&gt; Hi all,<br>
&gt;<br>&gt; It seems that the PWE3 WG has completed their re-charter activity,<br>&gt; which now includes defining P2MP PW&#39;s:<br>&gt; <a href="http://www.ietf.org/html.charters/pwe3-charter.html">http://www.ietf.org/html.charters/pwe3-charter.html</a><br>
&gt;<br>&gt; As a result, we would like to conduct a short call for interest to<br>&gt; include VPMS (likely utilizing P2MP PW&#39;s) into the new L2VPN WG<br>&gt; charter, before submitting it to the IESG.&nbsp;&nbsp;Please indicate to the<br>
&gt; mailing list whether you agree that it should be included in the new<br>&gt; L2VPN charter.&nbsp;&nbsp;(Silence will not count as support).&nbsp;&nbsp;Also, please<br>&gt; speak up if you have comments or clarifications with respect to the<br>
&gt; proposed wording of VPMS.<br>&gt;<br>&gt; Copied below is a full copy of the proposed charter, including VPMS.<br>&gt;<br>&gt; We will close discussion and gauge consensus on this issue in 2 weeks,<br>&gt; on Wednesday, 7/23, at 17:00 MDT, UTC -6.<br>
&gt;<br>&gt; Finally, this call *is not* re-opening the entire charter for<br>&gt; discussion, rather this is narrowly focused strictly on whether, or<br>&gt; not, to add VPMS to the previously agreed upon L2VPN charter.<br>
&gt;<br>&gt; -shane &amp; Vach<br>&gt;<br>&gt;<br><br>&nbsp;</div><br>

------=_Part_14205_28923054.1215719714913--


From l2vpn-bounces@ietf.org  Thu Jul 10 23:46:15 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57C3E28C0F4;
	Thu, 10 Jul 2008 23:46:15 -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 F052028C0F4
	for <l2vpn@core3.amsl.com>; Thu, 10 Jul 2008 23:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.86
X-Spam-Level: 
X-Spam-Status: No, score=-5.86 tagged_above=-999 required=5 tests=[AWL=0.739, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pms4GA7BsRlh for <l2vpn@core3.amsl.com>;
	Thu, 10 Jul 2008 23:46:13 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 910D928C0EB
	for <l2vpn@ietf.org>; Thu, 10 Jul 2008 23:46:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.30,343,1212364800"; d="scan'208";a="64683989"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 11 Jul 2008 06:41:06 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6B6f6bc001761; 
	Thu, 10 Jul 2008 23:41:06 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6B6f686022635;
	Fri, 11 Jul 2008 06:41:06 GMT
Received: from xmb-sjc-239.amer.cisco.com ([128.107.191.105]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 Jul 2008 23:41:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Thu, 10 Jul 2008 23:41:05 -0700
Message-ID: <483F121CD2155B43B56DB71228DBAF1501D97B5A@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: AcjhckHBLfxxsopjRO+D6w2l7cAt9gBrkFBg
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 11 Jul 2008 06:41:06.0352 (UTC)
	FILETIME=[1870A300:01C8E321]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1656; t=1215758466;
	x=1216622466; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20(sajassi)=22=20<sajassi@cisco.c
	om> |Subject:=20RE=3A=20Re-charter=20Take=202=3A=20Virtual=20Pr
	ivate=20Multicast=20Service=20(VPMS) |Sender:=20;
	bh=F/+KMfF18Mw7ZfD8yoRDSX+b5ukY7xt0D3zNmFPicoM=;
	b=TR+J8lGttdC1K3WLkJNr0IooiiYZ6qJJn+Yl6vyvM916duk6P7viU+E2AI
	iR/S9Fv8/fySE4fb980LFedQOh1dkvCEJtoLnlNFDKu/VTBkk1tbXw1XuVmn
	b4tiHURbex;
Authentication-Results: sj-dkim-2; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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


Shane,

Where is "a full copy of the proposed charter, including VPMS" ?

I looked through your previous emails and I found the following url but
there is no description of VPMS.

http://l2vpn.tcb.net/recharter/l2vpn-recharter.txt

Cheers,
Ali
=20

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20
> On Behalf Of Shane Amante
> Sent: Tuesday, July 08, 2008 8:17 PM
> To: l2vpn@ietf.org
> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
>=20
> Hi all,
>=20
> It seems that the PWE3 WG has completed their re-charter=20
> activity, which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>=20
> As a result, we would like to conduct a short call for=20
> interest to include VPMS (likely utilizing P2MP PW's) into=20
> the new L2VPN WG charter, before submitting it to the IESG. =20
> Please indicate to the mailing list whether you agree that it=20
> should be included in the new L2VPN charter.  (Silence will=20
> not count as support).  Also, please speak up if you have=20
> comments or clarifications with respect to the proposed=20
> wording of VPMS.
>=20
> Copied below is a full copy of the proposed charter, including VPMS.
>=20
> We will close discussion and gauge consensus on this issue in=20
> 2 weeks, on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>=20
> Finally, this call *is not* re-opening the entire charter for=20
> discussion, rather this is narrowly focused strictly on=20
> whether, or not, to add VPMS to the previously agreed upon=20
> L2VPN charter.
>=20
> -shane & Vach
>=20
>=20


From l2vpn-bounces@ietf.org  Fri Jul 11 00:59:45 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 105033A6B06;
	Fri, 11 Jul 2008 00:59:45 -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 547E73A6B07
	for <l2vpn@core3.amsl.com>; Fri, 11 Jul 2008 00:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 JEPsGywH6DNP for <l2vpn@core3.amsl.com>;
	Fri, 11 Jul 2008 00:59:42 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 0FFC53A6ADA
	for <l2vpn@ietf.org>; Fri, 11 Jul 2008 00:59:41 -0700 (PDT)
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Jul 2008 09:59:57 +0200
Received: from [10.193.15.234] ([10.193.15.234]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Jul 2008 09:59:57 +0200
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: Shane Amante <shane@castlepoint.net>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
Content-Type: text/plain
Organization: France Telecom R&D - Orange Labs
Date: Fri, 11 Jul 2008 09:59:57 +0200
Message-Id: <1215763197.4659.6.camel@l-at11168.FTRD>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jul 2008 07:59:57.0904 (UTC)
	FILETIME=[1CAA2D00:01C8E32C]
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Support.

-Thomas

Shane Amante :
> Hi all,
> 
> It seems that the PWE3 WG has completed their re-charter activity,  
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
> 
> As a result, we would like to conduct a short call for interest to  
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG  
> charter, before submitting it to the IESG.  Please indicate to the  
> mailing list whether you agree that it should be included in the new  
> L2VPN charter.  (Silence will not count as support).  Also, please  
> speak up if you have comments or clarifications with respect to the  
> proposed wording of VPMS.
> 
> Copied below is a full copy of the proposed charter, including VPMS.
> 
> We will close discussion and gauge consensus on this issue in 2 weeks,  
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> 
> Finally, this call *is not* re-opening the entire charter for  
> discussion, rather this is narrowly focused strictly on whether, or  
> not, to add VPMS to the previously agreed upon L2VPN charter.
> 
> -shane & Vach
> 



From l2vpn-bounces@ietf.org  Fri Jul 11 03:14:02 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6054828C163;
	Fri, 11 Jul 2008 03:14:02 -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 4BB5B3A6ABC
	for <l2vpn@core3.amsl.com>; Fri, 11 Jul 2008 03:14:00 -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 ZOkz6vRjhCux for <l2vpn@core3.amsl.com>;
	Fri, 11 Jul 2008 03:13:59 -0700 (PDT)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28])
	by core3.amsl.com (Postfix) with ESMTP id 350653A6A5A
	for <l2vpn@ietf.org>; Fri, 11 Jul 2008 03:13:59 -0700 (PDT)
Received: by yx-out-2324.google.com with SMTP id 8so1051777yxg.49
	for <l2vpn@ietf.org>; Fri, 11 Jul 2008 03:14:16 -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:references;
	bh=TzypyFHi0VknTzkZdDCYxZkD1We/RDc8FBxBl8BlBYk=;
	b=b4q0vcrySjUsropAavsxDXPqTyb0zc+dgYb1acucq5Ep/VzqU5AeB6OpKplUb37KTC
	YMkaP00whwjY6UQRaSyUJUqsnDvxZr0U5yoPRnjxxGT1f+RxidJRPpkgM4Z7MKsTn5Q7
	CfLXxlqTR7vxUTT5c3w+yvYW2cs+44RDQNe74=
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:references;
	b=X7vSeFVdsYOvXAC4niUAFKg56eY7YCsTLxaspVMwBPMVlb9iDmwA4pcEd4zrIrf/jo
	idj0SjnjDUfPQI8yLS9JQepnkjU3ImMa6ZhwVYnkBPZwF+yVoCXXTBWjlchH3aSicsia
	olcFY6mrOZQLU4lzCc0wf7CKH4TwYzgiw5xWQ=
Received: by 10.151.12.4 with SMTP id p4mr15644558ybi.29.1215771256044;
	Fri, 11 Jul 2008 03:14:16 -0700 (PDT)
Received: by 10.151.14.6 with HTTP; Fri, 11 Jul 2008 03:14:15 -0700 (PDT)
Message-ID: <8c99930d0807110314r313a15f6x2b59fd1acec8d3f3@mail.gmail.com>
Date: Fri, 11 Jul 2008 06:14:15 -0400
From: "Andrew G. Malis" <agmalis@gmail.com>
To: "Thomas Morin" <thomas.morin@orange-ftgroup.com>
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
In-Reply-To: <1215763197.4659.6.camel@l-at11168.FTRD>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_21892_24881718.1215771256024"
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
	<1215763197.4659.6.camel@l-at11168.FTRD>
Cc: l2vpn@ietf.org, Shane Amante <shane@castlepoint.net>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

------=_Part_21892_24881718.1215771256024
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I also support including VPMS in the charter.

Cheers,
Andy
On Fri, Jul 11, 2008 at 3:59 AM, Thomas Morin <
thomas.morin@orange-ftgroup.com> wrote:

> Support.
>
> -Thomas
>
> Shane Amante :
>  > Hi all,
> >
> > It seems that the PWE3 WG has completed their re-charter activity,
> > which now includes defining P2MP PW's:
> > http://www.ietf.org/html.charters/pwe3-charter.html
> >
> > As a result, we would like to conduct a short call for interest to
> > include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG
> > charter, before submitting it to the IESG.  Please indicate to the
> > mailing list whether you agree that it should be included in the new
> > L2VPN charter.  (Silence will not count as support).  Also, please
> > speak up if you have comments or clarifications with respect to the
> > proposed wording of VPMS.
> >
> > Copied below is a full copy of the proposed charter, including VPMS.
> >
> > We will close discussion and gauge consensus on this issue in 2 weeks,
> > on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> >
> > Finally, this call *is not* re-opening the entire charter for
> > discussion, rather this is narrowly focused strictly on whether, or
> > not, to add VPMS to the previously agreed upon L2VPN charter.
> >
> > -shane & Vach
> >
>
>

------=_Part_21892_24881718.1215771256024
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>I also support including VPMS in the charter.</div>
<div>&nbsp;</div>
<div>Cheers,</div>
<div>Andy<br></div>
<div class="gmail_quote">On Fri, Jul 11, 2008 at 3:59 AM, Thomas Morin &lt;<a href="mailto:thomas.morin@orange-ftgroup.com">thomas.morin@orange-ftgroup.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Support.<br><br>-Thomas<br><br>Shane Amante :<br>
<div>
<div></div>
<div class="Wj3C7c">&gt; Hi all,<br>&gt;<br>&gt; It seems that the PWE3 WG has completed their re-charter activity,<br>&gt; which now includes defining P2MP PW&#39;s:<br>&gt; <a href="http://www.ietf.org/html.charters/pwe3-charter.html" target="_blank">http://www.ietf.org/html.charters/pwe3-charter.html</a><br>
&gt;<br>&gt; As a result, we would like to conduct a short call for interest to<br>&gt; include VPMS (likely utilizing P2MP PW&#39;s) into the new L2VPN WG<br>&gt; charter, before submitting it to the IESG. &nbsp;Please indicate to the<br>
&gt; mailing list whether you agree that it should be included in the new<br>&gt; L2VPN charter. &nbsp;(Silence will not count as support). &nbsp;Also, please<br>&gt; speak up if you have comments or clarifications with respect to the<br>
&gt; proposed wording of VPMS.<br>&gt;<br>&gt; Copied below is a full copy of the proposed charter, including VPMS.<br>&gt;<br>&gt; We will close discussion and gauge consensus on this issue in 2 weeks,<br>&gt; on Wednesday, 7/23, at 17:00 MDT, UTC -6.<br>
&gt;<br>&gt; Finally, this call *is not* re-opening the entire charter for<br>&gt; discussion, rather this is narrowly focused strictly on whether, or<br>&gt; not, to add VPMS to the previously agreed upon L2VPN charter.<br>
&gt;<br>&gt; -shane &amp; Vach<br>&gt;<br><br></div></div></blockquote></div><br>

------=_Part_21892_24881718.1215771256024--


From l2vpn-bounces@ietf.org  Fri Jul 11 07:07:40 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F0A93A67DD;
	Fri, 11 Jul 2008 07:07:40 -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 2600A3A67DD
	for <l2vpn@core3.amsl.com>; Fri, 11 Jul 2008 07:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 efzSsBogSkHh for <l2vpn@core3.amsl.com>;
	Fri, 11 Jul 2008 07:07:36 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 342E83A67A4
	for <l2vpn@ietf.org>; Fri, 11 Jul 2008 07:07:33 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 111E82684EC; Fri, 11 Jul 2008 08:07:51 -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; Fri, 11 Jul 2008 08:07:51 -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=33164; data-bytes=0
Message-ID: <48776936.8080509@castlepoint.net>
Date: Fri, 11 Jul 2008 08:07:50 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
	<483F121CD2155B43B56DB71228DBAF1501D97B5A@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <483F121CD2155B43B56DB71228DBAF1501D97B5A@xmb-sjc-239.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Ali,

The proposed, updated charter was included in the first mail that 
started this thread.  You can find a copy of the mail, including the 
proposed charter, here:

http://www.ietf.org/mail-archive/web/l2vpn/current/msg01724.html

-shane



Ali Sajassi (sajassi) wrote:
> Shane,
> 
> Where is "a full copy of the proposed charter, including VPMS" ?
> 
> I looked through your previous emails and I found the following url but
> there is no description of VPMS.
> 
> http://l2vpn.tcb.net/recharter/l2vpn-recharter.txt
> 
> Cheers,
> Ali
>  
> 
>> -----Original Message-----
>> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
>> On Behalf Of Shane Amante
>> Sent: Tuesday, July 08, 2008 8:17 PM
>> To: l2vpn@ietf.org
>> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
>>
>> Hi all,
>>
>> It seems that the PWE3 WG has completed their re-charter 
>> activity, which now includes defining P2MP PW's:
>> http://www.ietf.org/html.charters/pwe3-charter.html
>>
>> As a result, we would like to conduct a short call for 
>> interest to include VPMS (likely utilizing P2MP PW's) into 
>> the new L2VPN WG charter, before submitting it to the IESG.  
>> Please indicate to the mailing list whether you agree that it 
>> should be included in the new L2VPN charter.  (Silence will 
>> not count as support).  Also, please speak up if you have 
>> comments or clarifications with respect to the proposed 
>> wording of VPMS.
>>
>> Copied below is a full copy of the proposed charter, including VPMS.
>>
>> We will close discussion and gauge consensus on this issue in 
>> 2 weeks, on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>>
>> Finally, this call *is not* re-opening the entire charter for 
>> discussion, rather this is narrowly focused strictly on 
>> whether, or not, to add VPMS to the previously agreed upon 
>> L2VPN charter.
>>
>> -shane & Vach
>>
>>



From l2vpn-bounces@ietf.org  Fri Jul 11 09:56:11 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C53513A684E;
	Fri, 11 Jul 2008 09:56:11 -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 21A2528C243
	for <l2vpn@core3.amsl.com>; Fri, 11 Jul 2008 09:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.942
X-Spam-Level: 
X-Spam-Status: No, score=-5.942 tagged_above=-999 required=5 tests=[AWL=0.657, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Zw1kgcbrjxjV for <l2vpn@core3.amsl.com>;
	Fri, 11 Jul 2008 09:56:09 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 13B0928C251
	for <l2vpn@ietf.org>; Fri, 11 Jul 2008 09:56:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.30,346,1212364800"; d="scan'208";a="86701268"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 11 Jul 2008 16:56:27 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m6BGuRlF029196; 
	Fri, 11 Jul 2008 09:56:27 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m6BGuHf9029446;
	Fri, 11 Jul 2008 16:56:27 GMT
Received: from xmb-sjc-239.amer.cisco.com ([128.107.191.105]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Jul 2008 09:56:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Fri, 11 Jul 2008 09:56:23 -0700
Message-ID: <483F121CD2155B43B56DB71228DBAF1501D97C36@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <48776936.8080509@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: AcjjX42QV+zpYx5fQqaurDRjVPi/IQAFqmPg
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
	<483F121CD2155B43B56DB71228DBAF1501D97B5A@xmb-sjc-239.amer.cisco.com>
	<48776936.8080509@castlepoint.net>
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Shane Amante" <shane@castlepoint.net>
X-OriginalArrivalTime: 11 Jul 2008 16:56:24.0484 (UTC)
	FILETIME=[0D5C8640:01C8E377]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2483; t=1215795387;
	x=1216659387; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20(sajassi)=22=20<sajassi@cisco.c
	om> |Subject:=20RE=3A=20Re-charter=20Take=202=3A=20Virtual=20Pr
	ivate=20Multicast=20Service=20(VPMS) |Sender:=20;
	bh=4NMq7wGLf5v3eECJV4xySFFZjrEcQ5ZeqOTs+GppYEw=;
	b=AIiCqnKV5ykdHfOcLcdmRl3zA/OWtPooGr8sPlVTe7b5PzBfN/dsG5cuuw
	RZG2+AesXUHcEx2oZPKjCWEi42U7REvSiFv71UZr7h4HXKJSffLG5csWL+P5
	lLgSzDPd7Z;
Authentication-Results: sj-dkim-4; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

=20

O.K. Thanks. The definition of VPMS looks good. Lets ship it :-)

-Ali

> -----Original Message-----
> From: Shane Amante [mailto:shane@castlepoint.net]=20
> Sent: Friday, July 11, 2008 7:08 AM
> To: Ali Sajassi (sajassi)
> Cc: l2vpn@ietf.org
> Subject: Re: Re-charter Take 2: Virtual Private Multicast=20
> Service (VPMS)
>=20
> Ali,
>=20
> The proposed, updated charter was included in the first mail=20
> that started this thread.  You can find a copy of the mail,=20
> including the proposed charter, here:
>=20
> http://www.ietf.org/mail-archive/web/l2vpn/current/msg01724.html
>=20
> -shane
>=20
>=20
>=20
> Ali Sajassi (sajassi) wrote:
> > Shane,
> >=20
> > Where is "a full copy of the proposed charter, including VPMS" ?
> >=20
> > I looked through your previous emails and I found the following url=20
> > but there is no description of VPMS.
> >=20
> > http://l2vpn.tcb.net/recharter/l2vpn-recharter.txt
> >=20
> > Cheers,
> > Ali
> > =20
> >=20
> >> -----Original Message-----
> >> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On=20
> >> Behalf Of Shane Amante
> >> Sent: Tuesday, July 08, 2008 8:17 PM
> >> To: l2vpn@ietf.org
> >> Subject: Re-charter Take 2: Virtual Private Multicast=20
> Service (VPMS)
> >>
> >> Hi all,
> >>
> >> It seems that the PWE3 WG has completed their re-charter activity,=20
> >> which now includes defining P2MP PW's:
> >> http://www.ietf.org/html.charters/pwe3-charter.html
> >>
> >> As a result, we would like to conduct a short call for interest to=20
> >> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG=20
> >> charter, before submitting it to the IESG.
> >> Please indicate to the mailing list whether you agree that=20
> it should=20
> >> be included in the new L2VPN charter.  (Silence will not count as=20
> >> support).  Also, please speak up if you have comments or=20
> >> clarifications with respect to the proposed wording of VPMS.
> >>
> >> Copied below is a full copy of the proposed charter,=20
> including VPMS.
> >>
> >> We will close discussion and gauge consensus on this issue in
> >> 2 weeks, on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> >>
> >> Finally, this call *is not* re-opening the entire charter for=20
> >> discussion, rather this is narrowly focused strictly on=20
> whether, or=20
> >> not, to add VPMS to the previously agreed upon L2VPN charter.
> >>
> >> -shane & Vach
> >>
> >>
>=20
>=20


From l2vpn-bounces@ietf.org  Mon Jul 14 05:59:14 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7601128C280;
	Mon, 14 Jul 2008 05:59:14 -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 C4E093A69B9;
	Mon, 14 Jul 2008 05:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.22
X-Spam-Level: 
X-Spam-Status: No, score=-2.22 tagged_above=-999 required=5 tests=[AWL=0.379, 
	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 rTmHasv+g0hl; Mon, 14 Jul 2008 05:59:10 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id C5AED3A6943;
	Mon, 14 Jul 2008 05:59:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id 948A9285E6;
	Mon, 14 Jul 2008 14:59:33 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 08118-07; Mon, 14 Jul 2008 14:59:30 +0200 (CEST)
Received: from [127.0.0.1] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id 21B97285CB;
	Mon, 14 Jul 2008 14:59:30 +0200 (CEST)
Message-ID: <487B4DAC.5050306@pi.nu>
Date: Mon, 14 Jul 2008 14:59:24 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org, L2VPN <l2vpn@ietf.org>, ccamp <ccamp@ops.ietf.org>, 
	pwe3 <pwe3@ietf.org>
Subject: mpls wg agenda for Dublin
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at viciousnest.net
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

All,

I've just uploaded a preliminary agenda for the MPLS wg meeting in
Dublin.

First: I've a strong feeling that I dropped one request for an agenda
slot, so could all of you who have requested  slots check if it got
on the the agenda.

Second: Pleas note that the agenda covers both MPLS wg meetings in
Dublin, Monday morning (the "traditional" wg meeting) and Wednesday
(the meeting on MPLS-TP). Though this meeting is formally a MPLS
wg meeting, since the focus is MPLS-TP it is from very important
aspects a joint meeting with pwe3, ccamp and l2vpn, this mails is
therefore sent to these working groups as well.

The agenda is available at;

http://www.ietf.org/proceedings/08jul/agenda/mpls.txt

/Loa



-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.nu


From l2vpn-bounces@ietf.org  Mon Jul 14 13:30:05 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C7E428C29B;
	Mon, 14 Jul 2008 13:30:05 -0700 (PDT)
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 26A7A3A6B2D; Mon, 14 Jul 2008 13:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l2vpn-oam-req-frmk-10.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080714203002.26A7A3A6B2D@core3.amsl.com>
Date: Mon, 14 Jul 2008 13:30:02 -0700 (PDT)
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.


	Title           : L2VPN OAM Requirements and Framework
	Author(s)       : D. Mohan, et al.
	Filename        : draft-ietf-l2vpn-oam-req-frmk-10.txt
	Pages           : 36
	Date            : 2008-07-14

This draft provides framework and requirements for Layer 2 Virtual
Private Networks (L2VPN) Operation, Administration and Maintenance
(OAM). The OAM framework is intended to provide OAM layering across
L2VPN services, Pseudo Wires (PWs) and Packet Switched Network (PSN)
tunnels. The requirements are intended to identify OAM requirement
for L2VPN services (i.e. VPLS, VPWS, and IPLS). Furthermore, if
L2VPN services OAM requirements impose specific requirements on PWOAM
and/or PSN OAM, those specific PW and/or PSN OAM requirements
are also identified.


Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.

When these key words are used in consideration of RFC 2119, these

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-oam-req-frmk-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-oam-req-frmk-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-07-14132007.I-D@ietf.org>


--NextPart--


From l2vpn-bounces@ietf.org  Tue Jul 15 09:15:05 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 40DCF28C19F;
	Tue, 15 Jul 2008 09:15:05 -0700 (PDT)
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id CF8123A6A91; Tue, 15 Jul 2008 09:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-vpls-bridge-interop-03.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080715161501.CF8123A6A91@core3.amsl.com>
Date: Tue, 15 Jul 2008 09:15:01 -0700 (PDT)
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.

	Title		: VPLS Interoperability with CE Bridges
	Author(s)	: D. Mohan, A. Sajassi
	Filename	: draft-ietf-l2vpn-vpls-bridge-interop-03.txt
	Pages		: 19
	Date		: 2008-7-15
	
One of the main motivations behind VPLS is its ability to provide 
   connectivity not only among customer routers and servers/hosts but 
   also among customer bridges. VPLS is expected to deliver the same 
   level of service that current enterprise users are accustomed to 
   from their own enterprise bridged networks today or the same level 
   of service that they receive from their Ethernet Service Providers 
   using IEEE bridged networks. 
    
   When CE devices are IEEE bridges, then there are certain issues and 
   challenges that need to be accounted for in a VPLS network. The 
   majority of these issues have currently been addressed in the IEEE 
   802.1ad standard for provider bridges and they need to be addressed 
   for VPLS networks. This draft discusses these issues and wherever 
   possible suggests areas to be explored in rectifying these issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-bridge-interop-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-vpls-bridge-interop-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-7-15091255.I-D@ietf.org>


--NextPart--



From l2vpn-bounces@ietf.org  Tue Jul 15 09:30:04 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D06E03A6B25;
	Tue, 15 Jul 2008 09:30:04 -0700 (PDT)
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id E6FD23A6AEF; Tue, 15 Jul 2008 09:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mib-02.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080715163001.E6FD23A6AEF@core3.amsl.com>
Date: Tue, 15 Jul 2008 09:30:01 -0700 (PDT)
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF.

	Title		: Virtual Private Lan Services (VPLS) Management Information Base
	Author(s)	: R. Mediratta, T. Nadeau, K. Koushik
	Filename	: draft-ietf-l2vpn-vpls-mib-02.txt
	Pages		: 41
	Date		: 2008-7-15
	
This memo defines an experimental portion of the Management 
    Information Base for use with network management protocols in the 
    Internet community.  In particular, it describes managed objects 
    for modeling of Virtual Private LAN services. It needs to be used 
    in conjunction with Pseudo Wire (PW) Management Information Base 
    [PWE3-PW-MIB].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-mib-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l2vpn-vpls-mib-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-7-15092347.I-D@ietf.org>


--NextPart--



From l2vpn-bounces@ietf.org  Tue Jul 15 14:10:45 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF0F93A6872;
	Tue, 15 Jul 2008 14:10:44 -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 697EC3A6872
	for <l2vpn@core3.amsl.com>; Tue, 15 Jul 2008 14:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.395
X-Spam-Level: 
X-Spam-Status: No, score=-0.395 tagged_above=-999 required=5 tests=[AWL=1.854, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 Xi60T3n2LkSD for <l2vpn@core3.amsl.com>;
	Tue, 15 Jul 2008 14:10:43 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 60F503A67BD
	for <l2vpn@ietf.org>; Tue, 15 Jul 2008 14:10:43 -0700 (PDT)
Received: from FRVELSBHS07.ad2.ad.alcatel.com (frvelsbhs07.ad2.ad.alcatel.com
	[155.132.6.79])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m6FLAi7L019533; 
	Tue, 15 Jul 2008 23:10:44 +0200
Received: from [159.217.32.15] ([159.217.32.15]) by
	FRVELSBHS07.ad2.ad.alcatel.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.2499); Tue, 15 Jul 2008 23:10:44 +0200
Message-ID: <487D1259.6020502@alcatel-lucent.fr>
Date: Tue, 15 Jul 2008 23:10:49 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.fr>
Organization: Alcatel-Lucent Bell-Labs
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Shane Amante <shane@castlepoint.net>
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 15 Jul 2008 21:10:44.0096 (UTC)
	FILETIME=[3E738800:01C8E6BF]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

all,

I do support VPMS inclusion.

-m

Shane Amante a écrit :
> Hi all,
> 
> It seems that the PWE3 WG has completed their re-charter activity, which 
> now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
> 
> As a result, we would like to conduct a short call for interest to 
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG charter, 
> before submitting it to the IESG.  Please indicate to the mailing list 
> whether you agree that it should be included in the new L2VPN charter.  
> (Silence will not count as support).  Also, please speak up if you have 
> comments or clarifications with respect to the proposed wording of VPMS.
> 
> Copied below is a full copy of the proposed charter, including VPMS.
> 
> We will close discussion and gauge consensus on this issue in 2 weeks, 
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> 
> Finally, this call *is not* re-opening the entire charter for 
> discussion, rather this is narrowly focused strictly on whether, or not, 
> to add VPMS to the previously agreed upon L2VPN charter.
> 
> -shane & Vach
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 


From l2vpn-bounces@ietf.org  Wed Jul 16 01:02:28 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFB4F3A699F;
	Wed, 16 Jul 2008 01:02:28 -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 9F4633A699F
	for <l2vpn@core3.amsl.com>; Wed, 16 Jul 2008 01:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 sogjMbihyaT5 for <l2vpn@core3.amsl.com>;
	Wed, 16 Jul 2008 01:02:25 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 4A2973A68E6
	for <l2vpn@ietf.org>; Wed, 16 Jul 2008 01:02:25 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m6G82M6q004357; 
	Wed, 16 Jul 2008 10:02:30 +0200
Received: from [172.27.205.154] ([172.27.205.154]) by
	FRVELSBHS06.ad2.ad.alcatel.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.2499); Wed, 16 Jul 2008 10:02:29 +0200
Message-ID: <487DAB15.1000702@alcatel-lucent.fr>
Date: Wed, 16 Jul 2008 10:02:29 +0200
From: Laurent Ciavaglia <Laurent.Ciavaglia@alcatel-lucent.fr>
Organization: Alcatel-Lucent France
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Shane Amante <shane@castlepoint.net>
Subject: Re: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
Content-Type: multipart/mixed; boundary="------------020800050104080900080104"
X-OriginalArrivalTime: 16 Jul 2008 08:02:29.0412 (UTC)
	FILETIME=[4B093640:01C8E71A]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.
--------------020800050104080900080104
Content-Type: multipart/alternative;
 boundary="------------030104030603000909050401"


--------------030104030603000909050401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

All,

I support the addition of VPMS as part of the L2VPN re-charter.

Regards, Laurent.

Shane Amante wrote:
> Hi all,
>
> It seems that the PWE3 WG has completed their re-charter activity, 
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>
> As a result, we would like to conduct a short call for interest to 
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG 
> charter, before submitting it to the IESG.  Please indicate to the 
> mailing list whether you agree that it should be included in the new 
> L2VPN charter.  (Silence will not count as support).  Also, please 
> speak up if you have comments or clarifications with respect to the 
> proposed wording of VPMS.
>
> Copied below is a full copy of the proposed charter, including VPMS.
>
> We will close discussion and gauge consensus on this issue in 2 weeks, 
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>
> Finally, this call *is not* re-opening the entire charter for 
> discussion, rather this is narrowly focused strictly on whether, or 
> not, to add VPMS to the previously agreed upon L2VPN charter.
>
> -shane & Vach
>
> ------------------------------------------------------------------------
>
>
>
>   

--------------030104030603000909050401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
All,<br>
<br>
I support the addition of VPMS as part of the L2VPN re-charter.<br>
<br>
Regards, Laurent.<br>
<br>
Shane Amante wrote:
<blockquote
 cite="mid:1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net"
 type="cite">Hi all,
  <br>
  <br>
It seems that the PWE3 WG has completed their re-charter activity,
which now includes defining P2MP PW's:
  <br>
<a class="moz-txt-link-freetext" href="http://www.ietf.org/html.charters/pwe3-charter.html">http://www.ietf.org/html.charters/pwe3-charter.html</a>
  <br>
  <br>
As a result, we would like to conduct a short call for interest to
include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG
charter, before submitting it to the IESG.&nbsp; Please indicate to the
mailing list whether you agree that it should be included in the new
L2VPN charter.&nbsp; (Silence will not count as support).&nbsp; Also, please
speak up if you have comments or clarifications with respect to the
proposed wording of VPMS.
  <br>
  <br>
Copied below is a full copy of the proposed charter, including VPMS.
  <br>
  <br>
We will close discussion and gauge consensus on this issue in 2 weeks,
on Wednesday, 7/23, at 17:00 MDT, UTC -6.
  <br>
  <br>
Finally, this call *is not* re-opening the entire charter for
discussion, rather this is narrowly focused strictly on whether, or
not, to add VPMS to the previously agreed upon L2VPN charter.
  <br>
  <br>
-shane &amp; Vach
  <br>
  <br>
  <pre wrap="">
<hr size="4" width="90%">


  </pre>
</blockquote>
</body>
</html>

--------------030104030603000909050401--

--------------020800050104080900080104
Content-Type: text/x-vcard; charset=utf-8;
 name="Laurent_Ciavaglia.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Laurent_Ciavaglia.vcf"

begin:vcard
fn:Laurent Ciavaglia
n:Ciavaglia;Laurent
org:;Bell Labs
adr:Route de Villejust;;Copernic - 2F25;Nozay;;91620;FRANCE
email;internet:Laurent.Ciavaglia@alcatel-lucent.fr
title:Semantic and Autonomic Technologies
tel;work:+33 1 3077 2636
tel;fax:+33 1 3077 6175
version:2.1
end:vcard


--------------020800050104080900080104--


From l2vpn-bounces@ietf.org  Wed Jul 16 12:30:55 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A461F3A6988;
	Wed, 16 Jul 2008 12:30:55 -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 ED8863A6988
	for <l2vpn@core3.amsl.com>; Wed, 16 Jul 2008 12:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 oPng0foN5FOy for <l2vpn@core3.amsl.com>;
	Wed, 16 Jul 2008 12:30:54 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 2E53D3A681A
	for <l2vpn@ietf.org>; Wed, 16 Jul 2008 12:30:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,199,1215388800"; d="scan'208";a="53908970"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-1.cisco.com with ESMTP; 16 Jul 2008 19:31:01 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6GJV1TL002068
	for <l2vpn@ietf.org>; Wed, 16 Jul 2008 15:31:01 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6GJV1aX010170
	for <l2vpn@ietf.org>; Wed, 16 Jul 2008 19:31:01 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 16 Jul 2008 15:31:01 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Wed, 16 Jul 2008 15:31:01 -0400
Message-ID: <DD7E9F364F33B54881C225192D4872D7A874FA@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <mailman.4032.1215592400.4989.l2vpn@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: AcjhnoZQcI8UzCI3QgO+hdXKoIiZywF222Pg
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: <l2vpn@ietf.org>
X-OriginalArrivalTime: 16 Jul 2008 19:31:01.0436 (UTC)
	FILETIME=[7AEBCFC0:01C8E77A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1392; t=1216236661;
	x=1217100661; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lufang@cisco.com;
	z=From:=20=22Luyuan=20Fang=20(lufang)=22=20<lufang@cisco.com >
	|Subject:=20RE=3A=20Re-charter=20Take=202=3A=20Virtual=20Pr
	ivate=20Multicast=20Service=20(VPMS) |Sender:=20
	|To:=20<l2vpn@ietf.org>;
	bh=Qcs3PLzvA5XX8RSYvxCivJ2E13jqyNlPXfitvtWvQIw=;
	b=Vn7Wcoi8PTdCQROxaPh9kVBz1OmQxGEOlQFGwol/R6OCh1j9Hb+HzC7wFt
	6ukAui6ox3tmlT65bfz5vEQ4di4GigyFe4fJeNLJbb6z4ZjB1u8cLloFaL/2
	nI7wMTfyXS;
Authentication-Results: rtp-dkim-2; header.From=lufang@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Support.
Luyuan=20

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf

> Of Shane Amante
> Sent: Wednesday, July 09, 2008 12:17 PM
> To: l2vpn@ietf.org
> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
>=20
> Hi all,
>=20
> It seems that the PWE3 WG has completed their re-charter activity,=20
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>=20
> As a result, we would like to conduct a short call for interest to=20
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG=20
> charter, before submitting it to the IESG.
> Please indicate to the mailing list whether you agree that it should=20
> be included in the new L2VPN charter.  (Silence will not count as=20
> support).  Also, please speak up if you have comments or=20
> clarifications with respect to the proposed wording of VPMS.
>=20
> Copied below is a full copy of the proposed charter, including VPMS.
>=20
> We will close discussion and gauge consensus on this issue in
> 2 weeks, on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>=20
> Finally, this call *is not* re-opening the entire charter for=20
> discussion, rather this is narrowly focused strictly on whether, or=20
> not, to add VPMS to the previously agreed upon L2VPN charter.
>=20
> -shane & Vach
>=20


From l2vpn-bounces@ietf.org  Thu Jul 17 05:38:01 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29F133A67FC;
	Thu, 17 Jul 2008 05:38:01 -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 33A2D3A682F
	for <l2vpn@core3.amsl.com>; Thu, 17 Jul 2008 05:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[AWL=0.206, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 rKdM7Id+Bj11 for <l2vpn@core3.amsl.com>;
	Thu, 17 Jul 2008 05:37:58 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5])
	by core3.amsl.com (Postfix) with ESMTP id 3237C3A6407
	for <l2vpn@ietf.org>; Thu, 17 Jul 2008 05:37:58 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m6HCbxub014860; 
	Thu, 17 Jul 2008 14:37:59 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by
	FRVELSBHS06.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 17 Jul 2008 14:37:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Thu, 17 Jul 2008 14:37:28 +0200
Message-ID: <00275A5B436CA441900CB10936742A38CE1B74@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: AcjhckO05nS5GWTFSlWGXsC5RAFXwQGl3ABA
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 17 Jul 2008 12:37:59.0543 (UTC)
	FILETIME=[F22CC870:01C8E809]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

VPMS should be included in the new L2VPN charter.
-d.=20

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20
> On Behalf Of Shane Amante
> Sent: Wednesday, July 09, 2008 5:17 AM
> To: l2vpn@ietf.org
> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
>=20
> Hi all,
>=20
> It seems that the PWE3 WG has completed their re-charter activity, =20
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
>=20
> As a result, we would like to conduct a short call for interest to =20
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG =20
> charter, before submitting it to the IESG.  Please indicate to the =20
> mailing list whether you agree that it should be included in the new =20
> L2VPN charter.  (Silence will not count as support).  Also, please =20
> speak up if you have comments or clarifications with respect to the =20
> proposed wording of VPMS.
>=20
> Copied below is a full copy of the proposed charter, including VPMS.
>=20
> We will close discussion and gauge consensus on this issue in=20
> 2 weeks, =20
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
>=20
> Finally, this call *is not* re-opening the entire charter for =20
> discussion, rather this is narrowly focused strictly on whether, or =20
> not, to add VPMS to the previously agreed upon L2VPN charter.
>=20
> -shane & Vach
>=20
>=20


From l2vpn-bounces@ietf.org  Sun Jul 20 09:20:26 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C471E3A69CA;
	Sun, 20 Jul 2008 09:20:26 -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 D5D5C28C153
	for <l2vpn@core3.amsl.com>; Fri, 11 Jul 2008 13:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 H+7H5ADmcBtb for <l2vpn@core3.amsl.com>;
	Fri, 11 Jul 2008 13:23:31 -0700 (PDT)
Received: from mail143.messagelabs.com (mail143.messagelabs.com
	[216.82.254.35])
	by core3.amsl.com (Postfix) with ESMTP id EF43628C0E2
	for <l2vpn@ietf.org>; Fri, 11 Jul 2008 13:23:30 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: bensons@savvis.net
X-Msg-Ref: server-8.tower-143.messagelabs.com!1215807828!28480047!1
X-StarScan-Version: 5.5.12.14.2; banners=savvis.net,-,-
X-Originating-IP: [216.91.182.151]
Received: (qmail 13406 invoked from network); 11 Jul 2008 20:23:48 -0000
Received: from sl6edge1.savvis.net (HELO SL6EDGE1.savvis.net) (216.91.182.151)
	by server-8.tower-143.messagelabs.com with RC4-SHA encrypted SMTP;
	11 Jul 2008 20:23:48 -0000
Received: from sl6smtp2.savvis.ad.savvis.net (10.12.134.211) by
	SL6EDGE1.savvis.net (216.91.182.151) with Microsoft SMTP Server id
	8.1.263.0; Fri, 11 Jul 2008 15:23:53 -0500
Received: from sl6exchbe1.savvis.ad.savvis.net ([10.12.134.212]) by
	sl6smtp2.savvis.ad.savvis.net with Microsoft SMTPSVC(6.0.3790.3959);
	Fri, 11 Jul 2008 15:23:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Fri, 11 Jul 2008 15:23:08 -0500
Message-ID: <4B5ACF3E973474489456A00BD0F707AF01704FB2@sl6exchbe1.savvis.ad.savvis.net>
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Thread-Index: Acjhcj9TJ1b1apT6QQKOmM55d5c+VgBV4EoA
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
From: "Schliesser, Benson" <bensons@savvis.net>
To: Shane Amante <shane@castlepoint.net>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 11 Jul 2008 20:23:41.0155 (UTC)
	FILETIME=[0231EB30:01C8E394]
X-Mailman-Approved-At: Sun, 20 Jul 2008 09:20:26 -0700
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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


I=20support=20this=20work=20as=20part=20of=20the=20WG's=20charter.

-Benson
=20

>=20-----Original=20Message-----
>=20From:=20l2vpn-bounces@ietf.org=20[mailto:l2vpn-bounces@ietf.org]=20
>=20On=20Behalf=20Of=20Shane=20Amante
>=20Sent:=20Tuesday,=20July=2008,=202008=2010:17=20PM
>=20To:=20l2vpn@ietf.org
>=20Subject:=20Re-charter=20Take=202:=20Virtual=20Private=20Multicast=20Se=
rvice=20(VPMS)
>=20
>=20Hi=20all,
>=20
>=20It=20seems=20that=20the=20PWE3=20WG=20has=20completed=20their=20re-cha=
rter=20activity,=20=20
>=20which=20now=20includes=20defining=20P2MP=20PW's:
>=20http://www.ietf.org/html.charters/pwe3-charter.html
>=20
>=20As=20a=20result,=20we=20would=20like=20to=20conduct=20a=20short=20call=
=20for=20interest=20to=20=20
>=20include=20VPMS=20(likely=20utilizing=20P2MP=20PW's)=20into=20the=20new=
=20L2VPN=20WG=20=20
>=20charter,=20before=20submitting=20it=20to=20the=20IESG.=20=20Please=20i=
ndicate=20to=20the=20=20
>=20mailing=20list=20whether=20you=20agree=20that=20it=20should=20be=20inc=
luded=20in=20the=20new=20=20
>=20L2VPN=20charter.=20=20(Silence=20will=20not=20count=20as=20support).=20=
=20Also,=20please=20=20
>=20speak=20up=20if=20you=20have=20comments=20or=20clarifications=20with=20=
respect=20to=20the=20=20
>=20proposed=20wording=20of=20VPMS.
>=20
>=20Copied=20below=20is=20a=20full=20copy=20of=20the=20proposed=20charter,=
=20including=20VPMS.
>=20
>=20We=20will=20close=20discussion=20and=20gauge=20consensus=20on=20this=20=
issue=20in=20
>=202=20weeks,=20=20
>=20on=20Wednesday,=207/23,=20at=2017:00=20MDT,=20UTC=20-6.
>=20
>=20Finally,=20this=20call=20*is=20not*=20re-opening=20the=20entire=20char=
ter=20for=20=20
>=20discussion,=20rather=20this=20is=20narrowly=20focused=20strictly=20on=20=
whether,=20or=20=20
>=20not,=20to=20add=20VPMS=20to=20the=20previously=20agreed=20upon=20L2VPN=
=20charter.
>=20
>=20-shane=20&=20Vach
>=20
>=20

______________________________________________________________________
This=20message=20contains=20information=20which=20may=20be=20confidential=20=
and/or=20privileged.=20Unless=20you=20are=20the=20intended=20recipient=20(=
or=20authorized=20to=20receive=20for=20the=20intended=20recipient),=20you=20=
may=20not=20read,=20use,=20copy=20or=20disclose=20to=20anyone=20the=20mess=
age=20or=20any=20information=20contained=20in=20the=20message.=20If=20you=20=
have=20received=20the=20message=20in=20error,=20please=20advise=20the=20se=
nder=20by=20reply=20e-mail=20and=20delete=20the=20message=20and=20any=20at=
tachment(s)=20thereto=20without=20retaining=20any=20copies.
______________________________________________________________________


From l2vpn-bounces@ietf.org  Sun Jul 20 09:20:27 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B2EF28C10C;
	Sun, 20 Jul 2008 09:20:27 -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 8824B3A6B1B
	for <l2vpn@core3.amsl.com>; Thu, 17 Jul 2008 12:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.467
X-Spam-Level: 
X-Spam-Status: No, score=-1.467 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, J_CHICKENPOX_57=0.6,
	RCVD_IN_DNSWL_LOW=-1]
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 wo-7NFkdzbZn for <l2vpn@core3.amsl.com>;
	Thu, 17 Jul 2008 12:16:08 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150])
	by core3.amsl.com (Postfix) with ESMTP id 65BEE3A69B3
	for <l2vpn@ietf.org>; Thu, 17 Jul 2008 12:16:08 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 17 Jul 2008 20:16:39 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 17 Jul 2008 20:16:38 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1216322196801; Thu, 17 Jul 2008 20:16:36 +0100
Received: from mut.jungle.bt.co.uk ([10.73.81.228])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	m6HJGOFJ012556; Thu, 17 Jul 2008 20:16:33 +0100
Message-Id: <200807171916.m6HJGOFJ012556@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 17 Jul 2008 20:16:24 +0100
To: Loa Andersson <loa@pi.nu>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
In-Reply-To: <4875F9A1.5070408@pi.nu>
References: <4875F9A1.5070408@pi.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 17 Jul 2008 19:16:38.0884 (UTC)
	FILETIME=[A3369240:01C8E841]
X-Mailman-Approved-At: Sun, 20 Jul 2008 09:20:26 -0700
Cc: L2VPN <l2vpn@ietf.org>, mpls@ietf.org, tsvwg@ietf.org,
	ccamp <ccamp@ops.ietf.org>, pwe3 <pwe3@ietf.org>, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Loa,

I believe this draft has no technical effect. However there is some 
truth in the idea that names are important.

So, let's set aside a few clock cycles to consider this...

1/ Is CoS a good description of ECN? Given RFC5129 (Using the EXP 
field for ECN in MPLS), is it really appropriate now to call this a CoS field?

Thinking out loud...
- CoS is a signal from an ingress to the interior (a request for a 
certain class of service),
- whereas ECN is a signal from the interior forwarding plane to the 
egress (a response from the interior saying whether the class of 
service requested was congested).

The way 5129 was done, two (or more) EXP codepoints can be designated 
as the same CoS, but one can be used to say "this packet experienced 
congestion when using this CoS", while the other says "it didn't". 
So, I guess I could live with this field being called CoS, even 
though it's not strictly correct. I can't think of anything better.


2/ BTW, Thanks for pointing out that the RFC Index doesn't identify 
RFC5129 or RFC3270 as updates to RFC3032.

According to a recent discussion on TSVWG with Bob Braden, the 
annotation of the RFC Index is the responsibility of the RFC Editor, 
and doesn't need to be driven by text in RFCs. So we can send an 
email to the RFC Editor  at any time asking for annotation to be 
added to the index.

If no-one objects on this thread, will you be doing that? If not, I can.

But does 5129 UPDATE 3270? I don't believe it does. 5129 deliberately 
doesn't change or contradict anything in 3270. It complements it.


Thoughts?


Bob

At 12:59 10/07/2008, Loa Andersson wrote:
>All,
>
>this mail initiates a two week multiple-working group last call on
>
>draft-ietf-mpls-cosfield-def-04.txt
>
>Background:
>
>The name "EXP field" of a three bit field in the MPLS shim header,
>and the statement in RFC3032 "For experimental use" has led other
>SDOs to believe that this field could be used for any type of
>experiments. The field has however from the start been intended to
>carry Class of Service (CoS) information.
>
>The draft therefore renames the field "Class of Service (CoS) Field".
>
>This is an update of RFC3032, and also of drafts that builds on
>RFC3032. This multiple-working group last call is therefore sent to
>working groups with RFCs that has been updated.
>
>The document has been through wg last call in the mpls working group,
>which I don't think will stop that wg producing new comments now,
>nor should it :) .
>
>This working group last call is for CCAMP, L2VPN, PWE3 and TSVWG.
>
>Since this is also of interest in the work we started on a
>Transport Profile for MPLS (MPLS-TP) we are also sending it to the
>Ad HoC Team on MPLS in the ITU-T.
>
>Please review and send comments to the mpls wg mailing list, or to
>the mailing list for mpls-tp discussion that just been set up:
>
>mpls-tp@ietf.org
>
>or directly to the mpls wg co-chairs before e.o.b. July 24.
>
>/Loa
>
>--
>Loa Andersson
>
>Principal Networking Architect
>Acreo AB                           phone:  +46 8 632 77 14
>Isafjordsgatan 22                  mobile: +46 739 81 21 64
>Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu

____________________________________________________________________________
Notice: This contribution is the personal view of the author and does 
not necessarily reflect the technical nor commercial direction of BT plc.
____________________________________________________________________________
Bob Briscoe,                           Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 




From l2vpn-bounces@ietf.org  Sun Jul 20 14:02:15 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9893E3A6819;
	Sun, 20 Jul 2008 14:02:15 -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 D85F23A6819
	for <l2vpn@core3.amsl.com>; Sun, 20 Jul 2008 14:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.017
X-Spam-Level: 
X-Spam-Status: No, score=-1.017 tagged_above=-999 required=5 tests=[AWL=0.100, 
	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 j1VZoisqD6zJ for <l2vpn@core3.amsl.com>;
	Sun, 20 Jul 2008 14:02:14 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 0921E3A6778
	for <l2vpn@ietf.org>; Sun, 20 Jul 2008 14:02:14 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id BBA282684EA; Sun, 20 Jul 2008 15:02:47 -0600 (MDT)
Received: from pmac.castlepoint.net (71-218-96-35.hlrn.qwest.net
	[71.218.96.35]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	for l2vpn@ietf.org; Sun, 20 Jul 2008 15:02:47 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.218.96.35;
	client-port=2338; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <52D1DED1-549C-4314-B73B-D0E9CACCB62A@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: l2vpn@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Subject: IETF 72: Draft Agenda Posted
Date: Sun, 20 Jul 2008 15:02:32 -0600
X-Mailer: Apple Mail (2.928.1)
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

The draft agenda can be found here: http://www.ietf.org/proceedings/08jul/agenda/l2vpn.txt

Please let the chairs know if we've missed any requests.

Since our meeting is Monday afternoon, we kindly request that all  
presenters send us their slides no later than Sunday evening so they  
may be posted to the Meeting Materials Web site, prior to the start of  
the WG meeting.

-shane


From l2vpn-bounces@ietf.org  Mon Jul 21 00:23:39 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B368C3A6923;
	Mon, 21 Jul 2008 00:23:39 -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 1E0EE3A68AB;
	Mon, 21 Jul 2008 00:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_57=0.6]
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 1Bzn7xHGYJ3v; Mon, 21 Jul 2008 00:23:37 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64])
	by core3.amsl.com (Postfix) with ESMTP id E2D3C3A6806;
	Mon, 21 Jul 2008 00:23:36 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K4C002S0HWDTJ@szxga01-in.huawei.com>; Mon,
	21 Jul 2008 15:24:13 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K4C008CHHWDAD@szxga01-in.huawei.com>; Mon,
	21 Jul 2008 15:24:13 +0800 (CST)
Received: from M00900002 ([10.47.95.249])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K4C00MB8HVZB5@szxml03-in.huawei.com>; Mon,
	21 Jul 2008 15:24:13 +0800 (CST)
Date: Mon, 21 Jul 2008 09:24:02 +0200
From: Maarten Vissers <maarten.vissers@huawei.com>
Subject: RE: [Tsvwg] multiple-working group last call
	ondraft-ietf-mpls-cosfield-def-04.txt
In-reply-to: <200807171916.m6HJGOFJ012556@bagheera.jungle.bt.co.uk>
To: 'Bob Briscoe' <rbriscoe@jungle.bt.co.uk>, 'Loa Andersson' <loa@pi.nu>
Message-id: <001201c8eb02$c32f5460$f95f2f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcjqhLMDkrxTKH/TRL+HDl3R88PKvgAe/IRw
Cc: 'L2VPN' <l2vpn@ietf.org>, mpls@ietf.org, tsvwg@ietf.org,
	'ccamp' <ccamp@ops.ietf.org>, 'pwe3' <pwe3@ietf.org>, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Bob, Loa,

I expect that the EXP bits carry 'Priority' and 'Drop Eligible' information.
Is the term 'Class of Service' representing both elements?

For the case of VPLS, the 'PW label stack entry header' replaces the 'VLAN
Tag' and carries the 'vlan_identifier', 'priority' and 'drop_eligible'
parameter information of the 802.1Q (E)M_UNITDATA primitive signals. 

The EXP field in this PW label stack entry then carries the Priority Code
Point (PCP) information as specified in clause 6.7.3/802.1ad. I refer to
this EXP field often as M-PCP field, and to the PW label stack entry header
as 'MPLS label stack entry based VLAN (M-VLAN) Tag'. The 20-bit PW label
field carries a 20-bit M-VID.

Regards,
Maarten

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of
Bob Briscoe
Sent: 17 July 2008 21:16
To: Loa Andersson
Cc: L2VPN; mpls@ietf.org; tsvwg@ietf.org; ccamp; pwe3; ahtmpls@itu.int
Subject: Re: [Tsvwg] multiple-working group last call
ondraft-ietf-mpls-cosfield-def-04.txt

Loa,

I believe this draft has no technical effect. However there is some truth in
the idea that names are important.

So, let's set aside a few clock cycles to consider this...

1/ Is CoS a good description of ECN? Given RFC5129 (Using the EXP field for
ECN in MPLS), is it really appropriate now to call this a CoS field?

Thinking out loud...
- CoS is a signal from an ingress to the interior (a request for a certain
class of service),
- whereas ECN is a signal from the interior forwarding plane to the egress
(a response from the interior saying whether the class of service requested
was congested).

The way 5129 was done, two (or more) EXP codepoints can be designated as the
same CoS, but one can be used to say "this packet experienced congestion
when using this CoS", while the other says "it didn't". 
So, I guess I could live with this field being called CoS, even though it's
not strictly correct. I can't think of anything better.


2/ BTW, Thanks for pointing out that the RFC Index doesn't identify
RFC5129 or RFC3270 as updates to RFC3032.

According to a recent discussion on TSVWG with Bob Braden, the annotation of
the RFC Index is the responsibility of the RFC Editor, and doesn't need to
be driven by text in RFCs. So we can send an email to the RFC Editor  at any
time asking for annotation to be added to the index.

If no-one objects on this thread, will you be doing that? If not, I can.

But does 5129 UPDATE 3270? I don't believe it does. 5129 deliberately
doesn't change or contradict anything in 3270. It complements it.


Thoughts?


Bob

At 12:59 10/07/2008, Loa Andersson wrote:
>All,
>
>this mail initiates a two week multiple-working group last call on
>
>draft-ietf-mpls-cosfield-def-04.txt
>
>Background:
>
>The name "EXP field" of a three bit field in the MPLS shim header,
>and the statement in RFC3032 "For experimental use" has led other
>SDOs to believe that this field could be used for any type of
>experiments. The field has however from the start been intended to
>carry Class of Service (CoS) information.
>
>The draft therefore renames the field "Class of Service (CoS) Field".
>
>This is an update of RFC3032, and also of drafts that builds on
>RFC3032. This multiple-working group last call is therefore sent to
>working groups with RFCs that has been updated.
>
>The document has been through wg last call in the mpls working group,
>which I don't think will stop that wg producing new comments now,
>nor should it :) .
>
>This working group last call is for CCAMP, L2VPN, PWE3 and TSVWG.
>
>Since this is also of interest in the work we started on a
>Transport Profile for MPLS (MPLS-TP) we are also sending it to the
>Ad HoC Team on MPLS in the ITU-T.
>
>Please review and send comments to the mpls wg mailing list, or to
>the mailing list for mpls-tp discussion that just been set up:
>
>mpls-tp@ietf.org
>
>or directly to the mpls wg co-chairs before e.o.b. July 24.
>
>/Loa
>
>--
>Loa Andersson
>
>Principal Networking Architect
>Acreo AB                           phone:  +46 8 632 77 14
>Isafjordsgatan 22                  mobile: +46 739 81 21 64
>Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.nu

____________________________________________________________________________
Notice: This contribution is the personal view of the author and does 
not necessarily reflect the technical nor commercial direction of BT plc.
____________________________________________________________________________
Bob Briscoe,                           Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196







From l2vpn-bounces@ietf.org  Mon Jul 21 01:37:24 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 232323A68B0;
	Mon, 21 Jul 2008 01:37:24 -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 C54EF3A688C;
	Mon, 21 Jul 2008 01:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.924
X-Spam-Level: 
X-Spam-Status: No, score=-1.924 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, J_CHICKENPOX_57=0.6]
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 tJ2OpThGH1Wp; Mon, 21 Jul 2008 01:37:21 -0700 (PDT)
Received: from neo.viciousnest.net (neo.viciousnest.net [192.71.80.124])
	by core3.amsl.com (Postfix) with ESMTP id 6EFB23A684B;
	Mon, 21 Jul 2008 01:37:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by neo.viciousnest.net (Postfix) with ESMTP id E99BF3F27E;
	Mon, 21 Jul 2008 10:37:54 +0200 (CEST)
Received: from neo.viciousnest.net ([127.0.0.1])
	by localhost (neo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 29377-03; Mon, 21 Jul 2008 10:37:50 +0200 (CEST)
Received: from [127.0.0.1] (pat.acreo.se [217.151.195.214])
	by neo.viciousnest.net (Postfix) with ESMTP id 962343F25D;
	Mon, 21 Jul 2008 10:37:49 +0200 (CEST)
Message-ID: <48844AD7.8050305@pi.nu>
Date: Mon, 21 Jul 2008 10:37:43 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
References: <4875F9A1.5070408@pi.nu>
	<200807171916.m6HJGOFJ012556@bagheera.jungle.bt.co.uk>
In-Reply-To: <200807171916.m6HJGOFJ012556@bagheera.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at viciousnest.net
Cc: L2VPN <l2vpn@ietf.org>, mpls@ietf.org, tsvwg@ietf.org,
	ccamp <ccamp@ops.ietf.org>, pwe3 <pwe3@ietf.org>, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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


Bob,

thanks for useful comments :)

Bob Briscoe wrote:
> Loa,
> 
> I believe this draft has no technical effect. However there is some 
> truth in the idea that names are important.
> 
> So, let's set aside a few clock cycles to consider this...
> 
> 1/ Is CoS a good description of ECN? Given RFC5129 (Using the EXP field 
> for ECN in MPLS), is it really appropriate now to call this a CoS field?
> 
> Thinking out loud...
> - CoS is a signal from an ingress to the interior (a request for a 
> certain class of service),
> - whereas ECN is a signal from the interior forwarding plane to the 
> egress (a response from the interior saying whether the class of service 
> requested was congested).
> 
> The way 5129 was done, two (or more) EXP codepoints can be designated as 
> the same CoS, but one can be used to say "this packet experienced 
> congestion when using this CoS", while the other says "it didn't". So, I 
> guess I could live with this field being called CoS, even though it's 
> not strictly correct. I can't think of anything better.

We had the same discussion when we started to discuss this draft, we
wanted to find a name the covered both cases. We just couldn't come
with a better name, so we said "Let us call it 'CoS Field'" and change
it someone comes up with something better.

I'm still open to do that change, but time is kind of running out, the
latest point in time we can do this change is an RFC editor note, when
the IESG has approved the document.

> 
> 
> 2/ BTW, Thanks for pointing out that the RFC Index doesn't identify 
> RFC5129 or RFC3270 as updates to RFC3032.
> 
> According to a recent discussion on TSVWG with Bob Braden, the 
> annotation of the RFC Index is the responsibility of the RFC Editor, and 
> doesn't need to be driven by text in RFCs. So we can send an email to 
> the RFC Editor  at any time asking for annotation to be added to the index.
> 
> If no-one objects on this thread, will you be doing that? If not, I can.

I'll do it.

> 
> But does 5129 UPDATE 3270? I don't believe it does. 5129 deliberately 
> doesn't change or contradict anything in 3270. It complements it.

I tend to agree, but have a problem how to capture this. We have

obsoletes
obsoleted by
updates
updated by

Would the following change to the paragraph in the ID suffice:

                                    "We recommend this scheme, which we
       call `per-domain ECT checking', and define it more precisely in
       the following section.  Its chief drawback is that it can cause
       packets to be forwarded after encountering congestion only to be
       dropped at the egress of the MPLS domain.  The rationale for this
       decision is given in Section 8.1.  This scheme is an update to RFC
       3032 [RFC3032] and RFC 3270 [RFC3270] is extended to allow for
       CoS Field code points to encode ECN information."

and - yes if you agree and could improve on grammar that would be great.

"The problem" I have is that even with the changed version this is an
"updates/updated by" the way it is used by the RFC Editor. We want to
point to this extension from 3270 to give implementation context.


/Loa

PS
you helped me pick another nit alos 5219 should be 5129

> 
> 
> Thoughts?
> 
> 
> Bob
> 
> At 12:59 10/07/2008, Loa Andersson wrote:
>> All,
>>
>> this mail initiates a two week multiple-working group last call on
>>
>> draft-ietf-mpls-cosfield-def-04.txt
>>
>> Background:
>>
>> The name "EXP field" of a three bit field in the MPLS shim header,
>> and the statement in RFC3032 "For experimental use" has led other
>> SDOs to believe that this field could be used for any type of
>> experiments. The field has however from the start been intended to
>> carry Class of Service (CoS) information.
>>
>> The draft therefore renames the field "Class of Service (CoS) Field".
>>
>> This is an update of RFC3032, and also of drafts that builds on
>> RFC3032. This multiple-working group last call is therefore sent to
>> working groups with RFCs that has been updated.
>>
>> The document has been through wg last call in the mpls working group,
>> which I don't think will stop that wg producing new comments now,
>> nor should it :) .
>>
>> This working group last call is for CCAMP, L2VPN, PWE3 and TSVWG.
>>
>> Since this is also of interest in the work we started on a
>> Transport Profile for MPLS (MPLS-TP) we are also sending it to the
>> Ad HoC Team on MPLS in the ITU-T.
>>
>> Please review and send comments to the mpls wg mailing list, or to
>> the mailing list for mpls-tp discussion that just been set up:
>>
>> mpls-tp@ietf.org
>>
>> or directly to the mpls wg co-chairs before e.o.b. July 24.
>>
>> /Loa
>>
>> -- 
>> Loa Andersson
>>
>> Principal Networking Architect
>> Acreo AB                           phone:  +46 8 632 77 14
>> Isafjordsgatan 22                  mobile: +46 739 81 21 64
>> Kista, Sweden                      email:  loa.andersson@acreo.se
>>                                            loa@pi.nu
> 
> ____________________________________________________________________________ 
> 
> Notice: This contribution is the personal view of the author and does 
> not necessarily reflect the technical nor commercial direction of BT plc.
> ____________________________________________________________________________ 
> 
> Bob Briscoe,                           Networks Research Centre, BT 
> Research
> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 
> 645196
> 


-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson@acreo.se
                                            loa@pi.nu


From l2vpn-bounces@ietf.org  Mon Jul 21 07:06:50 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B291E3A6910;
	Mon, 21 Jul 2008 07:06:50 -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 C4DB43A6910;
	Mon, 21 Jul 2008 07:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 C41YJCyBHUpl; Mon, 21 Jul 2008 07:06:49 -0700 (PDT)
Received: from a2s13.a2hosting.com (a2s13.a2hosting.com [69.39.88.160])
	by core3.amsl.com (Postfix) with ESMTP id D06583A6846;
	Mon, 21 Jul 2008 07:06:48 -0700 (PDT)
Received: from adsl-76-242-40-69.dsl.sbndin.sbcglobal.net ([76.242.40.69]
	helo=[192.168.1.113])
	by a2s13.a2hosting.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69) (envelope-from <johnkenney@alumni.nd.edu>)
	id 1KKw2p-0006T9-5d; Mon, 21 Jul 2008 10:07:19 -0400
Message-ID: <48849819.3000808@alumni.nd.edu>
Date: Mon, 21 Jul 2008 10:07:21 -0400
From: John Kenney <johnkenney@alumni.nd.edu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
Subject: Re: [mpls] [Tsvwg] multiple-working group last call
	on	draft-ietf-mpls-cosfield-def-04.txt
References: <4875F9A1.5070408@pi.nu>	<200807171916.m6HJGOFJ012556@bagheera.jungle.bt.co.uk>
	<48844AD7.8050305@pi.nu>
In-Reply-To: <48844AD7.8050305@pi.nu>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - a2s13.a2hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - alumni.nd.edu
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: L2VPN <l2vpn@ietf.org>, mpls@ietf.org, tsvwg@ietf.org,
	Bob Briscoe <rbriscoe@jungle.bt.co.uk>,
	ccamp <ccamp@ops.ietf.org>, pwe3 <pwe3@ietf.org>, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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,

This is a good draft.  It's time to rename the EXP field.  While CoS 
Field may have been a good choice at one time, we've now heard from many 
who think it is too narrow for current usage of this field.

I suggest "Traffic Management Field".

Traffic management is a common, generic, and concise term.  It covers 
all current uses of the field: scheduling class, drop priority, and 
congestion notification. CoS really only covers the first.  Traffic 
management is well-scoped to this purpose, and clearly preferable to CoS 
in my opinion.

In terms of the draft, I think a simple global substitution of "traffic 
management" for "class of service" and of "TM" for "CoS" should suffice.

I think in the long run we'll be glad if we bite the bullet now and make 
this change.

Best Regards,
John


Loa Andersson wrote:
>
> Bob,
>
> thanks for useful comments :)
>
> Bob Briscoe wrote:
>> Loa,
>>
>> I believe this draft has no technical effect. However there is some 
>> truth in the idea that names are important.
>>
>> So, let's set aside a few clock cycles to consider this...
>>
>> 1/ Is CoS a good description of ECN? Given RFC5129 (Using the EXP 
>> field for ECN in MPLS), is it really appropriate now to call this a 
>> CoS field?
>>
>> Thinking out loud...
>> - CoS is a signal from an ingress to the interior (a request for a 
>> certain class of service),
>> - whereas ECN is a signal from the interior forwarding plane to the 
>> egress (a response from the interior saying whether the class of 
>> service requested was congested).
>>
>> The way 5129 was done, two (or more) EXP codepoints can be designated 
>> as the same CoS, but one can be used to say "this packet experienced 
>> congestion when using this CoS", while the other says "it didn't". 
>> So, I guess I could live with this field being called CoS, even 
>> though it's not strictly correct. I can't think of anything better.
>
> We had the same discussion when we started to discuss this draft, we
> wanted to find a name the covered both cases. We just couldn't come
> with a better name, so we said "Let us call it 'CoS Field'" and change
> it someone comes up with something better.
>
> I'm still open to do that change, but time is kind of running out, the
> latest point in time we can do this change is an RFC editor note, when
> the IESG has approved the document.



From l2vpn-bounces@ietf.org  Mon Jul 21 08:14:10 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96B403A68A7;
	Mon, 21 Jul 2008 08:14:10 -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 302203A67F3;
	Mon, 21 Jul 2008 08:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.785
X-Spam-Level: 
X-Spam-Status: No, score=-2.785 tagged_above=-999 required=5 tests=[AWL=0.814, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Tp5aOaFgyStf; Mon, 21 Jul 2008 08:14:08 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151])
	by core3.amsl.com (Postfix) with ESMTP id 012C03A689C;
	Mon, 21 Jul 2008 08:14:07 -0700 (PDT)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.109]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 Jul 2008 16:14:46 +0100
Received: from 10.215.40.109 ([10.215.40.109]) by
	E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.32]) with
	Microsoft Exchange Server HTTP-DAV ; Mon, 21 Jul 2008 15:14:45 +0000
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Mon, 21 Jul 2008 16:14:43 +0100
Subject: Re: [mpls] [Tsvwg] multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: John Kenney <johnkenney@alumni.nd.edu>,
	Loa Andersson <loa@pi.nu>
Message-ID: <C4AA6673.892F%benjamin.niven-jenkins@bt.com>
Thread-Topic: [mpls] [Tsvwg] multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
Thread-Index: AcjrRIC5+eyB+rhTFUGGUR5GYPN9AA==
In-Reply-To: <48849819.3000808@alumni.nd.edu>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 21 Jul 2008 15:14:46.0534 (UTC)
	FILETIME=[82D4B260:01C8EB44]
Cc: L2VPN <l2vpn@ietf.org>, mpls@ietf.org, tsvwg@ietf.org,
	Bob Briscoe <rbriscoe@jungle.bt.co.uk>,
	ccamp <ccamp@ops.ietf.org>, pwe3 <pwe3@ietf.org>, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

I'm not precious about which term we use but if we use Traffic Management I
think a paragraph should be added explaining what is meant to put it in
context.

Ben



On 21/07/2008 15:07, "John Kenney" <johnkenney@alumni.nd.edu> wrote:

> Hi Loa,
> 
> This is a good draft.  It's time to rename the EXP field.  While CoS
> Field may have been a good choice at one time, we've now heard from many
> who think it is too narrow for current usage of this field.
> 
> I suggest "Traffic Management Field".
> 
> Traffic management is a common, generic, and concise term.  It covers
> all current uses of the field: scheduling class, drop priority, and
> congestion notification. CoS really only covers the first.  Traffic
> management is well-scoped to this purpose, and clearly preferable to CoS
> in my opinion.
> 
> In terms of the draft, I think a simple global substitution of "traffic
> management" for "class of service" and of "TM" for "CoS" should suffice.
> 
> I think in the long run we'll be glad if we bite the bullet now and make
> this change.
> 
> Best Regards,
> John
> 
> 
> Loa Andersson wrote:
>> 
>> Bob,
>> 
>> thanks for useful comments :)
>> 
>> Bob Briscoe wrote:
>>> Loa,
>>> 
>>> I believe this draft has no technical effect. However there is some
>>> truth in the idea that names are important.
>>> 
>>> So, let's set aside a few clock cycles to consider this...
>>> 
>>> 1/ Is CoS a good description of ECN? Given RFC5129 (Using the EXP
>>> field for ECN in MPLS), is it really appropriate now to call this a
>>> CoS field?
>>> 
>>> Thinking out loud...
>>> - CoS is a signal from an ingress to the interior (a request for a
>>> certain class of service),
>>> - whereas ECN is a signal from the interior forwarding plane to the
>>> egress (a response from the interior saying whether the class of
>>> service requested was congested).
>>> 
>>> The way 5129 was done, two (or more) EXP codepoints can be designated
>>> as the same CoS, but one can be used to say "this packet experienced
>>> congestion when using this CoS", while the other says "it didn't".
>>> So, I guess I could live with this field being called CoS, even
>>> though it's not strictly correct. I can't think of anything better.
>> 
>> We had the same discussion when we started to discuss this draft, we
>> wanted to find a name the covered both cases. We just couldn't come
>> with a better name, so we said "Let us call it 'CoS Field'" and change
>> it someone comes up with something better.
>> 
>> I'm still open to do that change, but time is kind of running out, the
>> latest point in time we can do this change is an RFC editor note, when
>> the IESG has approved the document.
> 



From l2vpn-bounces@ietf.org  Tue Jul 22 09:47:28 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF51228C0E3;
	Tue, 22 Jul 2008 09:47:28 -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 6AE823A68CD;
	Tue, 22 Jul 2008 09:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level: 
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=0.450, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 aR3aoSg7zgc1; Tue, 22 Jul 2008 09:33:10 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138])
	by core3.amsl.com (Postfix) with ESMTP id 35A453A68BE;
	Tue, 22 Jul 2008 09:33:10 -0700 (PDT)
Received: from E03MVZ4-UKDY.domain1.systemhost.net ([193.113.30.64]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Jul 2008 17:33:50 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] [mpls] multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
Date: Tue, 22 Jul 2008 17:33:57 +0100
Message-ID: <BAB4DC0CD5148948A86BD047A85CE2A706020C9B@E03MVZ4-UKDY.domain1.systemhost.net>
In-Reply-To: <C4AA6673.892F%benjamin.niven-jenkins@bt.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] [mpls] multiple-working group last call on
	draft-ietf-mpls-cosfield-def-04.txt
Thread-Index: AcjrRIC5+eyB+rhTFUGGUR5GYPN9AAA0+3zg
From: <toby.moncaster@bt.com>
To: <benjamin.niven-jenkins@bt.com>, <johnkenney@alumni.nd.edu>, <loa@pi.nu>
X-OriginalArrivalTime: 22 Jul 2008 16:33:50.0188 (UTC)
	FILETIME=[B8AE9AC0:01C8EC18]
X-Mailman-Approved-At: Tue, 22 Jul 2008 09:47:26 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org, tsvwg@ietf.org, ccamp@ops.ietf.org,
	pwe3@ietf.org, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

I tend to agree with Ben - in effect whatever we end up calling it there
should be a clear explanation of what we think it actually means.

If you are still open to new suggestions how about "traffic information
field" as strictly using it for ECN still isn't traffic management. Or
even "traffic signalling field"

Toby

____________________________________________________________________
Toby Moncaster, <toby.moncaster@bt.com> Networks Research Centre, BT
B54/70 Adastral Park, Ipswich, IP53RE, UK.  +44 1473 648734=20


> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]=20
> On Behalf Of Ben Niven-Jenkins
> Sent: 21 July 2008 16:15
> To: John Kenney; Loa Andersson
> Cc: L2VPN; mpls@ietf.org; tsvwg@ietf.org; ccamp; pwe3; ahtmpls@itu.int
> Subject: Re: [Tsvwg] [mpls] multiple-working group last call=20
> on draft-ietf-mpls-cosfield-def-04.txt
>=20
> I'm not precious about which term we use but if we use=20
> Traffic Management I
> think a paragraph should be added explaining what is meant to=20
> put it in
> context.
>=20
> Ben
>=20
>=20
>=20
> On 21/07/2008 15:07, "John Kenney" <johnkenney@alumni.nd.edu> wrote:
>=20
> > Hi Loa,
> >=20
> > This is a good draft.  It's time to rename the EXP field.  While CoS
> > Field may have been a good choice at one time, we've now=20
> heard from many
> > who think it is too narrow for current usage of this field.
> >=20
> > I suggest "Traffic Management Field".
> >=20
> > Traffic management is a common, generic, and concise term. =20
> It covers
> > all current uses of the field: scheduling class, drop priority, and
> > congestion notification. CoS really only covers the first.  Traffic
> > management is well-scoped to this purpose, and clearly=20
> preferable to CoS
> > in my opinion.
> >=20
> > In terms of the draft, I think a simple global substitution=20
> of "traffic
> > management" for "class of service" and of "TM" for "CoS"=20
> should suffice.
> >=20
> > I think in the long run we'll be glad if we bite the bullet=20
> now and make
> > this change.
> >=20
> > Best Regards,
> > John
> >=20
> >=20
> > Loa Andersson wrote:
> >>=20
> >> Bob,
> >>=20
> >> thanks for useful comments :)
> >>=20
> >> Bob Briscoe wrote:
> >>> Loa,
> >>>=20
> >>> I believe this draft has no technical effect. However=20
> there is some
> >>> truth in the idea that names are important.
> >>>=20
> >>> So, let's set aside a few clock cycles to consider this...
> >>>=20
> >>> 1/ Is CoS a good description of ECN? Given RFC5129 (Using the EXP
> >>> field for ECN in MPLS), is it really appropriate now to=20
> call this a
> >>> CoS field?
> >>>=20
> >>> Thinking out loud...
> >>> - CoS is a signal from an ingress to the interior (a request for a
> >>> certain class of service),
> >>> - whereas ECN is a signal from the interior forwarding=20
> plane to the
> >>> egress (a response from the interior saying whether the class of
> >>> service requested was congested).
> >>>=20
> >>> The way 5129 was done, two (or more) EXP codepoints can=20
> be designated
> >>> as the same CoS, but one can be used to say "this packet=20
> experienced
> >>> congestion when using this CoS", while the other says "it didn't".
> >>> So, I guess I could live with this field being called CoS, even
> >>> though it's not strictly correct. I can't think of=20
> anything better.
> >>=20
> >> We had the same discussion when we started to discuss this=20
> draft, we
> >> wanted to find a name the covered both cases. We just couldn't come
> >> with a better name, so we said "Let us call it 'CoS=20
> Field'" and change
> >> it someone comes up with something better.
> >>=20
> >> I'm still open to do that change, but time is kind of=20
> running out, the
> >> latest point in time we can do this change is an RFC=20
> editor note, when
> >> the IESG has approved the document.
> >=20
>=20
>=20


From l2vpn-bounces@ietf.org  Tue Jul 22 09:47:47 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48FF728C0FD;
	Tue, 22 Jul 2008 09:47:47 -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 220153A6918;
	Tue, 22 Jul 2008 09:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.917
X-Spam-Level: 
X-Spam-Status: No, score=-5.917 tagged_above=-999 required=5 tests=[AWL=0.682, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 iCMhKYUTDUqS; Tue, 22 Jul 2008 09:46:59 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48])
	by core3.amsl.com (Postfix) with ESMTP id E8F613A6909;
	Tue, 22 Jul 2008 09:46:58 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m6MGl8HV027644
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 22 Jul 2008 09:47:09 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m6MGl8lg001709; Tue, 22 Jul 2008 09:47:08 -0700 (PDT)
Received: from xch-swbh-11.sw.nos.boeing.com (xch-swbh-11.sw.nos.boeing.com
	[129.172.192.157])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m6MGl8Ce001680; Tue, 22 Jul 2008 09:47:08 -0700 (PDT)
Received: from XCH-SW-5V2.sw.nos.boeing.com ([129.172.193.50]) by
	xch-swbh-11.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Jul 2008 09:47:08 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] [mpls] multiple-working group last call
	ondraft-ietf-mpls-cosfield-def-04.txt
Date: Tue, 22 Jul 2008 09:47:06 -0700
Message-ID: <51661468CBD1354294533DA79E85955AEFDDE3@XCH-SW-5V2.sw.nos.boeing.com>
In-Reply-To: <BAB4DC0CD5148948A86BD047A85CE2A706020C9B@E03MVZ4-UKDY.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] [mpls] multiple-working group last call
	ondraft-ietf-mpls-cosfield-def-04.txt
Thread-Index: AcjrRIC5+eyB+rhTFUGGUR5GYPN9AAA0+3zgAACBXDA=
References: <C4AA6673.892F%benjamin.niven-jenkins@bt.com>
	<BAB4DC0CD5148948A86BD047A85CE2A706020C9B@E03MVZ4-UKDY.domain1.systemhost.net>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: <toby.moncaster@bt.com>, <benjamin.niven-jenkins@bt.com>,
	<johnkenney@alumni.nd.edu>, <loa@pi.nu>
X-OriginalArrivalTime: 22 Jul 2008 16:47:08.0150 (UTC)
	FILETIME=[944DF160:01C8EC1A]
X-Mailman-Approved-At: Tue, 22 Jul 2008 09:47:45 -0700
Cc: l2vpn@ietf.org, mpls@ietf.org, tsvwg@ietf.org, ccamp@ops.ietf.org,
	pwe3@ietf.org, ahtmpls@itu.int
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

What about 'CoS'?=20

>-----Original Message-----
>From: toby.moncaster@bt.com [mailto:toby.moncaster@bt.com]=20
>Sent: Tuesday, July 22, 2008 9:34 AM
>To: benjamin.niven-jenkins@bt.com; johnkenney@alumni.nd.edu; loa@pi.nu
>Cc: l2vpn@ietf.org; mpls@ietf.org; tsvwg@ietf.org;=20
>ccamp@ops.ietf.org; pwe3@ietf.org; ahtmpls@itu.int
>Subject: Re: [Tsvwg] [mpls] multiple-working group last call=20
>ondraft-ietf-mpls-cosfield-def-04.txt
>
>I tend to agree with Ben - in effect whatever we end up=20
>calling it there should be a clear explanation of what we=20
>think it actually means.
>
>If you are still open to new suggestions how about "traffic=20
>information field" as strictly using it for ECN still isn't=20
>traffic management. Or even "traffic signalling field"
>
>Toby
>
>____________________________________________________________________
>Toby Moncaster, <toby.moncaster@bt.com> Networks Research=20
>Centre, BT B54/70 Adastral Park, Ipswich, IP53RE, UK.  +44 1473 648734=20
>
>
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]=20
>On Behalf=20
>> Of Ben Niven-Jenkins
>> Sent: 21 July 2008 16:15
>> To: John Kenney; Loa Andersson
>> Cc: L2VPN; mpls@ietf.org; tsvwg@ietf.org; ccamp; pwe3;=20
>ahtmpls@itu.int
>> Subject: Re: [Tsvwg] [mpls] multiple-working group last call on=20
>> draft-ietf-mpls-cosfield-def-04.txt
>>=20
>> I'm not precious about which term we use but if we use Traffic=20
>> Management I think a paragraph should be added explaining what is=20
>> meant to put it in context.
>>=20
>> Ben
>>=20
>>=20
>>=20
>> On 21/07/2008 15:07, "John Kenney" <johnkenney@alumni.nd.edu> wrote:
>>=20
>> > Hi Loa,
>> >=20
>> > This is a good draft.  It's time to rename the EXP field. =20
>While CoS=20
>> > Field may have been a good choice at one time, we've now
>> heard from many
>> > who think it is too narrow for current usage of this field.
>> >=20
>> > I suggest "Traffic Management Field".
>> >=20
>> > Traffic management is a common, generic, and concise term. =20
>> It covers
>> > all current uses of the field: scheduling class, drop=20
>priority, and=20
>> > congestion notification. CoS really only covers the first.=20
> Traffic=20
>> > management is well-scoped to this purpose, and clearly
>> preferable to CoS
>> > in my opinion.
>> >=20
>> > In terms of the draft, I think a simple global substitution
>> of "traffic
>> > management" for "class of service" and of "TM" for "CoS"=20
>> should suffice.
>> >=20
>> > I think in the long run we'll be glad if we bite the bullet
>> now and make
>> > this change.
>> >=20
>> > Best Regards,
>> > John
>> >=20
>> >=20
>> > Loa Andersson wrote:
>> >>=20
>> >> Bob,
>> >>=20
>> >> thanks for useful comments :)
>> >>=20
>> >> Bob Briscoe wrote:
>> >>> Loa,
>> >>>=20
>> >>> I believe this draft has no technical effect. However
>> there is some
>> >>> truth in the idea that names are important.
>> >>>=20
>> >>> So, let's set aside a few clock cycles to consider this...
>> >>>=20
>> >>> 1/ Is CoS a good description of ECN? Given RFC5129=20
>(Using the EXP=20
>> >>> field for ECN in MPLS), is it really appropriate now to
>> call this a
>> >>> CoS field?
>> >>>=20
>> >>> Thinking out loud...
>> >>> - CoS is a signal from an ingress to the interior (a=20
>request for a=20
>> >>> certain class of service),
>> >>> - whereas ECN is a signal from the interior forwarding
>> plane to the
>> >>> egress (a response from the interior saying whether the class of=20
>> >>> service requested was congested).
>> >>>=20
>> >>> The way 5129 was done, two (or more) EXP codepoints can
>> be designated
>> >>> as the same CoS, but one can be used to say "this packet
>> experienced
>> >>> congestion when using this CoS", while the other says=20
>"it didn't".
>> >>> So, I guess I could live with this field being called CoS, even=20
>> >>> though it's not strictly correct. I can't think of
>> anything better.
>> >>=20
>> >> We had the same discussion when we started to discuss this
>> draft, we
>> >> wanted to find a name the covered both cases. We just=20
>couldn't come=20
>> >> with a better name, so we said "Let us call it 'CoS
>> Field'" and change
>> >> it someone comes up with something better.
>> >>=20
>> >> I'm still open to do that change, but time is kind of
>> running out, the
>> >> latest point in time we can do this change is an RFC
>> editor note, when
>> >> the IESG has approved the document.
>> >=20
>>=20
>>=20
>


From l2vpn-bounces@ietf.org  Tue Jul 22 10:17:48 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F8F13A6972;
	Tue, 22 Jul 2008 10:17:48 -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 C42013A6820
	for <l2vpn@core3.amsl.com>; Tue, 22 Jul 2008 10:17:46 -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 X7xeYkpbC1a9 for <l2vpn@core3.amsl.com>;
	Tue, 22 Jul 2008 10:17:45 -0700 (PDT)
Received: from imo-m24.mx.aol.com (imo-m24.mx.aol.com [64.12.137.5])
	by core3.amsl.com (Postfix) with ESMTP id C50CF3A6909
	for <l2vpn@ietf.org>; Tue, 22 Jul 2008 10:17:45 -0700 (PDT)
Received: from balavenkata@aim.com
	by imo-m24.mx.aol.com (mail_out_v38_r9.4.) id l.d11.2fd308f7 (37055)
	for <l2vpn@ietf.org>; Tue, 22 Jul 2008 13:18:20 -0400 (EDT)
Received: from smtprly-ma01.mx.aol.com (smtprly-ma01.mx.aol.com
	[64.12.207.140]) by cia-db04.mx.aol.com (v121.5) with ESMTP id
	MAILCIADB041-90bf4886165cdd; Tue, 22 Jul 2008 13:18:20 -0400
Received: from webmail-nh14 (webmail-nh14.sim.aol.com [207.200.84.133]) by
	smtprly-ma01.mx.aol.com (v121_r2.10) with ESMTP id
	MAILSMTPRLYMA013-5c454886165226b; Tue, 22 Jul 2008 13:18:10 -0400
References: <mailman.120.1216148412.4124.l2vpn@ietf.org>
To: l2vpn@ietf.org
Subject: Re: L2vpn Digest, Vol 50, Issue 6
Date: Tue, 22 Jul 2008 13:18:10 -0400
X-AOL-IP: 76.199.70.100
In-Reply-To: <mailman.120.1216148412.4124.l2vpn@ietf.org>
X-MB-Message-Source: WebUI
MIME-Version: 1.0
From: Bala Venkata <balavenkata@aim.com>
X-MB-Message-Type: User
Content-Type: multipart/alternative; 
	boundary="--------MB_8CABA360CDEC9F9_A60_1219_webmail-nh14.sysops.aol.com"
X-Mailer: AIM WebMail 37955-STANDARD
Received: from 76.199.70.100 by webmail-nh14.sysops.aol.com (207.200.84.133)
	with HTTP (WebMailUI); Tue, 22 Jul 2008 13:18:10 -0400
Message-Id: <8CABA360C842FDF-A60-90D@webmail-nh14.sysops.aol.com>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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


----------MB_8CABA360CDEC9F9_A60_1219_webmail-nh14.sysops.aol.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"



Hello,

In response to the following 

> ------------------------------
> Message: 3
> Date: Tue, 15 Jul 2008 09:30:01 -0700 (PDT)
> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mib-02.txt 
> To: i-d-announce@ietf.org
> Cc: l2vpn@ietf.org
> Message-ID: <20080715163001.E6FD23A6AEF@core3.amsl.com>
> Content-Type: text/plain; charset="us-ascii"
> ------------------------------




1. I never saw any responses to the mib file comments made here except for the vplsPwBindIndex one:
http://www.ietf.org/mail-archive/web/l2vpn/current/msg01595.html


2. It looks as though the vplsPwBindIndex variable has been removed. But it is still being referenced by the vplsPwBindEntry &
one or more other tables ?



Thanks !

/bala

----------MB_8CABA360CDEC9F9_A60_1219_webmail-nh14.sysops.aol.com
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="us-ascii"


<div id="AOLMsgPart_0_adf713f3-8a34-4c34-96ed-7303c5562c46" style="margin: 0px; font-family: Tahoma,Verdana,Arial,Sans-Serif; font-size: 12px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"><pre style="font-size: 9pt;"><tt>Hello,<br>
<br>
In response to the following <br>
<br>
&gt; ------------------------------<br>
&gt; Message: 3<br>
&gt; Date: Tue, 15 Jul 2008 09:30:01 -0700 (PDT)<br>
&gt; From: <a href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>
&gt; Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mib-02.txt <br>
&gt; To: <a href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
&gt; Cc: <a href="mailto:l2vpn@ietf.org">l2vpn@ietf.org</a><br>
&gt; Message-ID: &lt;<a href="mailto:20080715163001.E6FD23A6AEF@core3.amsl.com">20080715163001.E6FD23A6AEF@core3.amsl.com</a>&gt;<br>
&gt; Content-Type: text/plain; charset="us-ascii"<br>
&gt; ------------------------------<br>
<br>
</tt></pre>
</div>
<font face="Arial, Helvetica, sans-serif">1. I never saw any responses to the mib file comments made here except for the </font><font face="Arial, Helvetica, sans-serif">vplsPwBindIndex </font><font face="Arial, Helvetica, sans-serif">one:<br>
http://www.ietf.org/mail-archive/web/l2vpn/current/msg01595.html<br>
<br>
<br>
2. It looks as though the vplsPwBindIndex variable has been removed. But it is still being referenced by the </font>vplsPwBindEntry<font face="Arial, Helvetica, sans-serif"> &amp;<br>
one or more other tables ?<br>
<br>
<br>
<br>
Thanks !<br>
<br>
/bala<br>
</font><div id='u8CABA360C842FDF-A60-90D' class='aol_ad_footer'><FONT style="color: black; font: normal 10pt ARIAL, SAN-SERIF;"><HR style="MARGIN-TOP: 10px">The Famous, the Infamous, the Lame - in your browser. <A title="http://toolbar.aol.com/tmz/download.html?NCID=aolcmp00050000000014" href="http://toolbar.aol.com/tmz/download.html?NCID=aolcmp00050000000014" target="_blank">Get the TMZ Toolbar Now</A>!</FONT> </div>

----------MB_8CABA360CDEC9F9_A60_1219_webmail-nh14.sysops.aol.com--


From l2vpn-bounces@ietf.org  Tue Jul 22 23:15:29 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC6FA28C0E8;
	Tue, 22 Jul 2008 23:15:28 -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 2489828C0E8
	for <l2vpn@core3.amsl.com>; Tue, 22 Jul 2008 23:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.168
X-Spam-Level: 
X-Spam-Status: No, score=0.168 tagged_above=-999 required=5 tests=[AWL=2.766, 
	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 68xrwMgHT7ue for <l2vpn@core3.amsl.com>;
	Tue, 22 Jul 2008 23:15:26 -0700 (PDT)
Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com
	[143.209.238.164])
	by core3.amsl.com (Postfix) with ESMTP id 266453A6946
	for <l2vpn@ietf.org>; Tue, 22 Jul 2008 23:15:25 -0700 (PDT)
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com
	[172.22.216.13])
	by audl751.usa.alcatel.com (ALCANET) with ESMTP id m6N6G2bS016286;
	Wed, 23 Jul 2008 01:16:06 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs02.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Wed, 23 Jul 2008 01:16:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8EC8B.94E55EDD"
Subject: RE: L2vpn Digest, Vol 50, Issue 6
Date: Wed, 23 Jul 2008 01:16:01 -0500
Message-ID: <67FBA6A55FF15B46B8B572062529D26A028D29B0@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <8CABA360C842FDF-A60-90D@webmail-nh14.sysops.aol.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: L2vpn Digest, Vol 50, Issue 6
Thread-Index: AcjsHvkQW6J2hkO9Tb21qtmPrmcPMwAa3D/Q
From: "MEDIRATTA Rohit" <Rohit.Mediratta@alcatel-lucent.com>
To: "Bala Venkata" <balavenkata@aim.com>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 23 Jul 2008 06:16:02.0309 (UTC)
	FILETIME=[94EAE350:01C8EC8B]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8EC8B.94E55EDD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Bala,
1.  Many of the concerns in the mentioned  post were discussed in
Philadelphia. You might be able to find more in the meeting minutes and
the slide for the presentation of Vpls-MIB in Philadelphia IETF.
=20
2.  I agree, the index name for the index to vplsPwBindEntry should be
changed to pwIndex instead of vplsPwBindIndex, this will lead to a TC
reference change a well.
=20
thanks,
Rohit

________________________________

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Bala Venkata
Sent: Tuesday, July 22, 2008 10:18 AM
To: l2vpn@ietf.org
Subject: Re: L2vpn Digest, Vol 50, Issue 6


Hello,



In response to the following=20



> ------------------------------

> Message: 3

> Date: Tue, 15 Jul 2008 09:30:01 -0700 (PDT)

> From: Internet-Drafts@ietf.org

> Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mib-02.txt=20

> To: i-d-announce@ietf.org

> Cc: l2vpn@ietf.org

> Message-ID: <20080715163001.E6FD23A6AEF@core3.amsl.com>

> Content-Type: text/plain; charset=3D"us-ascii"

> ------------------------------




1. I never saw any responses to the mib file comments made here except
for the vplsPwBindIndex one:
http://www.ietf.org/mail-archive/web/l2vpn/current/msg01595.html


2. It looks as though the vplsPwBindIndex variable has been removed. But
it is still being referenced by the vplsPwBindEntry &
one or more other tables ?



Thanks !

/bala

________________________________

The Famous, the Infamous, the Lame - in your browser. Get the TMZ
Toolbar Now
<http://toolbar.aol.com/tmz/download.html?NCID=3Daolcmp00050000000014> ! =


------_=_NextPart_001_01C8EC8B.94E55EDD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Bala,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>1.&nbsp; Many of the concerns in the=20
mentioned&nbsp;&nbsp;post were discussed in Philadelphia. You might be =
able to=20
find more in the meeting minutes and the slide for the presentation of =
Vpls-MIB=20
in Philadelphia IETF.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>2.&nbsp;&nbsp;I agree, the index name for the =
index to=20
vplsPwBindEntry should be changed to pwIndex instead of vplsPwBindIndex, =
this=20
will lead to a TC reference change a well.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D919400706-23072008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Rohit</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> l2vpn-bounces@ietf.org=20
[mailto:l2vpn-bounces@ietf.org] <B>On Behalf Of </B>Bala =
Venkata<BR><B>Sent:</B>=20
Tuesday, July 22, 2008 10:18 AM<BR><B>To:</B> =
l2vpn@ietf.org<BR><B>Subject:</B>=20
Re: L2vpn Digest, Vol 50, Issue 6<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=3DAOLMsgPart_0_adf713f3-8a34-4c34-96ed-7303c5562c46=20
style=3D"FONT-SIZE: 12px; MARGIN: 0px; COLOR: rgb(0,0,0); FONT-FAMILY: =
Tahoma,Verdana,Arial,Sans-Serif; BACKGROUND-COLOR: =
rgb(255,255,255)"><PRE style=3D"FONT-SIZE: 9pt"><TT>Hello,<BR>
<BR>
In response to the following <BR>
<BR>
&gt; ------------------------------<BR>
&gt; Message: 3<BR>
&gt; Date: Tue, 15 Jul 2008 09:30:01 -0700 (PDT)<BR>
&gt; From: <A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A><BR>=

&gt; Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mib-02.txt <BR>
&gt; To: <A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A><BR>
&gt; Cc: <A href=3D"mailto:l2vpn@ietf.org">l2vpn@ietf.org</A><BR>
&gt; Message-ID: &lt;<A =
href=3D"mailto:20080715163001.E6FD23A6AEF@core3.amsl.com">20080715163001.=
E6FD23A6AEF@core3.amsl.com</A>&gt;<BR>
&gt; Content-Type: text/plain; charset=3D"us-ascii"<BR>
&gt; ------------------------------<BR>
<BR>
</TT></PRE></DIV><FONT face=3D"Arial, Helvetica, sans-serif">1. I never =
saw any=20
responses to the mib file comments made here except for the </FONT><FONT =

face=3D"Arial, Helvetica, sans-serif">vplsPwBindIndex </FONT><FONT=20
face=3D"Arial, Helvetica, =
sans-serif">one:<BR>http://www.ietf.org/mail-archive/web/l2vpn/current/ms=
g01595.html<BR><BR><BR>2.=20
It looks as though the vplsPwBindIndex variable has been removed. But it =
is=20
still being referenced by the </FONT>vplsPwBindEntry<FONT=20
face=3D"Arial, Helvetica, sans-serif"> &amp;<BR>one or more other tables =

?<BR><BR><BR><BR>Thanks !<BR><BR>/bala<BR></FONT>
<DIV class=3Daol_ad_footer id=3Du8CABA360C842FDF-A60-90D><FONT=20
style=3D"FONT: 10pt ARIAL, SAN-SERIF; COLOR: black">
<HR style=3D"MARGIN-TOP: 10px">
The Famous, the Infamous, the Lame - in your browser. <A=20
title=3Dhttp://toolbar.aol.com/tmz/download.html?NCID=3Daolcmp00050000000=
014=20
href=3D"http://toolbar.aol.com/tmz/download.html?NCID=3Daolcmp00050000000=
014"=20
target=3D_blank>Get the TMZ Toolbar Now</A>!</FONT> </DIV></BODY></HTML>

------_=_NextPart_001_01C8EC8B.94E55EDD--


From l2vpn-bounces@ietf.org  Wed Jul 23 08:00:40 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09D833A68AA;
	Wed, 23 Jul 2008 08:00:40 -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 245553A68A3
	for <l2vpn@core3.amsl.com>; Wed, 23 Jul 2008 08:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.716
X-Spam-Level: 
X-Spam-Status: No, score=-1.716 tagged_above=-999 required=5 tests=[AWL=0.533, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 XYju5ujjhlRk for <l2vpn@core3.amsl.com>;
	Wed, 23 Jul 2008 08:00:37 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id 86DA828C1C0
	for <l2vpn@ietf.org>; Wed, 23 Jul 2008 08:00:31 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m6NF0gKY008043; 
	Wed, 23 Jul 2008 17:00:44 +0200
Received: from itvimn0i34082 ([151.98.70.19]) by
	FRVELSBHS06.ad2.ad.alcatel.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.2499); Wed, 23 Jul 2008 17:00:43 +0200
From: "Italo Busi" <Italo.Busi@alcatel-lucent.it>
To: "'Shane Amante'" <shane@castlepoint.net>, <l2vpn@ietf.org>
References: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
Subject: RE: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
Date: Wed, 23 Jul 2008 17:01:46 +0200
Message-ID: <010a01c8ecd5$071e13e0$13466297@vim.tlt.alcatel.it>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcjhckWVg3XAUhLNSRKytIa7ApfytALYrezg
In-Reply-To: <1AB02CAF-DA50-4F0F-BD3A-EF1400616939@castlepoint.net>
X-OriginalArrivalTime: 23 Jul 2008 15:00:43.0105 (UTC)
	FILETIME=[E0EF2510:01C8ECD4]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

I agree including VPMS within the L2VPN charter

Italo 

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
> On Behalf Of Shane Amante
> Sent: Wednesday, July 09, 2008 5:17 AM
> To: l2vpn@ietf.org
> Subject: Re-charter Take 2: Virtual Private Multicast Service (VPMS)
> 
> Hi all,
> 
> It seems that the PWE3 WG has completed their re-charter activity,  
> which now includes defining P2MP PW's:
> http://www.ietf.org/html.charters/pwe3-charter.html
> 
> As a result, we would like to conduct a short call for interest to  
> include VPMS (likely utilizing P2MP PW's) into the new L2VPN WG  
> charter, before submitting it to the IESG.  Please indicate to the  
> mailing list whether you agree that it should be included in the new  
> L2VPN charter.  (Silence will not count as support).  Also, please  
> speak up if you have comments or clarifications with respect to the  
> proposed wording of VPMS.
> 
> Copied below is a full copy of the proposed charter, including VPMS.
> 
> We will close discussion and gauge consensus on this issue in 
> 2 weeks,  
> on Wednesday, 7/23, at 17:00 MDT, UTC -6.
> 
> Finally, this call *is not* re-opening the entire charter for  
> discussion, rather this is narrowly focused strictly on whether, or  
> not, to add VPMS to the previously agreed upon L2VPN charter.
> 
> -shane & Vach
> 
> 



From l2vpn-bounces@ietf.org  Thu Jul 24 10:50:28 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E8B93A6A29;
	Thu, 24 Jul 2008 10:50:28 -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 5F6A83A6A03
	for <l2vpn@core3.amsl.com>; Thu, 24 Jul 2008 10:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 JuG99jRnhSlW for <l2vpn@core3.amsl.com>;
	Thu, 24 Jul 2008 10:50:26 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 1F9FF3A692B
	for <l2vpn@ietf.org>; Thu, 24 Jul 2008 10:50:26 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 4777E2684EC; Thu, 24 Jul 2008 11:51:11 -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;
	Thu, 24 Jul 2008 11:51:11 -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=60459; data-bytes=0
Message-ID: <4888C10E.7040602@castlepoint.net>
Date: Thu, 24 Jul 2008 11:51:10 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: l2vpn@ietf.org
Subject: VPLS Architecture
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Recently, a significant number of drafts have been submitted, and 
discussed, to address incorporating 802.1ag, 802.1ah and other IEEE/ITU 
protocols within the VPLS Architecture.  These drafts appear to largely 
be: a) a re-specification of how IEEE protocols work over top of a VPLS; 
or, b) how IEEE protocols inter-work with other IEEE data-plane formats 
within a VPLS (or PWE3's).  In addition, for completeness, there is a 
question which L2VPN hasn't addressed: the potential for inter-working 
Native Service Layer control protocols from the IEEE/ITU with those 
created and maintained by L2VPN.

With respect to the first question (re-specification of other SDO's 
protocols), there are a significant number of concerns.  Specifically, 
when protocols from another SDO are re-specified within the IETF, there 
is the potential for errors or omissions to be introduced.  In general, 
there is likely to be insufficient expertise widely available within the 
IETF to review those drafts, in-depth, for accuracy or "faithfulness" to 
the original SDO's standard as they progress through the IETF standards 
process.  Finally, there is always the [unanswered] question of what 
SDO's document is considered authoritative in case a conflict, error or 
omission develops.  In summary, there is both little value and 
significant risk in widespread re-publication of IEEE/ITU specifications 
within the L2VPN WG.  In a well written draft, Normative References to 
another SDO's detailed architecture, protocol or technology documents 
should be more than adequate, and seems to have worked well, so far, 
particularly in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761] 
to cite just two examples.

On the other hand, the second and third questions, both raise 
significant concerns about the current and future architecture of VPLS.

With respect to the second question (interworking of two IEEE data-plane 
protocols within a VPLS), L2VPN (via PWE3 WG) seems to have gone down a 
path of just defining a new PW type for a new IEEE data-plane (i.e.: 
draft-martini-pwe3-802.1ah-pw-02), most likely based on past precedent 
of raw and tagged Ethernet PW types, which were originally specified as 
such to make up for hardware limitations at the time.  Instead, the 
(much) larger question that should be asked is: why can't the VPLS 
architecture *seamlessly* support existing/legacy and new Ethernet 
data-plane formats concurrently?  In other words, what is lacking in the 
current emulation of PW's that needs to be fixed in order to provide 
more seamless carriage of Ethernet frames within a VPLS, so that the 
VPLS architecture can remain agnostic to current and future IEEE 
data-plane protocols?

Related to this last point, a number of people have put together the 
following draft specifying a "Generic Ethernet PW", 
<http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>, 
whose purpose is to re-cast Ethernet PW's back into a generic Ethernet 
transport mechanism, (as was originally desired).  In doing so, 
processing related to the "normalization" of Ethernet frames is then 
shifted back into the ingress or egress PW Native Service Processing 
(NSP) functions.  From an architecture standpoint, the NSP function has 
direct (configured) knowledge of the incoming/outgoing data-plane format 
as well as any associated actions that need to be performed when 
receiving from or transmitting to the AC.  This would allow a (Generic 
Ethernet) PW and, consequently, VPLS to (again) remain agnostic as to 
the Ethernet data-plane, thus allowing seamless support of existing and 
emerging (or, even, future) IEEE data-plane protocols.

Finally, there is the third question (inter-working of Native Service 
Layer (NSL) control protocols with VPLS).  One component of the VPLS 
Architecture, is a "Bridge Module", which is equivalent to a PW NSP[1]. 
  Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2, it is 
noted that "precise functionality that the bridge modules must have in 
particular circumstances is, however, out of scope of the current 
document".  In other words, the VPLS architecture should be oblivious to 
Native Service Layer control protocols entering, exiting or processed 
within the Bridge Module.  The main reason for this is to avoid 
re-specification of other SDO's protocols.  A secondary reason is to 
avoid unnecessary and uncomfortably tight coupling of other SDO's NSL 
control protocols with those specified and maintained within the IETF 
L2VPN (or PWE3) WG's.  Finally, this allows end-users and implementers 
to expect the NSL Layer-2 Control Protocols operating within the Bridge 
Module (or, PW NSP) to remain "faithful" to the original SDO's 
specification of those L2 control protocols.

In summary, we believe that the architecture of VPLS (and PW's) should 
remain agnostic to the underlying data-plane, in order to simplify the 
overall architecture and /operation/ of VPLS.  Therefore, as co-chairs, 
we will be placing overwhelming scrutiny on **all** drafts within the 
L2VPN WG, going forward, in order to avoid re-specification of other 
SDO's standards even as Informational Drafts.  Furthermore, we also will 
be guiding the WG to look at the fundamental architecture of VPLS, and 
its underlying PW's, to *first* determine what are the /requirements/ to 
ensure VPLS remains agnostic to data-plane protocols.  Eventually, that 
should lead to specific enhancements/solutions to IETF protocols (VPLS 
and/or PW's) in order that we have the most straightforward 
implementations of VPLS, which are able to accommodate both present and 
future data-plane protocols, thereby increasing the longevity of VPLS 
implementations and deployments.  Also, just to be clear, this latter 
task will most likely require careful coordination between both the 
L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS 
architecture and own/maintain key elements of VPLS control, signaling 
and encapsulation formats.

Thanks,

-shane & Vach
co-chairs of L2VPN WG

[1] The following is defined within PWE3 Architecture [RFC 3985]:
---snip---
    Native Service Processing (NSP): Processing of the data received by
    the PE from the CE before presentation to the PW for transmission
    across the core, or processing of the data received from a PW by a PE
    before it is output on the AC.  NSP functionality is defined by
    standards bodies other than the IETF, such as ITU-T, ANSI, or ATMF.)
---snip---
In the context of this conversation, it is important to note that "NSP 
functionality is defined by standards bodies other than the IETF".

[2] If we step back and look at history, the SUBIP and, subsequently, 
PWE3 WG's were clear about **not** providing perfect emulation of a 
Native Service over an MPLS PSN.  In fact, if one refers to the PW 
encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and 
Ethernet [RFC 4448] there is a clear "Applicability Statement" in 
Section 3 of all RFC's, where this is pointed out.  In addition, it 
points out in a very concise manner, "notable differences" between the 
traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Thu Jul 24 17:38:11 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0ADA13A6A4D;
	Thu, 24 Jul 2008 17:38:11 -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 7BE7D3A67B2
	for <l2vpn@core3.amsl.com>; Thu, 24 Jul 2008 17:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 lONxY4bA06gx for <l2vpn@core3.amsl.com>;
	Thu, 24 Jul 2008 17:38:08 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id E41463A6A2D
	for <l2vpn@ietf.org>; Thu, 24 Jul 2008 17:38:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,249,1215388800"; d="scan'208";a="38640373"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 25 Jul 2008 00:38:02 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6P0c28V006818; 
	Thu, 24 Jul 2008 17:38:02 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m6P0c2Dj008641;
	Fri, 25 Jul 2008 00:38:02 GMT
Received: from xmb-sjc-239.amer.cisco.com ([128.107.191.105]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 Jul 2008 17:38:01 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Thu, 24 Jul 2008 17:38:02 -0700
Message-ID: <483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <4888C10E.7040602@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjtteRkvCMv3E3oTW2NF1JqH25X3gALwgcw
References: <4888C10E.7040602@castlepoint.net>
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 25 Jul 2008 00:38:01.0834 (UTC)
	FILETIME=[B1A37CA0:01C8EDEE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10444; t=1216946282;
	x=1217810282; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20(sajassi)=22=20<sajassi@cisco.c
	om> |Subject:=20RE=3A=20VPLS=20Architecture |Sender:=20;
	bh=NHEbn9bV5VCmExAxnZnK7rPhB1U5GgJi7KcnrSJZvnQ=;
	b=eCLm1k0ZKgpFPJSY2G6XO9HBUkMpRK9qqMfJe4roHuwbwMXR3AHTT/MyPm
	tF1stt98L1SuRZKGT08QnaZC/Wc+Wo4NNuiTd1C2YaEBicM5HBLaF85Nnjv6
	82XBwAjfcl;
Authentication-Results: sj-dkim-2; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

=20
Shane,

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20
> On Behalf Of Shane Amante
> Sent: Thursday, July 24, 2008 10:51 AM
> To: l2vpn@ietf.org
> Subject: VPLS Architecture
>=20
> Recently, a significant number of drafts have been submitted,=20
> and discussed, to address incorporating 802.1ag, 802.1ah and=20
> other IEEE/ITU protocols within the VPLS Architecture.  These=20
> drafts appear to largely
> be: a) a re-specification of how IEEE protocols work over top=20
> of a VPLS; or, b) how IEEE protocols inter-work with other=20
> IEEE data-plane formats within a VPLS (or PWE3's).  In=20
> addition, for completeness, there is a question which L2VPN=20
> hasn't addressed: the potential for inter-working Native=20
> Service Layer control protocols from the IEEE/ITU with those=20
> created and maintained by L2VPN.
>=20

Can you be more precise on which drafts you are talking about. It is
hard to formulate a response to your comments without knowing what
drafts you mean specifically.=20

> With respect to the first question (re-specification of other=20
> SDO's protocols), there are a significant number of concerns.=20
>  Specifically, when protocols from another SDO are=20
> re-specified within the IETF, there is the potential for=20
> errors or omissions to be introduced.  In general, there is=20
> likely to be insufficient expertise widely available within=20
> the IETF to review those drafts, in-depth, for accuracy or=20
> "faithfulness" to the original SDO's standard as they=20
> progress through the IETF standards process.  Finally, there=20
> is always the [unanswered] question of what SDO's document is=20
> considered authoritative in case a conflict, error or=20
> omission develops.  In summary, there is both little value=20
> and significant risk in widespread re-publication of IEEE/ITU=20
> specifications within the L2VPN WG.  In a well written draft,=20
> Normative References to another SDO's detailed architecture,=20
> protocol or technology documents should be more than=20
> adequate, and seems to have worked well, so far, particularly=20
> in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761]=20
> to cite just two examples.
>=20

I concur. There should be no reason for the re-specification of IEEE
drafts for many reasons some of which you have mentioned above. As the
matter of fact in my pbb-interop draft, I put a short primer on PBB in
the Appendix for just this purpose so that any re-specification be
avoided in the main body of the draft. And I was told by many people
that this one page primer was very helpful to them.



> On the other hand, the second and third questions, both raise=20
> significant concerns about the current and future=20
> architecture of VPLS.
>=20
> With respect to the second question (interworking of two IEEE=20
> data-plane protocols within a VPLS), L2VPN (via PWE3 WG)=20
> seems to have gone down a path of just defining a new PW type=20
> for a new IEEE data-plane (i.e.:=20
> draft-martini-pwe3-802.1ah-pw-02), most likely based on past=20
> precedent of raw and tagged Ethernet PW types, which were=20
> originally specified as such to make up for hardware=20
> limitations at the time.  Instead, the
> (much) larger question that should be asked is: why can't the=20
> VPLS architecture *seamlessly* support existing/legacy and=20
> new Ethernet data-plane formats concurrently?  In other=20
> words, what is lacking in the current emulation of PW's that=20
> needs to be fixed in order to provide more seamless carriage=20
> of Ethernet frames within a VPLS, so that the VPLS=20
> architecture can remain agnostic to current and future IEEE=20
> data-plane protocols?
>=20

"raw" and "tagged" modes were debated many times since the genesis of
PWE3 and the WG decided on using them as specified and we got not RFC in
both PWE3 and L2VPN regarding their applications. Are you suggesting
that we start from square one again ??

Also, I think a point may be getting missed here with respect to L2VPN
services using these PWs. The type of the PW frankly is not as important
as having the two sides agree on exchanging the same packet format and
agree on the interpretation of such format; whether that is done
explicitly or implicitly (via PW type) is a small point. The precedence
for last seven years has been explicit indication via PW type (e.g., raw
mode versus tagged mode).   =20

> Related to this last point, a number of people have put=20
> together the following draft specifying a "Generic Ethernet=20
> PW",=20
> <http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
> whose purpose is to re-cast Ethernet PW's back into a generic=20
> Ethernet transport mechanism, (as was originally desired). =20
> In doing so, processing related to the "normalization" of=20
> Ethernet frames is then shifted back into the ingress or=20
> egress PW Native Service Processing
> (NSP) functions.  From an architecture standpoint, the NSP=20
> function has direct (configured) knowledge of the=20
> incoming/outgoing data-plane format as well as any associated=20
> actions that need to be performed when receiving from or=20
> transmitting to the AC.  This would allow a (Generic
> Ethernet) PW and, consequently, VPLS to (again) remain=20
> agnostic as to the Ethernet data-plane, thus allowing=20
> seamless support of existing and emerging (or, even, future)=20
> IEEE data-plane protocols.
>=20

There are pros/cons for this where we can discuss in the PWE3 or L2VPN
sessions but frankly I don't think of this explicit v.s. implicit PW
type indication as a significant one which deserves such attention and
being made center piece of "VPLS architecture". =20

> Finally, there is the third question (inter-working of Native=20
> Service Layer (NSL) control protocols with VPLS).  One=20
> component of the VPLS Architecture, is a "Bridge Module",=20
> which is equivalent to a PW NSP[1].=20
>   Furthermore, within the L2VPN Framework [RFC 4664], Section=20
> 2.2, it is noted that "precise functionality that the bridge=20
> modules must have in particular circumstances is, however,=20
> out of scope of the current document".  In other words, the=20
> VPLS architecture should be oblivious to Native Service Layer=20
> control protocols entering, exiting or processed within the=20
> Bridge Module.  The main reason for this is to avoid=20
> re-specification of other SDO's protocols.  A secondary=20
> reason is to avoid unnecessary and uncomfortably tight=20
> coupling of other SDO's NSL control protocols with those=20
> specified and maintained within the IETF L2VPN (or PWE3)=20
> WG's.  Finally, this allows end-users and implementers to=20
> expect the NSL Layer-2 Control Protocols operating within the=20
> Bridge Module (or, PW NSP) to remain "faithful" to the=20
> original SDO's specification of those L2 control protocols.
>=20

The nature of service being offered in VPLS (e.g., qualified v.s.
non-qualifed modes) affect the interaction with some of these bridging
protocols which needs to be captured. If there was no affect, I would
have agreed with you but if there is an impact then we need to at least
specify what we expect from this magic box (bridge module). Regarding
how it is done, it can simply be referred to IEEE spec. Remember that
VPLS (as a service) is defined among a set of Attachment Circuits !!
=20

> In summary, we believe that the architecture of VPLS (and=20
> PW's) should remain agnostic to the underlying data-plane, in=20
> order to simplify the overall architecture and /operation/ of=20
> VPLS. Therefore, as co-chairs, we will be placing=20
> overwhelming scrutiny on **all** drafts within the L2VPN WG,=20
> going forward, in order to avoid re-specification of other=20
> SDO's standards even as Informational Drafts.  Furthermore,=20
> we also will be guiding the WG to look at the fundamental=20
> architecture of VPLS, and its underlying PW's, to *first*=20
> determine what are the /requirements/ to ensure VPLS remains=20
> agnostic to data-plane protocols.  Eventually, that should=20
> lead to specific enhancements/solutions to IETF protocols=20
> (VPLS and/or PW's) in order that we have the most=20
> straightforward implementations of VPLS, which are able to=20
> accommodate both present and future data-plane protocols,=20
> thereby increasing the longevity of VPLS implementations and=20
> deployments.  Also, just to be clear, this latter task will=20
> most likely require careful coordination between both the=20
> L2VPN and PWE3 WG's, since PWE3 is an integral part of the=20
> VPLS architecture and own/maintain key elements of VPLS=20
> control, signaling and encapsulation formats.
>=20

I think we first need to decide whether we are going to rehash all the
PW type discussion all over again and change the application of existing
"raw" and "tagged" mode as being defined in both PWE3 and L2VPN RFCs.=20

Cheers,
Ali=20

> Thanks,
>=20
> -shane & Vach
> co-chairs of L2VPN WG
>=20
> [1] The following is defined within PWE3 Architecture [RFC 3985]:
> ---snip---
>     Native Service Processing (NSP): Processing of the data=20
> received by
>     the PE from the CE before presentation to the PW for transmission
>     across the core, or processing of the data received from=20
> a PW by a PE
>     before it is output on the AC.  NSP functionality is defined by
>     standards bodies other than the IETF, such as ITU-T,=20
> ANSI, or ATMF.)
> ---snip---
> In the context of this conversation, it is important to note=20
> that "NSP functionality is defined by standards bodies other=20
> than the IETF".
>=20
> [2] If we step back and look at history, the SUBIP and, subsequently,
> PWE3 WG's were clear about **not** providing perfect=20
> emulation of a Native Service over an MPLS PSN.  In fact, if=20
> one refers to the PW encapsulation RFC's for Frame Relay [RFC=20
> 4619], ATM [RFC 4717] and Ethernet [RFC 4448] there is a=20
> clear "Applicability Statement" in Section 3 of all RFC's,=20
> where this is pointed out.  In addition, it points out in a=20
> very concise manner, "notable differences" between the=20
> traditional Native Service and the new <FOO> over PW service.
>=20


From l2vpn-bounces@ietf.org  Fri Jul 25 02:29:05 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CC3428C130;
	Fri, 25 Jul 2008 02:29:05 -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 1A76E28C128
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 02:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 uIw2n7zwrh1C for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 02:29:02 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id 7ADA328C130
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 02:29:02 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m6P9R7e15106; Fri, 25 Jul 2008 09:27:07 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 05:28:59 -0400
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
In-Reply-To: <4888C10E.7040602@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjtteM20JxCCB2wSMmYeU9/lf8NOQAfyP7A
References: <4888C10E.7040602@castlepoint.net>
From: "David Allan" <dallan@nortel.com>
To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 Shane: I'm trying to understand this in the context of
draft-allan-mmrp... And other proposals....

What I get out of this raises a number of points of interest....

1) No interaction with L2 protocols in theory takes all possibility of
resilient access off the table except as a pure overlay over totally
static and unfiltered VPLS instance(s). Some interaction is required to
ensure VPLS is not creating a loop if it has more than one point of
attachment to a broadcast domain. However if that interaction is off the
table then (for example) preferred forwarding which implies interaction
with peer networks protocols such as LACP, is a piece of work that
should be abandoned by this criteria...

MAC withdraw is effectively interaction with IEEE control protocols of
some form similar to 1. Topology change BPDUs transparently passed over
PWs between bridge modules would appear to be the only acceptable
approach by this criteria...

Which actually would work just fine as far as draft allan is
concerned... But for the case where ALL bridge modules do not have STP
enabled, preferred forwarding needs to stunt double...=20

2) In the case of MMRP if the PW is presented as an interface to a
bridge module...I do not think there is a conflict. It is filtering
programmed prior to PW ingress by IEEE registration protocols for the
purpose of multicast pruning in a single broadcast domain. Registration
of filtering needs to be tied to topology change being what I think is
both your interest and concern....

But if I were to back this up to where efforts appear to be going....

1) preferred forwarding as a means of semaphoring a topology change
across a VPLS instance appears to be well advanced. That it can be used
as an aggregated MAC withdraw for PBBNs seems consistent with where PWE
is already going. That it can stunt double for a topology change BPDU I
do not think is a stretch as that is exactly what it is
communicating....

2) Multicast MAC filtering at the ingress to a broadcast domain does not
involve modifications to IEEE registration protocols in my proposal, or
is statically provisioned (as in Ali's proposal),and at least that part
is exclusive to the bridge module so does not seem to undermine your
concerns.

Does my analysis align with yours?
Thanks
Dave



=20

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Shane Amante
Sent: Thursday, July 24, 2008 1:51 PM
To: l2vpn@ietf.org
Subject: VPLS Architecture

Recently, a significant number of drafts have been submitted, and
discussed, to address incorporating 802.1ag, 802.1ah and other IEEE/ITU
protocols within the VPLS Architecture.  These drafts appear to largely
be: a) a re-specification of how IEEE protocols work over top of a VPLS;
or, b) how IEEE protocols inter-work with other IEEE data-plane formats
within a VPLS (or PWE3's).  In addition, for completeness, there is a
question which L2VPN hasn't addressed: the potential for inter-working
Native Service Layer control protocols from the IEEE/ITU with those
created and maintained by L2VPN.

With respect to the first question (re-specification of other SDO's
protocols), there are a significant number of concerns.  Specifically,
when protocols from another SDO are re-specified within the IETF, there
is the potential for errors or omissions to be introduced.  In general,
there is likely to be insufficient expertise widely available within the
IETF to review those drafts, in-depth, for accuracy or "faithfulness" to
the original SDO's standard as they progress through the IETF standards
process.  Finally, there is always the [unanswered] question of what
SDO's document is considered authoritative in case a conflict, error or
omission develops.  In summary, there is both little value and
significant risk in widespread re-publication of IEEE/ITU specifications
within the L2VPN WG.  In a well written draft, Normative References to
another SDO's detailed architecture, protocol or technology documents
should be more than adequate, and seems to have worked well, so far,
particularly in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761]
to cite just two examples.

On the other hand, the second and third questions, both raise
significant concerns about the current and future architecture of VPLS.

With respect to the second question (interworking of two IEEE data-plane
protocols within a VPLS), L2VPN (via PWE3 WG) seems to have gone down a
path of just defining a new PW type for a new IEEE data-plane (i.e.:=20
draft-martini-pwe3-802.1ah-pw-02), most likely based on past precedent
of raw and tagged Ethernet PW types, which were originally specified as
such to make up for hardware limitations at the time.  Instead, the
(much) larger question that should be asked is: why can't the VPLS
architecture *seamlessly* support existing/legacy and new Ethernet
data-plane formats concurrently?  In other words, what is lacking in the
current emulation of PW's that needs to be fixed in order to provide
more seamless carriage of Ethernet frames within a VPLS, so that the
VPLS architecture can remain agnostic to current and future IEEE
data-plane protocols?

Related to this last point, a number of people have put together the
following draft specifying a "Generic Ethernet PW",
<http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
whose purpose is to re-cast Ethernet PW's back into a generic Ethernet
transport mechanism, (as was originally desired).  In doing so,
processing related to the "normalization" of Ethernet frames is then
shifted back into the ingress or egress PW Native Service Processing
(NSP) functions.  From an architecture standpoint, the NSP function has
direct (configured) knowledge of the incoming/outgoing data-plane format
as well as any associated actions that need to be performed when
receiving from or transmitting to the AC.  This would allow a (Generic
Ethernet) PW and, consequently, VPLS to (again) remain agnostic as to
the Ethernet data-plane, thus allowing seamless support of existing and
emerging (or, even, future) IEEE data-plane protocols.

Finally, there is the third question (inter-working of Native Service
Layer (NSL) control protocols with VPLS).  One component of the VPLS
Architecture, is a "Bridge Module", which is equivalent to a PW NSP[1].=20
  Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2, it is
noted that "precise functionality that the bridge modules must have in
particular circumstances is, however, out of scope of the current
document".  In other words, the VPLS architecture should be oblivious to
Native Service Layer control protocols entering, exiting or processed
within the Bridge Module.  The main reason for this is to avoid
re-specification of other SDO's protocols.  A secondary reason is to
avoid unnecessary and uncomfortably tight coupling of other SDO's NSL
control protocols with those specified and maintained within the IETF
L2VPN (or PWE3) WG's.  Finally, this allows end-users and implementers
to expect the NSL Layer-2 Control Protocols operating within the Bridge
Module (or, PW NSP) to remain "faithful" to the original SDO's
specification of those L2 control protocols.

In summary, we believe that the architecture of VPLS (and PW's) should
remain agnostic to the underlying data-plane, in order to simplify the
overall architecture and /operation/ of VPLS.  Therefore, as co-chairs,
we will be placing overwhelming scrutiny on **all** drafts within the
L2VPN WG, going forward, in order to avoid re-specification of other
SDO's standards even as Informational Drafts.  Furthermore, we also will
be guiding the WG to look at the fundamental architecture of VPLS, and
its underlying PW's, to *first* determine what are the /requirements/ to
ensure VPLS remains agnostic to data-plane protocols.  Eventually, that
should lead to specific enhancements/solutions to IETF protocols (VPLS
and/or PW's) in order that we have the most straightforward
implementations of VPLS, which are able to accommodate both present and
future data-plane protocols, thereby increasing the longevity of VPLS
implementations and deployments.  Also, just to be clear, this latter
task will most likely require careful coordination between both the
L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS
architecture and own/maintain key elements of VPLS control, signaling
and encapsulation formats.

Thanks,

-shane & Vach
co-chairs of L2VPN WG

[1] The following is defined within PWE3 Architecture [RFC 3985]:
---snip---
    Native Service Processing (NSP): Processing of the data received by
    the PE from the CE before presentation to the PW for transmission
    across the core, or processing of the data received from a PW by a
PE
    before it is output on the AC.  NSP functionality is defined by
    standards bodies other than the IETF, such as ITU-T, ANSI, or ATMF.)
---snip---
In the context of this conversation, it is important to note that "NSP
functionality is defined by standards bodies other than the IETF".

[2] If we step back and look at history, the SUBIP and, subsequently,
PWE3 WG's were clear about **not** providing perfect emulation of a
Native Service over an MPLS PSN.  In fact, if one refers to the PW
encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and
Ethernet [RFC 4448] there is a clear "Applicability Statement" in
Section 3 of all RFC's, where this is pointed out.  In addition, it
points out in a very concise manner, "notable differences" between the
traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Fri Jul 25 07:17:47 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1FFE3A6ADC;
	Fri, 25 Jul 2008 07:17:47 -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 6990A3A6AE8
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 07:17:46 -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 LPGB3IsHReJs for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 07:17:44 -0700 (PDT)
Received: from audl952.usa.alcatel.com (audl952.usa.alcatel.com
	[143.209.238.159])
	by core3.amsl.com (Postfix) with ESMTP id 8434C3A6ADC
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 07:15:23 -0700 (PDT)
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com
	[172.22.216.13])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id m6PEFE9F005272;
	Fri, 25 Jul 2008 09:15:15 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs02.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 25 Jul 2008 09:15:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 09:15:04 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B047916E3@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjtteM20JxCCB2wSMmYeU9/lf8NOQAfyP7AAAm+73A=
References: <4888C10E.7040602@castlepoint.net>
	<87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "David Allan" <dallan@nortel.com>, "Shane Amante" <shane@castlepoint.net>, 
	<l2vpn@ietf.org>
X-OriginalArrivalTime: 25 Jul 2008 14:15:13.0980 (UTC)
	FILETIME=[DB1337C0:01C8EE60]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Cc: Tony Jeffree <tony@JEFFREE.CO.UK>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 Dave,

This is not about VPLS not being aware about IEEE protocols you list
below. It's about the fact that with proper, IEEE compliant
implementations, the VPLS NSP (native service processing) module will
handle the interactions in an interoperable fashion. That was the whole
idea, otherwise we will keep reproducing all the IEEE work in IETF L2VPN
WG.=20

So I agree with Shane's email: i.e. for IEEE specifically, if a solution
requires development or new interaction for an IEEE protocol then it
should be brought up in the related IEEE session first. Especially if it
applies to both IEEE native domains (e.g. native QinQ or PBB) and VPLS.

For the case in hand (your draft and IEEE 802.1ah, 802.1ak MMRP specs)
if a VPLS designer reads the IEEE specifications it will be able to
implement them no problem. And the resulting (proper) implementations
will just interoperate. Why do we need to spend any cycles in L2VPN WG
on this?

If something is broken in the IEEE protocol then the interested parties
should just go to IEEE and discuss fixes, extensions to the protocol in
the related IEEE sessions, where all the protocol knowledge is
concentrated.=20

This is actually what happened 18 months ago with IEEE 802.1ak - there
were problems with the protocol base, a corrigendum was opened and
solutions were discussed in there that can be applied, no problem, to
both native Ethernet domains and VPLS. Tony, one of the IEEE 802.1ak
editor (in CC), drove the changes smoothly through the process.

There were no cycles spent on this in L2VPN WG. I think we should keep
it this way to maintain proper protocol development.

Florin

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
> Of David Allan
> Sent: Friday, July 25, 2008 2:29 AM
> To: Shane Amante; l2vpn@ietf.org
> Subject: RE: VPLS Architecture
>=20
> HI Shane: I'm trying to understand this in the context of
> draft-allan-mmrp... And other proposals....
>=20
> What I get out of this raises a number of points of interest....
>=20
> 1) No interaction with L2 protocols in theory takes all possibility of
> resilient access off the table except as a pure overlay over totally
> static and unfiltered VPLS instance(s). Some interaction is required
to
> ensure VPLS is not creating a loop if it has more than one point of
> attachment to a broadcast domain. However if that interaction is off
> the
> table then (for example) preferred forwarding which implies
interaction
> with peer networks protocols such as LACP, is a piece of work that
> should be abandoned by this criteria...
>=20
> MAC withdraw is effectively interaction with IEEE control protocols of
> some form similar to 1. Topology change BPDUs transparently passed
over
> PWs between bridge modules would appear to be the only acceptable
> approach by this criteria...
>=20
> Which actually would work just fine as far as draft allan is
> concerned... But for the case where ALL bridge modules do not have STP
> enabled, preferred forwarding needs to stunt double...
>=20
> 2) In the case of MMRP if the PW is presented as an interface to a
> bridge module...I do not think there is a conflict. It is filtering
> programmed prior to PW ingress by IEEE registration protocols for the
> purpose of multicast pruning in a single broadcast domain.
Registration
> of filtering needs to be tied to topology change being what I think is
> both your interest and concern....
>=20
> But if I were to back this up to where efforts appear to be going....
>=20
> 1) preferred forwarding as a means of semaphoring a topology change
> across a VPLS instance appears to be well advanced. That it can be
used
> as an aggregated MAC withdraw for PBBNs seems consistent with where
PWE
> is already going. That it can stunt double for a topology change BPDU
I
> do not think is a stretch as that is exactly what it is
> communicating....
>=20
> 2) Multicast MAC filtering at the ingress to a broadcast domain does
> not
> involve modifications to IEEE registration protocols in my proposal,
or
> is statically provisioned (as in Ali's proposal),and at least that
part
> is exclusive to the bridge module so does not seem to undermine your
> concerns.
>=20
> Does my analysis align with yours?
> Thanks
> Dave
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
> Of Shane Amante
> Sent: Thursday, July 24, 2008 1:51 PM
> To: l2vpn@ietf.org
> Subject: VPLS Architecture
>=20
> Recently, a significant number of drafts have been submitted, and
> discussed, to address incorporating 802.1ag, 802.1ah and other
IEEE/ITU
> protocols within the VPLS Architecture.  These drafts appear to
largely
> be: a) a re-specification of how IEEE protocols work over top of a
> VPLS;
> or, b) how IEEE protocols inter-work with other IEEE data-plane
formats
> within a VPLS (or PWE3's).  In addition, for completeness, there is a
> question which L2VPN hasn't addressed: the potential for inter-working
> Native Service Layer control protocols from the IEEE/ITU with those
> created and maintained by L2VPN.
>=20
> With respect to the first question (re-specification of other SDO's
> protocols), there are a significant number of concerns.  Specifically,
> when protocols from another SDO are re-specified within the IETF,
there
> is the potential for errors or omissions to be introduced.  In
general,
> there is likely to be insufficient expertise widely available within
> the
> IETF to review those drafts, in-depth, for accuracy or "faithfulness"
> to
> the original SDO's standard as they progress through the IETF
standards
> process.  Finally, there is always the [unanswered] question of what
> SDO's document is considered authoritative in case a conflict, error
or
> omission develops.  In summary, there is both little value and
> significant risk in widespread re-publication of IEEE/ITU
> specifications
> within the L2VPN WG.  In a well written draft, Normative References to
> another SDO's detailed architecture, protocol or technology documents
> should be more than adequate, and seems to have worked well, so far,
> particularly in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC
> 4761]
> to cite just two examples.
>=20
> On the other hand, the second and third questions, both raise
> significant concerns about the current and future architecture of
VPLS.
>=20
> With respect to the second question (interworking of two IEEE data-
> plane
> protocols within a VPLS), L2VPN (via PWE3 WG) seems to have gone down
a
> path of just defining a new PW type for a new IEEE data-plane (i.e.:
> draft-martini-pwe3-802.1ah-pw-02), most likely based on past precedent
> of raw and tagged Ethernet PW types, which were originally specified
as
> such to make up for hardware limitations at the time.  Instead, the
> (much) larger question that should be asked is: why can't the VPLS
> architecture *seamlessly* support existing/legacy and new Ethernet
> data-plane formats concurrently?  In other words, what is lacking in
> the
> current emulation of PW's that needs to be fixed in order to provide
> more seamless carriage of Ethernet frames within a VPLS, so that the
> VPLS architecture can remain agnostic to current and future IEEE
> data-plane protocols?
>=20
> Related to this last point, a number of people have put together the
> following draft specifying a "Generic Ethernet PW",
> <http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
> whose purpose is to re-cast Ethernet PW's back into a generic Ethernet
> transport mechanism, (as was originally desired).  In doing so,
> processing related to the "normalization" of Ethernet frames is then
> shifted back into the ingress or egress PW Native Service Processing
> (NSP) functions.  From an architecture standpoint, the NSP function
has
> direct (configured) knowledge of the incoming/outgoing data-plane
> format
> as well as any associated actions that need to be performed when
> receiving from or transmitting to the AC.  This would allow a (Generic
> Ethernet) PW and, consequently, VPLS to (again) remain agnostic as to
> the Ethernet data-plane, thus allowing seamless support of existing
and
> emerging (or, even, future) IEEE data-plane protocols.
>=20
> Finally, there is the third question (inter-working of Native Service
> Layer (NSL) control protocols with VPLS).  One component of the VPLS
> Architecture, is a "Bridge Module", which is equivalent to a PW
NSP[1].
>   Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2, it
> is
> noted that "precise functionality that the bridge modules must have in
> particular circumstances is, however, out of scope of the current
> document".  In other words, the VPLS architecture should be oblivious
> to
> Native Service Layer control protocols entering, exiting or processed
> within the Bridge Module.  The main reason for this is to avoid
> re-specification of other SDO's protocols.  A secondary reason is to
> avoid unnecessary and uncomfortably tight coupling of other SDO's NSL
> control protocols with those specified and maintained within the IETF
> L2VPN (or PWE3) WG's.  Finally, this allows end-users and implementers
> to expect the NSL Layer-2 Control Protocols operating within the
Bridge
> Module (or, PW NSP) to remain "faithful" to the original SDO's
> specification of those L2 control protocols.
>=20
> In summary, we believe that the architecture of VPLS (and PW's) should
> remain agnostic to the underlying data-plane, in order to simplify the
> overall architecture and /operation/ of VPLS.  Therefore, as
co-chairs,
> we will be placing overwhelming scrutiny on **all** drafts within the
> L2VPN WG, going forward, in order to avoid re-specification of other
> SDO's standards even as Informational Drafts.  Furthermore, we also
> will
> be guiding the WG to look at the fundamental architecture of VPLS, and
> its underlying PW's, to *first* determine what are the /requirements/
> to
> ensure VPLS remains agnostic to data-plane protocols.  Eventually,
that
> should lead to specific enhancements/solutions to IETF protocols (VPLS
> and/or PW's) in order that we have the most straightforward
> implementations of VPLS, which are able to accommodate both present
and
> future data-plane protocols, thereby increasing the longevity of VPLS
> implementations and deployments.  Also, just to be clear, this latter
> task will most likely require careful coordination between both the
> L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS
> architecture and own/maintain key elements of VPLS control, signaling
> and encapsulation formats.
>=20
> Thanks,
>=20
> -shane & Vach
> co-chairs of L2VPN WG
>=20
> [1] The following is defined within PWE3 Architecture [RFC 3985]:
> ---snip---
>     Native Service Processing (NSP): Processing of the data received
by
>     the PE from the CE before presentation to the PW for transmission
>     across the core, or processing of the data received from a PW by a
> PE
>     before it is output on the AC.  NSP functionality is defined by
>     standards bodies other than the IETF, such as ITU-T, ANSI, or
> ATMF.)
> ---snip---
> In the context of this conversation, it is important to note that "NSP
> functionality is defined by standards bodies other than the IETF".
>=20
> [2] If we step back and look at history, the SUBIP and, subsequently,
> PWE3 WG's were clear about **not** providing perfect emulation of a
> Native Service over an MPLS PSN.  In fact, if one refers to the PW
> encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and
> Ethernet [RFC 4448] there is a clear "Applicability Statement" in
> Section 3 of all RFC's, where this is pointed out.  In addition, it
> points out in a very concise manner, "notable differences" between the
> traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Fri Jul 25 08:34:11 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2405128C1F7;
	Fri, 25 Jul 2008 08:34:11 -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 9B30628C1F2
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 08:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9hyUBRuONRII for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 08:34:08 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id F155F28C1ED
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 08:34:07 -0700 (PDT)
Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com
	[47.129.230.97])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m6PFWDe15263; Fri, 25 Jul 2008 15:32:13 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 11:32:54 -0400
Message-ID: <183DD1B052A11A40B76125E42F1CBAAB13272195@zcarhxm1.corp.nortel.com>
In-Reply-To: <4888C10E.7040602@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: Acjttd/drM08Xbw0TTKCS23UE0nkOgAs0DNg
References: <4888C10E.7040602@castlepoint.net>
From: "Dinesh Mohan" <mohand@nortel.com>
To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Shane,

I must admit I am still trying to grasp the context of your note, since
as a WG we had recently spent quite a bit of time in updating the
charter for L2PVN and most drafts that you refer to, if not all, were
already in consideration for the WG.

In the meantime I would like to make few observations:

- It seems to me that the basic VPLS functionality becomes questionable
here since as you state below <<One component of the VPLS Architecture,
is a "Bridge Module", which is equivalent to a PW NSP[1]>> and if NSP is
not the focus, then we should simply be working on defining PWs and
should be done. IEEE already a well defined definition of a bridge, and
we should not need VPLS. But I am sure I have misunderstood.

- There is no disagreement that we should not re-specify other SDO
protocols and technologies. However, when we do take the liberty of
using these protocols and technologies, should we not be obligated to
ensure that we get approval from these bodies to ensure that our
interpretation of these protocols and technologies is consistent with
the other SDOs. I bring this up since you have mentioned below <<In
general, there is likely to be insufficient expertise widely available
within the IETF to review those drafts, in-depth, for accuracy or
"faithfulness" to the original SDO's standard as they progress through
the IETF standards process.>> As far as I know neither VPLS-LDP [RFC
4762] and VPLS-BGP [RFC 4761] have gone through such review yet we, as
L2VPN WG cite these as shining examples. So what are the issues that we
are confronted with now suddenly?

- We can certainly try to step aside some of the discussions by citing
<<**not** providing perfect emulation of a Native Service over an MPLS
PSN>> but I am not sure if this is sufficient.
draft-ietf-l2vpn-vpls-bridge-interop highlights the issues confronted
with current day VPLS solutions and no wonder WG has been trying to
address some of these already and with the charter updating highlighting
others that need to be and which already have active work underway in
WG. If this is not an issue, why bother with these follow-ups since VPLS
is already done via VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761].

Therefore, I am still confused with this sudden message.

---
Dinesh

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Shane Amante
Sent: Thursday, July 24, 2008 1:51 PM
To: l2vpn@ietf.org
Subject: VPLS Architecture

Recently, a significant number of drafts have been submitted, and
discussed, to address incorporating 802.1ag, 802.1ah and other IEEE/ITU
protocols within the VPLS Architecture.  These drafts appear to largely
be: a) a re-specification of how IEEE protocols work over top of a VPLS;
or, b) how IEEE protocols inter-work with other IEEE data-plane formats
within a VPLS (or PWE3's).  In addition, for completeness, there is a
question which L2VPN hasn't addressed: the potential for inter-working
Native Service Layer control protocols from the IEEE/ITU with those
created and maintained by L2VPN.

With respect to the first question (re-specification of other SDO's
protocols), there are a significant number of concerns.  Specifically,
when protocols from another SDO are re-specified within the IETF, there
is the potential for errors or omissions to be introduced.  In general,
there is likely to be insufficient expertise widely available within the
IETF to review those drafts, in-depth, for accuracy or "faithfulness" to
the original SDO's standard as they progress through the IETF standards
process.  Finally, there is always the [unanswered] question of what
SDO's document is considered authoritative in case a conflict, error or
omission develops.  In summary, there is both little value and
significant risk in widespread re-publication of IEEE/ITU specifications
within the L2VPN WG.  In a well written draft, Normative References to
another SDO's detailed architecture, protocol or technology documents
should be more than adequate, and seems to have worked well, so far,
particularly in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761]
to cite just two examples.

On the other hand, the second and third questions, both raise
significant concerns about the current and future architecture of VPLS.

With respect to the second question (interworking of two IEEE data-plane
protocols within a VPLS), L2VPN (via PWE3 WG) seems to have gone down a
path of just defining a new PW type for a new IEEE data-plane (i.e.:=20
draft-martini-pwe3-802.1ah-pw-02), most likely based on past precedent
of raw and tagged Ethernet PW types, which were originally specified as
such to make up for hardware limitations at the time.  Instead, the
(much) larger question that should be asked is: why can't the VPLS
architecture *seamlessly* support existing/legacy and new Ethernet
data-plane formats concurrently?  In other words, what is lacking in the
current emulation of PW's that needs to be fixed in order to provide
more seamless carriage of Ethernet frames within a VPLS, so that the
VPLS architecture can remain agnostic to current and future IEEE
data-plane protocols?

Related to this last point, a number of people have put together the
following draft specifying a "Generic Ethernet PW",
<http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
whose purpose is to re-cast Ethernet PW's back into a generic Ethernet
transport mechanism, (as was originally desired).  In doing so,
processing related to the "normalization" of Ethernet frames is then
shifted back into the ingress or egress PW Native Service Processing
(NSP) functions.  From an architecture standpoint, the NSP function has
direct (configured) knowledge of the incoming/outgoing data-plane format
as well as any associated actions that need to be performed when
receiving from or transmitting to the AC.  This would allow a (Generic
Ethernet) PW and, consequently, VPLS to (again) remain agnostic as to
the Ethernet data-plane, thus allowing seamless support of existing and
emerging (or, even, future) IEEE data-plane protocols.

Finally, there is the third question (inter-working of Native Service
Layer (NSL) control protocols with VPLS).  One component of the VPLS
Architecture, is a "Bridge Module", which is equivalent to a PW NSP[1].=20
  Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2, it is
noted that "precise functionality that the bridge modules must have in
particular circumstances is, however, out of scope of the current
document".  In other words, the VPLS architecture should be oblivious to
Native Service Layer control protocols entering, exiting or processed
within the Bridge Module.  The main reason for this is to avoid
re-specification of other SDO's protocols.  A secondary reason is to
avoid unnecessary and uncomfortably tight coupling of other SDO's NSL
control protocols with those specified and maintained within the IETF
L2VPN (or PWE3) WG's.  Finally, this allows end-users and implementers
to expect the NSL Layer-2 Control Protocols operating within the Bridge
Module (or, PW NSP) to remain "faithful" to the original SDO's
specification of those L2 control protocols.

In summary, we believe that the architecture of VPLS (and PW's) should
remain agnostic to the underlying data-plane, in order to simplify the
overall architecture and /operation/ of VPLS.  Therefore, as co-chairs,
we will be placing overwhelming scrutiny on **all** drafts within the
L2VPN WG, going forward, in order to avoid re-specification of other
SDO's standards even as Informational Drafts.  Furthermore, we also will
be guiding the WG to look at the fundamental architecture of VPLS, and
its underlying PW's, to *first* determine what are the /requirements/ to
ensure VPLS remains agnostic to data-plane protocols.  Eventually, that
should lead to specific enhancements/solutions to IETF protocols (VPLS
and/or PW's) in order that we have the most straightforward
implementations of VPLS, which are able to accommodate both present and
future data-plane protocols, thereby increasing the longevity of VPLS
implementations and deployments.  Also, just to be clear, this latter
task will most likely require careful coordination between both the
L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS
architecture and own/maintain key elements of VPLS control, signaling
and encapsulation formats.

Thanks,

-shane & Vach
co-chairs of L2VPN WG

[1] The following is defined within PWE3 Architecture [RFC 3985]:
---snip---
    Native Service Processing (NSP): Processing of the data received by
    the PE from the CE before presentation to the PW for transmission
    across the core, or processing of the data received from a PW by a
PE
    before it is output on the AC.  NSP functionality is defined by
    standards bodies other than the IETF, such as ITU-T, ANSI, or ATMF.)
---snip---
In the context of this conversation, it is important to note that "NSP
functionality is defined by standards bodies other than the IETF".

[2] If we step back and look at history, the SUBIP and, subsequently,
PWE3 WG's were clear about **not** providing perfect emulation of a
Native Service over an MPLS PSN.  In fact, if one refers to the PW
encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and
Ethernet [RFC 4448] there is a clear "Applicability Statement" in
Section 3 of all RFC's, where this is pointed out.  In addition, it
points out in a very concise manner, "notable differences" between the
traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Fri Jul 25 08:41:04 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 091F53A6AF6;
	Fri, 25 Jul 2008 08:41:04 -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 DF2A03A6AF6
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 08:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xovnyR1XPLHr for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 08:41:01 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 068E33A67D0
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 08:41:00 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m6PFewA25774; Fri, 25 Jul 2008 15:40:58 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 11:40:54 -0400
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE16831872@zcarhxm2.corp.nortel.com>
In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B047916E3@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjtteM20JxCCB2wSMmYeU9/lf8NOQAfyP7AAAm+73AAA53IQA==
References: <4888C10E.7040602@castlepoint.net>
	<87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
	<4A5028372622294A99B8FFF6BD06EB7B047916E3@USDALSMBS03.ad3.ad.alcatel.com>
From: "David Allan" <dallan@nortel.com>
To: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>,
	"Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
Cc: Tony Jeffree <tony@JEFFREE.CO.UK>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 Florin=20

> This is not about VPLS not being aware about IEEE protocols you list
below. It's about the fact that with proper, IEEE=20
> compliant implementations, the VPLS NSP (native service processing)
module will handle the interactions in an=20
> interoperable fashion. That was the whole idea, otherwise we will keep
reproducing all the IEEE work in IETF L2VPN WG.

That of course makes perfect sense, I was seeking to clarify that. But I
actually need that confirmation from the chairs...=20

> So I agree with Shane's email: i.e. for IEEE specifically, if a
solution requires development or new interaction for an > IEEE protocol
then it should be brought up in the related IEEE session first.
Especially if it applies to both IEEE=20
> native domains (e.g. native QinQ or PBB) and VPLS.

I do not think that is what is being proposed....

> For the case in hand (your draft and IEEE 802.1ah, 802.1ak MMRP specs)
if a VPLS designer reads the IEEE specifications > it will be able to
implement them no problem. And the resulting (proper) implementations
will just interoperate. Why do > we need to spend any cycles in L2VPN WG
on this?

So you are suggesting we are already done and do not need to consider
this or any other drafts on 802.1ah???? You surprise me!

There is one point to be validated,  the distinction that a PE is at a
boundary between an active topology an a split horizon mesh, VPLS may
provide an input into the state machine for the mesh facing MMRP
implementation. That is a missing component to produce a very viable
model, and IMO would be worth spending a small number of cycles upon.

If the group finds it of interest, a liaison to Tony and co. to test
that this does not break anything would be useful if the group does not
consider it immediately obvious. I believe it doesn't break anything.=20

> If something is broken in the IEEE protocol then the interested
parties should just go to IEEE and discuss fixes,=20
> extensions to the protocol in the related IEEE sessions, where all the
protocol knowledge is concentrated.=20

> This is actually what happened 18 months ago with IEEE 802.1ak - there
were problems with the protocol base, a=20
> corrigendum was opened and solutions were discussed in there that can
be applied, no problem, to both native Ethernet=20
> domains and VPLS. Tony, one of the IEEE 802.1ak editor (in CC), drove
the changes smoothly through the process.

> There were no cycles spent on this in L2VPN WG. I think we should keep
it this way to maintain proper protocol=20
> development.

As the draft proposes a model of how MMRP is used and does not suggest
anything is broken with it, your points escape me..

Cheers
Dave



> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf

> Of David Allan
> Sent: Friday, July 25, 2008 2:29 AM
> To: Shane Amante; l2vpn@ietf.org
> Subject: RE: VPLS Architecture
>=20
> HI Shane: I'm trying to understand this in the context of=20
> draft-allan-mmrp... And other proposals....
>=20
> What I get out of this raises a number of points of interest....
>=20
> 1) No interaction with L2 protocols in theory takes all possibility of

> resilient access off the table except as a pure overlay over totally=20
> static and unfiltered VPLS instance(s). Some interaction is required
to
> ensure VPLS is not creating a loop if it has more than one point of=20
> attachment to a broadcast domain. However if that interaction is off=20
> the table then (for example) preferred forwarding which implies
interaction
> with peer networks protocols such as LACP, is a piece of work that=20
> should be abandoned by this criteria...
>=20
> MAC withdraw is effectively interaction with IEEE control protocols of

> some form similar to 1. Topology change BPDUs transparently passed
over
> PWs between bridge modules would appear to be the only acceptable=20
> approach by this criteria...
>=20
> Which actually would work just fine as far as draft allan is=20
> concerned... But for the case where ALL bridge modules do not have STP

> enabled, preferred forwarding needs to stunt double...
>=20
> 2) In the case of MMRP if the PW is presented as an interface to a=20
> bridge module...I do not think there is a conflict. It is filtering=20
> programmed prior to PW ingress by IEEE registration protocols for the=20
> purpose of multicast pruning in a single broadcast domain.
Registration
> of filtering needs to be tied to topology change being what I think is

> both your interest and concern....
>=20
> But if I were to back this up to where efforts appear to be going....
>=20
> 1) preferred forwarding as a means of semaphoring a topology change=20
> across a VPLS instance appears to be well advanced. That it can be
used
> as an aggregated MAC withdraw for PBBNs seems consistent with where
PWE
> is already going. That it can stunt double for a topology change BPDU
I
> do not think is a stretch as that is exactly what it is=20
> communicating....
>=20
> 2) Multicast MAC filtering at the ingress to a broadcast domain does=20
> not involve modifications to IEEE registration protocols in my=20
> proposal,
or
> is statically provisioned (as in Ali's proposal),and at least that
part
> is exclusive to the bridge module so does not seem to undermine your=20
> concerns.
>=20
> Does my analysis align with yours?
> Thanks
> Dave
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf

> Of Shane Amante
> Sent: Thursday, July 24, 2008 1:51 PM
> To: l2vpn@ietf.org
> Subject: VPLS Architecture
>=20
> Recently, a significant number of drafts have been submitted, and=20
> discussed, to address incorporating 802.1ag, 802.1ah and other
IEEE/ITU
> protocols within the VPLS Architecture.  These drafts appear to
largely
> be: a) a re-specification of how IEEE protocols work over top of a=20
> VPLS; or, b) how IEEE protocols inter-work with other IEEE data-plane
formats
> within a VPLS (or PWE3's).  In addition, for completeness, there is a=20
> question which L2VPN hasn't addressed: the potential for inter-working

> Native Service Layer control protocols from the IEEE/ITU with those=20
> created and maintained by L2VPN.
>=20
> With respect to the first question (re-specification of other SDO's=20
> protocols), there are a significant number of concerns.  Specifically,

> when protocols from another SDO are re-specified within the IETF,
there
> is the potential for errors or omissions to be introduced.  In
general,
> there is likely to be insufficient expertise widely available within=20
> the IETF to review those drafts, in-depth, for accuracy or=20
> "faithfulness"
> to
> the original SDO's standard as they progress through the IETF
standards
> process.  Finally, there is always the [unanswered] question of what=20
> SDO's document is considered authoritative in case a conflict, error
or
> omission develops.  In summary, there is both little value and=20
> significant risk in widespread re-publication of IEEE/ITU=20
> specifications within the L2VPN WG.  In a well written draft,=20
> Normative References to another SDO's detailed architecture, protocol=20
> or technology documents should be more than adequate, and seems to=20
> have worked well, so far, particularly in the cases of VPLS-LDP [RFC=20
> 4762] and VPLS-BGP [RFC 4761] to cite just two examples.
>=20
> On the other hand, the second and third questions, both raise=20
> significant concerns about the current and future architecture of
VPLS.
>=20
> With respect to the second question (interworking of two IEEE data-=20
> plane protocols within a VPLS), L2VPN (via PWE3 WG) seems to have gone

> down
a
> path of just defining a new PW type for a new IEEE data-plane (i.e.:
> draft-martini-pwe3-802.1ah-pw-02), most likely based on past precedent

> of raw and tagged Ethernet PW types, which were originally specified
as
> such to make up for hardware limitations at the time.  Instead, the
> (much) larger question that should be asked is: why can't the VPLS=20
> architecture *seamlessly* support existing/legacy and new Ethernet=20
> data-plane formats concurrently?  In other words, what is lacking in=20
> the current emulation of PW's that needs to be fixed in order to=20
> provide more seamless carriage of Ethernet frames within a VPLS, so=20
> that the VPLS architecture can remain agnostic to current and future=20
> IEEE data-plane protocols?
>=20
> Related to this last point, a number of people have put together the=20
> following draft specifying a "Generic Ethernet PW",=20
> <http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
> whose purpose is to re-cast Ethernet PW's back into a generic Ethernet

> transport mechanism, (as was originally desired).  In doing so,=20
> processing related to the "normalization" of Ethernet frames is then=20
> shifted back into the ingress or egress PW Native Service Processing
> (NSP) functions.  From an architecture standpoint, the NSP function
has
> direct (configured) knowledge of the incoming/outgoing data-plane=20
> format as well as any associated actions that need to be performed=20
> when receiving from or transmitting to the AC.  This would allow a=20
> (Generic
> Ethernet) PW and, consequently, VPLS to (again) remain agnostic as to=20
> the Ethernet data-plane, thus allowing seamless support of existing
and
> emerging (or, even, future) IEEE data-plane protocols.
>=20
> Finally, there is the third question (inter-working of Native Service=20
> Layer (NSL) control protocols with VPLS).  One component of the VPLS=20
> Architecture, is a "Bridge Module", which is equivalent to a PW
NSP[1].
>   Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2, it=20
> is noted that "precise functionality that the bridge modules must have

> in particular circumstances is, however, out of scope of the current=20
> document".  In other words, the VPLS architecture should be oblivious=20
> to Native Service Layer control protocols entering, exiting or=20
> processed within the Bridge Module.  The main reason for this is to=20
> avoid re-specification of other SDO's protocols.  A secondary reason=20
> is to avoid unnecessary and uncomfortably tight coupling of other=20
> SDO's NSL control protocols with those specified and maintained within

> the IETF L2VPN (or PWE3) WG's.  Finally, this allows end-users and=20
> implementers to expect the NSL Layer-2 Control Protocols operating=20
> within the
Bridge
> Module (or, PW NSP) to remain "faithful" to the original SDO's=20
> specification of those L2 control protocols.
>=20
> In summary, we believe that the architecture of VPLS (and PW's) should

> remain agnostic to the underlying data-plane, in order to simplify the

> overall architecture and /operation/ of VPLS.  Therefore, as
co-chairs,
> we will be placing overwhelming scrutiny on **all** drafts within the=20
> L2VPN WG, going forward, in order to avoid re-specification of other=20
> SDO's standards even as Informational Drafts.  Furthermore, we also=20
> will be guiding the WG to look at the fundamental architecture of=20
> VPLS, and its underlying PW's, to *first* determine what are the=20
> /requirements/ to ensure VPLS remains agnostic to data-plane=20
> protocols.  Eventually,
that
> should lead to specific enhancements/solutions to IETF protocols (VPLS

> and/or PW's) in order that we have the most straightforward=20
> implementations of VPLS, which are able to accommodate both present
and
> future data-plane protocols, thereby increasing the longevity of VPLS=20
> implementations and deployments.  Also, just to be clear, this latter=20
> task will most likely require careful coordination between both the=20
> L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS=20
> architecture and own/maintain key elements of VPLS control, signaling=20
> and encapsulation formats.
>=20
> Thanks,
>=20
> -shane & Vach
> co-chairs of L2VPN WG
>=20
> [1] The following is defined within PWE3 Architecture [RFC 3985]:
> ---snip---
>     Native Service Processing (NSP): Processing of the data received
by
>     the PE from the CE before presentation to the PW for transmission
>     across the core, or processing of the data received from a PW by a

> PE
>     before it is output on the AC.  NSP functionality is defined by
>     standards bodies other than the IETF, such as ITU-T, ANSI, or
> ATMF.)
> ---snip---
> In the context of this conversation, it is important to note that "NSP

> functionality is defined by standards bodies other than the IETF".
>=20
> [2] If we step back and look at history, the SUBIP and, subsequently,
> PWE3 WG's were clear about **not** providing perfect emulation of a=20
> Native Service over an MPLS PSN.  In fact, if one refers to the PW=20
> encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and=20
> Ethernet [RFC 4448] there is a clear "Applicability Statement" in=20
> Section 3 of all RFC's, where this is pointed out.  In addition, it=20
> points out in a very concise manner, "notable differences" between the

> traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Fri Jul 25 08:42:42 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE2E428C211;
	Fri, 25 Jul 2008 08:42:42 -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 4E7C228C201
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 08:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Q++YvI+Mkg9Q for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 08:42:39 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 4945E28C211
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 08:42:39 -0700 (PDT)
Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com
	[47.129.230.97])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m6PFgbu22298; Fri, 25 Jul 2008 15:42:37 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 11:41:53 -0400
Message-ID: <183DD1B052A11A40B76125E42F1CBAAB132721CB@zcarhxm1.corp.nortel.com>
In-Reply-To: <183DD1B052A11A40B76125E42F1CBAAB13272195@zcarhxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: Acjttd/drM08Xbw0TTKCS23UE0nkOgAs0DNgAAC9v+A=
References: <4888C10E.7040602@castlepoint.net>
	<183DD1B052A11A40B76125E42F1CBAAB13272195@zcarhxm1.corp.nortel.com>
From: "Dinesh Mohan" <mohand@nortel.com>
To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

And just to add to my second bullet:=20

I do not think that we currently have any activities in WG (in context
of activities that I have been involved in) which are attempting to
redefine the protocols/technologies being used in other SDOs, rather,
what we have is an application of these to address issues identified
with VPLS in draft-ietf-l2vpn-vpls-bridge-interop, similar to
application of Ethernet bridging in VPLS-LDP [RFC 4762] and VPLS-BGP
[RFC 4761].

---
Dinesh

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Mohan, Dinesh (CAR:NP02)
Sent: Friday, July 25, 2008 11:33 AM
To: Shane Amante; l2vpn@ietf.org
Subject: RE: VPLS Architecture

Shane,

I must admit I am still trying to grasp the context of your note, since
as a WG we had recently spent quite a bit of time in updating the
charter for L2PVN and most drafts that you refer to, if not all, were
already in consideration for the WG.

In the meantime I would like to make few observations:

- It seems to me that the basic VPLS functionality becomes questionable
here since as you state below <<One component of the VPLS Architecture,
is a "Bridge Module", which is equivalent to a PW NSP[1]>> and if NSP is
not the focus, then we should simply be working on defining PWs and
should be done. IEEE already a well defined definition of a bridge, and
we should not need VPLS. But I am sure I have misunderstood.

- There is no disagreement that we should not re-specify other SDO
protocols and technologies. However, when we do take the liberty of
using these protocols and technologies, should we not be obligated to
ensure that we get approval from these bodies to ensure that our
interpretation of these protocols and technologies is consistent with
the other SDOs. I bring this up since you have mentioned below <<In
general, there is likely to be insufficient expertise widely available
within the IETF to review those drafts, in-depth, for accuracy or
"faithfulness" to the original SDO's standard as they progress through
the IETF standards process.>> As far as I know neither VPLS-LDP [RFC
4762] and VPLS-BGP [RFC 4761] have gone through such review yet we, as
L2VPN WG cite these as shining examples. So what are the issues that we
are confronted with now suddenly?

- We can certainly try to step aside some of the discussions by citing
<<**not** providing perfect emulation of a Native Service over an MPLS
PSN>> but I am not sure if this is sufficient.
draft-ietf-l2vpn-vpls-bridge-interop highlights the issues confronted
with current day VPLS solutions and no wonder WG has been trying to
address some of these already and with the charter updating highlighting
others that need to be and which already have active work underway in
WG. If this is not an issue, why bother with these follow-ups since VPLS
is already done via VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761].

Therefore, I am still confused with this sudden message.

---
Dinesh

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Shane Amante
Sent: Thursday, July 24, 2008 1:51 PM
To: l2vpn@ietf.org
Subject: VPLS Architecture

Recently, a significant number of drafts have been submitted, and
discussed, to address incorporating 802.1ag, 802.1ah and other IEEE/ITU
protocols within the VPLS Architecture.  These drafts appear to largely
be: a) a re-specification of how IEEE protocols work over top of a VPLS;
or, b) how IEEE protocols inter-work with other IEEE data-plane formats
within a VPLS (or PWE3's).  In addition, for completeness, there is a
question which L2VPN hasn't addressed: the potential for inter-working
Native Service Layer control protocols from the IEEE/ITU with those
created and maintained by L2VPN.

With respect to the first question (re-specification of other SDO's
protocols), there are a significant number of concerns.  Specifically,
when protocols from another SDO are re-specified within the IETF, there
is the potential for errors or omissions to be introduced.  In general,
there is likely to be insufficient expertise widely available within the
IETF to review those drafts, in-depth, for accuracy or "faithfulness" to
the original SDO's standard as they progress through the IETF standards
process.  Finally, there is always the [unanswered] question of what
SDO's document is considered authoritative in case a conflict, error or
omission develops.  In summary, there is both little value and
significant risk in widespread re-publication of IEEE/ITU specifications
within the L2VPN WG.  In a well written draft, Normative References to
another SDO's detailed architecture, protocol or technology documents
should be more than adequate, and seems to have worked well, so far,
particularly in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761]
to cite just two examples.

On the other hand, the second and third questions, both raise
significant concerns about the current and future architecture of VPLS.

With respect to the second question (interworking of two IEEE data-plane
protocols within a VPLS), L2VPN (via PWE3 WG) seems to have gone down a
path of just defining a new PW type for a new IEEE data-plane (i.e.:=20
draft-martini-pwe3-802.1ah-pw-02), most likely based on past precedent
of raw and tagged Ethernet PW types, which were originally specified as
such to make up for hardware limitations at the time.  Instead, the
(much) larger question that should be asked is: why can't the VPLS
architecture *seamlessly* support existing/legacy and new Ethernet
data-plane formats concurrently?  In other words, what is lacking in the
current emulation of PW's that needs to be fixed in order to provide
more seamless carriage of Ethernet frames within a VPLS, so that the
VPLS architecture can remain agnostic to current and future IEEE
data-plane protocols?

Related to this last point, a number of people have put together the
following draft specifying a "Generic Ethernet PW",
<http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
whose purpose is to re-cast Ethernet PW's back into a generic Ethernet
transport mechanism, (as was originally desired).  In doing so,
processing related to the "normalization" of Ethernet frames is then
shifted back into the ingress or egress PW Native Service Processing
(NSP) functions.  From an architecture standpoint, the NSP function has
direct (configured) knowledge of the incoming/outgoing data-plane format
as well as any associated actions that need to be performed when
receiving from or transmitting to the AC.  This would allow a (Generic
Ethernet) PW and, consequently, VPLS to (again) remain agnostic as to
the Ethernet data-plane, thus allowing seamless support of existing and
emerging (or, even, future) IEEE data-plane protocols.

Finally, there is the third question (inter-working of Native Service
Layer (NSL) control protocols with VPLS).  One component of the VPLS
Architecture, is a "Bridge Module", which is equivalent to a PW NSP[1].=20
  Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2, it is
noted that "precise functionality that the bridge modules must have in
particular circumstances is, however, out of scope of the current
document".  In other words, the VPLS architecture should be oblivious to
Native Service Layer control protocols entering, exiting or processed
within the Bridge Module.  The main reason for this is to avoid
re-specification of other SDO's protocols.  A secondary reason is to
avoid unnecessary and uncomfortably tight coupling of other SDO's NSL
control protocols with those specified and maintained within the IETF
L2VPN (or PWE3) WG's.  Finally, this allows end-users and implementers
to expect the NSL Layer-2 Control Protocols operating within the Bridge
Module (or, PW NSP) to remain "faithful" to the original SDO's
specification of those L2 control protocols.

In summary, we believe that the architecture of VPLS (and PW's) should
remain agnostic to the underlying data-plane, in order to simplify the
overall architecture and /operation/ of VPLS.  Therefore, as co-chairs,
we will be placing overwhelming scrutiny on **all** drafts within the
L2VPN WG, going forward, in order to avoid re-specification of other
SDO's standards even as Informational Drafts.  Furthermore, we also will
be guiding the WG to look at the fundamental architecture of VPLS, and
its underlying PW's, to *first* determine what are the /requirements/ to
ensure VPLS remains agnostic to data-plane protocols.  Eventually, that
should lead to specific enhancements/solutions to IETF protocols (VPLS
and/or PW's) in order that we have the most straightforward
implementations of VPLS, which are able to accommodate both present and
future data-plane protocols, thereby increasing the longevity of VPLS
implementations and deployments.  Also, just to be clear, this latter
task will most likely require careful coordination between both the
L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS
architecture and own/maintain key elements of VPLS control, signaling
and encapsulation formats.

Thanks,

-shane & Vach
co-chairs of L2VPN WG

[1] The following is defined within PWE3 Architecture [RFC 3985]:
---snip---
    Native Service Processing (NSP): Processing of the data received by
    the PE from the CE before presentation to the PW for transmission
    across the core, or processing of the data received from a PW by a
PE
    before it is output on the AC.  NSP functionality is defined by
    standards bodies other than the IETF, such as ITU-T, ANSI, or ATMF.)
---snip---
In the context of this conversation, it is important to note that "NSP
functionality is defined by standards bodies other than the IETF".

[2] If we step back and look at history, the SUBIP and, subsequently,
PWE3 WG's were clear about **not** providing perfect emulation of a
Native Service over an MPLS PSN.  In fact, if one refers to the PW
encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and
Ethernet [RFC 4448] there is a clear "Applicability Statement" in
Section 3 of all RFC's, where this is pointed out.  In addition, it
points out in a very concise manner, "notable differences" between the
traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Fri Jul 25 11:36:32 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57BF828C17E;
	Fri, 25 Jul 2008 11:36:32 -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 D848928C16A
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 11:36:31 -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 0MALfcjLTp+Y for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 11:36:31 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id 0C1C528C17E
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 11:36:30 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id m6PIaP5B024464;
	Fri, 25 Jul 2008 13:36:25 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 25 Jul 2008 13:36:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 13:38:32 -0500
Message-ID: <40B2D3B1A8D67246A33D2F5B832C17E7016BAD6C@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <183DD1B052A11A40B76125E42F1CBAAB132721CB@zcarhxm1.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: Acjttd/drM08Xbw0TTKCS23UE0nkOgAs0DNgAAC9v+AABhwS0A==
From: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>
To: "Dinesh Mohan" <mohand@nortel.com>, "Shane Amante" <shane@castlepoint.net>,
	<l2vpn@ietf.org>
X-OriginalArrivalTime: 25 Jul 2008 18:36:25.0685 (UTC)
	FILETIME=[5823A050:01C8EE85]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Dinesh, Dave, Ali, Florin,

This is not a sudden email, but we have been discussing this issue for a
while internally.

The basic point is an architectural issue: if we have done a decent job
in describing what is in the scope of the PWE and L2VPN architectures,
and what is NSP/Bridge module functionality, then we can clearly
distinguish what protocols are IEEE and what are IETF, and whether there
needs to be any interaction between them.

If we haven't done a good job, then we should fix the architecture.
Shane put down our thoughts at some length so there would be enough
context to understand the concerns on direction.

I hesitate to step in and argue points yet because I want to gauge the
WG concerns.

-Vach =20


From l2vpn-bounces@ietf.org  Fri Jul 25 14:16:07 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B55573A685F;
	Fri, 25 Jul 2008 14:16:07 -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 C99783A677D
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 14:16:06 -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 P7uEwECI2NIK for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 14:16:06 -0700 (PDT)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.226])
	by core3.amsl.com (Postfix) with ESMTP id C34933A6A35
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 14:15:59 -0700 (PDT)
Received: by wr-out-0506.google.com with SMTP id 37so3366830wra.17
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 14:16:01 -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:references;
	bh=hWY2A4hEwbO+fa143yldBl1/ZcbfT04EyCW+dtO7l0M=;
	b=OczXsJ2qv1wQW8iAu/jQkWIDwL5nklksRRnwqHK4ST0tTIyEbd/wb9dRABzzXEZO0o
	BlNHW2qR9HJQX/RhakNNqEB4Xplrj26HKL6Pjw6Dgzn1jtcf/iDXOAmW737IxwR+Pnu7
	1mX8HLGSYqvDmRB1swGYywYBu5FOpobBCiQOw=
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:references;
	b=n8Rl1J/xgGJ6hGuGLUL/0b1AEM/qDLWOdP0pPQA8fhiQiGXKpiSzIEDCRH+hxL/e5q
	GWOSBWEi0Rtu9yeiE1ZAX/wTqzQ6hS9lFlVOtgcX4gorL0roiBZGPs8ow5Td5sEAMVh6
	iYvxYq2GMBf3ecMC9ZZuZLaRerafdmIQ9/Ew0=
Received: by 10.101.67.15 with SMTP id u15mr3741172ank.136.1217020561430;
	Fri, 25 Jul 2008 14:16:01 -0700 (PDT)
Received: by 10.151.14.6 with HTTP; Fri, 25 Jul 2008 14:16:01 -0700 (PDT)
Message-ID: <8c99930d0807251416p60fda1e9ld57cd2a0ab7d70a3@mail.gmail.com>
Date: Fri, 25 Jul 2008 17:16:01 -0400
From: "Andrew G. Malis" <agmalis@gmail.com>
To: "KOMPELLA Vach" <Vach.Kompella@alcatel-lucent.com>
Subject: Re: VPLS Architecture
In-Reply-To: <40B2D3B1A8D67246A33D2F5B832C17E7016BAD6C@USDALSMBS03.ad3.ad.alcatel.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_6325_21144480.1217020561423"
References: <183DD1B052A11A40B76125E42F1CBAAB132721CB@zcarhxm1.corp.nortel.com>
	<40B2D3B1A8D67246A33D2F5B832C17E7016BAD6C@USDALSMBS03.ad3.ad.alcatel.com>
Cc: l2vpn@ietf.org, Dinesh Mohan <mohand@nortel.com>,
	Shane Amante <shane@castlepoint.net>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

------=_Part_6325_21144480.1217020561423
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Well, I'm a co-author, so you can't call me neutral, but I think
draft-vkompella-pwe3-ethernet-pw-bis-01 is a much architecturally cleaner
recasting of RFC 4448, and we made sure that it's backwards compatible with
existing 4448 implementations.

Cheers,
Andy
On Fri, Jul 25, 2008 at 2:38 PM, KOMPELLA Vach <
Vach.Kompella@alcatel-lucent.com> wrote:

> Dinesh, Dave, Ali, Florin,
>
> This is not a sudden email, but we have been discussing this issue for a
> while internally.
>
> The basic point is an architectural issue: if we have done a decent job
> in describing what is in the scope of the PWE and L2VPN architectures,
> and what is NSP/Bridge module functionality, then we can clearly
> distinguish what protocols are IEEE and what are IETF, and whether there
> needs to be any interaction between them.
>
> If we haven't done a good job, then we should fix the architecture.
> Shane put down our thoughts at some length so there would be enough
> context to understand the concerns on direction.
>
> I hesitate to step in and argue points yet because I want to gauge the
> WG concerns.
>
> -Vach
>

------=_Part_6325_21144480.1217020561423
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr"><div>Well, I&#39;m a co-author, so you can&#39;t call me neutral, but I think draft-vkompella-pwe3-ethernet-pw-bis-01 is a much architecturally cleaner recasting of RFC 4448, and we&nbsp;made sure that it&#39;s&nbsp;backwards compatible with existing 4448 implementations.</div>

<div>&nbsp;</div>
<div>Cheers,</div>
<div>Andy<br></div>
<div class="gmail_quote">On Fri, Jul 25, 2008 at 2:38 PM, KOMPELLA Vach <span dir="ltr">&lt;<a href="mailto:Vach.Kompella@alcatel-lucent.com">Vach.Kompella@alcatel-lucent.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dinesh, Dave, Ali, Florin,<br><br>This is not a sudden email, but we have been discussing this issue for a<br>
while internally.<br><br>The basic point is an architectural issue: if we have done a decent job<br>in describing what is in the scope of the PWE and L2VPN architectures,<br>and what is NSP/Bridge module functionality, then we can clearly<br>
distinguish what protocols are IEEE and what are IETF, and whether there<br>needs to be any interaction between them.<br><br>If we haven&#39;t done a good job, then we should fix the architecture.<br>Shane put down our thoughts at some length so there would be enough<br>
context to understand the concerns on direction.<br><br>I hesitate to step in and argue points yet because I want to gauge the<br>WG concerns.<br><font color="#888888"><br>-Vach<br></font></blockquote></div><br></div>

------=_Part_6325_21144480.1217020561423--


From l2vpn-bounces@ietf.org  Fri Jul 25 17:56:35 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11D3F3A69A4;
	Fri, 25 Jul 2008 17:56:35 -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 4E1533A69A4
	for <l2vpn@core3.amsl.com>; Fri, 25 Jul 2008 17:56:33 -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 oFI+f3zXHad5 for <l2vpn@core3.amsl.com>;
	Fri, 25 Jul 2008 17:56:31 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id 4172B3A695A
	for <l2vpn@ietf.org>; Fri, 25 Jul 2008 17:56:30 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id m6Q0uNbf016115;
	Fri, 25 Jul 2008 19:56:24 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 25 Jul 2008 19:56:23 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Fri, 25 Jul 2008 19:56:14 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0479188F@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <87AC5F88F03E6249AEA68D40BD3E00BE16831872@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjtteM20JxCCB2wSMmYeU9/lf8NOQAfyP7AAAm+73AAA53IQAATAb5Q
References: <4888C10E.7040602@castlepoint.net><87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com><4A5028372622294A99B8FFF6BD06EB7B047916E3@USDALSMBS03.ad3.ad.alcatel.com>
	<87AC5F88F03E6249AEA68D40BD3E00BE16831872@zcarhxm2.corp.nortel.com>
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "David Allan" <dallan@nortel.com>, "Shane Amante" <shane@castlepoint.net>, 
	<l2vpn@ietf.org>
X-OriginalArrivalTime: 26 Jul 2008 00:56:23.0816 (UTC)
	FILETIME=[6CE25880:01C8EEBA]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Cc: Tony Jeffree <tony@JEFFREE.CO.UK>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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 Dave,

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
> Of David Allan
> Sent: Friday, July 25, 2008 8:41 AM
> To: BALUS Florin; Shane Amante; l2vpn@ietf.org
> Cc: Tony Jeffree
> Subject: RE: VPLS Architecture
>=20
> Hi Florin
>=20
> > This is not about VPLS not being aware about IEEE protocols you list
> below. It's about the fact that with proper, IEEE
> > compliant implementations, the VPLS NSP (native service processing)
> module will handle the interactions in an
> > interoperable fashion. That was the whole idea, otherwise we will
> keep
> reproducing all the IEEE work in IETF L2VPN WG.
>=20
> That of course makes perfect sense, I was seeking to clarify that. But
> I
> actually need that confirmation from the chairs...
>=20
> > So I agree with Shane's email: i.e. for IEEE specifically, if a
> solution requires development or new interaction for an > IEEE
protocol
> then it should be brought up in the related IEEE session first.
> Especially if it applies to both IEEE
> > native domains (e.g. native QinQ or PBB) and VPLS.
>=20
> I do not think that is what is being proposed....


[[FB]] I was talking here about the general case not about your
proposal.

>=20
> > For the case in hand (your draft and IEEE 802.1ah, 802.1ak MMRP
> specs)
> if a VPLS designer reads the IEEE specifications > it will be able to
> implement them no problem. And the resulting (proper) implementations
> will just interoperate. Why do > we need to spend any cycles in L2VPN
> WG
> on this?
>=20
> So you are suggesting we are already done and do not need to consider
> this or any other drafts on 802.1ah???? You surprise me!

[[FB]] I like to surprise especially people that used to know me! :)=20
I don't think I said something about "any other IEEE 802.1ah drafts". I
was talking about the IEEE 802.1ah specification in the context of MMRP:
i.e. IEEE 802.1ah section 26.4 describes how 802.1ak MMRP can be used in
a PBB context. IEEE 802.1ak MMRP also describes the protocol in detail.
In my opinion between the two specs there is plenty of information to
make it work for PBB-VPLS.=20
>=20
> There is one point to be validated,  the distinction that a PE is at a
> boundary between an active topology an a split horizon mesh, VPLS may
> provide an input into the state machine for the mesh facing MMRP
> implementation. That is a missing component to produce a very viable
> model, and IMO would be worth spending a small number of cycles upon.
>=20
[[FB]] The VPLS PW Mesh is part of the active topology that MMRP can
just use to distribute its declarations/receive the registrations on a
per PW basis. I do not see an issue, maybe we can do some whiteboarding
on that in IETF-72.=20

> If the group finds it of interest, a liaison to Tony and co. to test
> that this does not break anything would be useful if the group does
not
> consider it immediately obvious. I believe it doesn't break anything.

[[FB]] I do not expect anything to break but asking the IEEE experts
won't hurt.=20

>=20
> > If something is broken in the IEEE protocol then the interested
> parties should just go to IEEE and discuss fixes,
> > extensions to the protocol in the related IEEE sessions, where all
> the
> protocol knowledge is concentrated.
>=20
> > This is actually what happened 18 months ago with IEEE 802.1ak -
> there
> were problems with the protocol base, a
> > corrigendum was opened and solutions were discussed in there that
can
> be applied, no problem, to both native Ethernet
> > domains and VPLS. Tony, one of the IEEE 802.1ak editor (in CC),
drove
> the changes smoothly through the process.
>=20
> > There were no cycles spent on this in L2VPN WG. I think we should
> keep
> it this way to maintain proper protocol
> > development.
>=20
> As the draft proposes a model of how MMRP is used and does not suggest
> anything is broken with it, your points escape me.

[[FB]] I thought the way MMRP issues were handled was a good generic
example on how we should handle issues related to IEEE protocol
development: i.e. although the interest for MMRP usage came from VPLS
implementations, the fixes were addressed in IEEE without involving
IETF. The example just happened to be MMRP, no linkage to your proposal.

>=20
> Cheers
> Dave
>=20
>=20
>=20
> > -----Original Message-----
> > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On
> Behalf
>=20
> > Of David Allan
> > Sent: Friday, July 25, 2008 2:29 AM
> > To: Shane Amante; l2vpn@ietf.org
> > Subject: RE: VPLS Architecture
> >
> > HI Shane: I'm trying to understand this in the context of
> > draft-allan-mmrp... And other proposals....
> >
> > What I get out of this raises a number of points of interest....
> >
> > 1) No interaction with L2 protocols in theory takes all possibility
> of
>=20
> > resilient access off the table except as a pure overlay over totally
> > static and unfiltered VPLS instance(s). Some interaction is required
> to
> > ensure VPLS is not creating a loop if it has more than one point of
> > attachment to a broadcast domain. However if that interaction is off
> > the table then (for example) preferred forwarding which implies
> interaction
> > with peer networks protocols such as LACP, is a piece of work that
> > should be abandoned by this criteria...
> >
> > MAC withdraw is effectively interaction with IEEE control protocols
> of
>=20
> > some form similar to 1. Topology change BPDUs transparently passed
> over
> > PWs between bridge modules would appear to be the only acceptable
> > approach by this criteria...
> >
> > Which actually would work just fine as far as draft allan is
> > concerned... But for the case where ALL bridge modules do not have
> STP
>=20
> > enabled, preferred forwarding needs to stunt double...
> >
> > 2) In the case of MMRP if the PW is presented as an interface to a
> > bridge module...I do not think there is a conflict. It is filtering
> > programmed prior to PW ingress by IEEE registration protocols for
the
> > purpose of multicast pruning in a single broadcast domain.
> Registration
> > of filtering needs to be tied to topology change being what I think
> is
>=20
> > both your interest and concern....
> >
> > But if I were to back this up to where efforts appear to be
going....
> >
> > 1) preferred forwarding as a means of semaphoring a topology change
> > across a VPLS instance appears to be well advanced. That it can be
> used
> > as an aggregated MAC withdraw for PBBNs seems consistent with where
> PWE
> > is already going. That it can stunt double for a topology change
BPDU
> I
> > do not think is a stretch as that is exactly what it is
> > communicating....
> >
> > 2) Multicast MAC filtering at the ingress to a broadcast domain does
> > not involve modifications to IEEE registration protocols in my
> > proposal,
> or
> > is statically provisioned (as in Ali's proposal),and at least that
> part
> > is exclusive to the bridge module so does not seem to undermine your
> > concerns.
> >
> > Does my analysis align with yours?
> > Thanks
> > Dave
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On
> Behalf
>=20
> > Of Shane Amante
> > Sent: Thursday, July 24, 2008 1:51 PM
> > To: l2vpn@ietf.org
> > Subject: VPLS Architecture
> >
> > Recently, a significant number of drafts have been submitted, and
> > discussed, to address incorporating 802.1ag, 802.1ah and other
> IEEE/ITU
> > protocols within the VPLS Architecture.  These drafts appear to
> largely
> > be: a) a re-specification of how IEEE protocols work over top of a
> > VPLS; or, b) how IEEE protocols inter-work with other IEEE
data-plane
> formats
> > within a VPLS (or PWE3's).  In addition, for completeness, there is
a
> > question which L2VPN hasn't addressed: the potential for inter-
> working
>=20
> > Native Service Layer control protocols from the IEEE/ITU with those
> > created and maintained by L2VPN.
> >
> > With respect to the first question (re-specification of other SDO's
> > protocols), there are a significant number of concerns.
> Specifically,
>=20
> > when protocols from another SDO are re-specified within the IETF,
> there
> > is the potential for errors or omissions to be introduced.  In
> general,
> > there is likely to be insufficient expertise widely available within
> > the IETF to review those drafts, in-depth, for accuracy or
> > "faithfulness"
> > to
> > the original SDO's standard as they progress through the IETF
> standards
> > process.  Finally, there is always the [unanswered] question of what
> > SDO's document is considered authoritative in case a conflict, error
> or
> > omission develops.  In summary, there is both little value and
> > significant risk in widespread re-publication of IEEE/ITU
> > specifications within the L2VPN WG.  In a well written draft,
> > Normative References to another SDO's detailed architecture,
protocol
> > or technology documents should be more than adequate, and seems to
> > have worked well, so far, particularly in the cases of VPLS-LDP [RFC
> > 4762] and VPLS-BGP [RFC 4761] to cite just two examples.
> >
> > On the other hand, the second and third questions, both raise
> > significant concerns about the current and future architecture of
> VPLS.
> >
> > With respect to the second question (interworking of two IEEE data-
> > plane protocols within a VPLS), L2VPN (via PWE3 WG) seems to have
> gone
>=20
> > down
> a
> > path of just defining a new PW type for a new IEEE data-plane (i.e.:
> > draft-martini-pwe3-802.1ah-pw-02), most likely based on past
> precedent
>=20
> > of raw and tagged Ethernet PW types, which were originally specified
> as
> > such to make up for hardware limitations at the time.  Instead, the
> > (much) larger question that should be asked is: why can't the VPLS
> > architecture *seamlessly* support existing/legacy and new Ethernet
> > data-plane formats concurrently?  In other words, what is lacking in
> > the current emulation of PW's that needs to be fixed in order to
> > provide more seamless carriage of Ethernet frames within a VPLS, so
> > that the VPLS architecture can remain agnostic to current and future
> > IEEE data-plane protocols?
> >
> > Related to this last point, a number of people have put together the
> > following draft specifying a "Generic Ethernet PW",
> >
<http://tools.ietf.org/html/draft-vkompella-pwe3-ethernet-pw-bis-01>,
> > whose purpose is to re-cast Ethernet PW's back into a generic
> Ethernet
>=20
> > transport mechanism, (as was originally desired).  In doing so,
> > processing related to the "normalization" of Ethernet frames is then
> > shifted back into the ingress or egress PW Native Service Processing
> > (NSP) functions.  From an architecture standpoint, the NSP function
> has
> > direct (configured) knowledge of the incoming/outgoing data-plane
> > format as well as any associated actions that need to be performed
> > when receiving from or transmitting to the AC.  This would allow a
> > (Generic
> > Ethernet) PW and, consequently, VPLS to (again) remain agnostic as
to
> > the Ethernet data-plane, thus allowing seamless support of existing
> and
> > emerging (or, even, future) IEEE data-plane protocols.
> >
> > Finally, there is the third question (inter-working of Native
Service
> > Layer (NSL) control protocols with VPLS).  One component of the VPLS
> > Architecture, is a "Bridge Module", which is equivalent to a PW
> NSP[1].
> >   Furthermore, within the L2VPN Framework [RFC 4664], Section 2.2,
it
> > is noted that "precise functionality that the bridge modules must
> have
>=20
> > in particular circumstances is, however, out of scope of the current
> > document".  In other words, the VPLS architecture should be
oblivious
> > to Native Service Layer control protocols entering, exiting or
> > processed within the Bridge Module.  The main reason for this is to
> > avoid re-specification of other SDO's protocols.  A secondary reason
> > is to avoid unnecessary and uncomfortably tight coupling of other
> > SDO's NSL control protocols with those specified and maintained
> within
>=20
> > the IETF L2VPN (or PWE3) WG's.  Finally, this allows end-users and
> > implementers to expect the NSL Layer-2 Control Protocols operating
> > within the
> Bridge
> > Module (or, PW NSP) to remain "faithful" to the original SDO's
> > specification of those L2 control protocols.
> >
> > In summary, we believe that the architecture of VPLS (and PW's)
> should
>=20
> > remain agnostic to the underlying data-plane, in order to simplify
> the
>=20
> > overall architecture and /operation/ of VPLS.  Therefore, as
> co-chairs,
> > we will be placing overwhelming scrutiny on **all** drafts within
the
> > L2VPN WG, going forward, in order to avoid re-specification of other
> > SDO's standards even as Informational Drafts.  Furthermore, we also
> > will be guiding the WG to look at the fundamental architecture of
> > VPLS, and its underlying PW's, to *first* determine what are the
> > /requirements/ to ensure VPLS remains agnostic to data-plane
> > protocols.  Eventually,
> that
> > should lead to specific enhancements/solutions to IETF protocols
> (VPLS
>=20
> > and/or PW's) in order that we have the most straightforward
> > implementations of VPLS, which are able to accommodate both present
> and
> > future data-plane protocols, thereby increasing the longevity of
VPLS
> > implementations and deployments.  Also, just to be clear, this
latter
> > task will most likely require careful coordination between both the
> > L2VPN and PWE3 WG's, since PWE3 is an integral part of the VPLS
> > architecture and own/maintain key elements of VPLS control,
signaling
> > and encapsulation formats.
> >
> > Thanks,
> >
> > -shane & Vach
> > co-chairs of L2VPN WG
> >
> > [1] The following is defined within PWE3 Architecture [RFC 3985]:
> > ---snip---
> >     Native Service Processing (NSP): Processing of the data received
> by
> >     the PE from the CE before presentation to the PW for
transmission
> >     across the core, or processing of the data received from a PW by
> a
>=20
> > PE
> >     before it is output on the AC.  NSP functionality is defined by
> >     standards bodies other than the IETF, such as ITU-T, ANSI, or
> > ATMF.)
> > ---snip---
> > In the context of this conversation, it is important to note that
> "NSP
>=20
> > functionality is defined by standards bodies other than the IETF".
> >
> > [2] If we step back and look at history, the SUBIP and,
subsequently,
> > PWE3 WG's were clear about **not** providing perfect emulation of a
> > Native Service over an MPLS PSN.  In fact, if one refers to the PW
> > encapsulation RFC's for Frame Relay [RFC 4619], ATM [RFC 4717] and
> > Ethernet [RFC 4448] there is a clear "Applicability Statement" in
> > Section 3 of all RFC's, where this is pointed out.  In addition, it
> > points out in a very concise manner, "notable differences" between
> the
>=20
> > traditional Native Service and the new <FOO> over PW service.


From l2vpn-bounces@ietf.org  Sat Jul 26 09:16:47 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCF5E3A69FA;
	Sat, 26 Jul 2008 09:16:47 -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 4392F3A68CE
	for <l2vpn@core3.amsl.com>; Sat, 26 Jul 2008 09:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 mNgVQ1OvGz3Z for <l2vpn@core3.amsl.com>;
	Sat, 26 Jul 2008 09:16:44 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 0F0E23A69FA
	for <l2vpn@ietf.org>; Sat, 26 Jul 2008 09:16:43 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id F2E3126866A; Sat, 26 Jul 2008 10:16:47 -0600 (MDT)
Received: from pmac.castlepoint.net (71-215-77-82.hlrn.qwest.net
	[71.215.77.82]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Sat, 26 Jul 2008 10:16:47 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.77.82;
	client-port=2211; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <3D662E05-507C-452D-860A-7706ED69C215@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: David Allan <dallan@nortel.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Subject: Re: VPLS Architecture
Date: Sat, 26 Jul 2008 10:16:29 -0600
References: <4888C10E.7040602@castlepoint.net>
	<87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
X-Mailer: Apple Mail (2.928.1)
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Dave,

On Jul 25, 2008, at 3:28 AM, David Allan wrote:
> HI Shane: I'm trying to understand this in the context of
> draft-allan-mmrp... And other proposals....
>
> What I get out of this raises a number of points of interest....
>
> 1) No interaction with L2 protocols in theory takes all possibility of
> resilient access off the table except as a pure overlay over totally
> static and unfiltered VPLS instance(s). Some interaction is required  
> to
> ensure VPLS is not creating a loop if it has more than one point of
> attachment to a broadcast domain. However if that interaction is off  
> the
> table then (for example) preferred forwarding which implies  
> interaction
> with peer networks protocols such as LACP, is a piece of work that
> should be abandoned by this criteria...
>
> MAC withdraw is effectively interaction with IEEE control protocols of
> some form similar to 1. Topology change BPDUs transparently passed  
> over
> PWs between bridge modules would appear to be the only acceptable
> approach by this criteria...
>
> Which actually would work just fine as far as draft allan is
> concerned... But for the case where ALL bridge modules do not have STP
> enabled, preferred forwarding needs to stunt double...
>
> 2) In the case of MMRP if the PW is presented as an interface to a
> bridge module...I do not think there is a conflict. It is filtering
> programmed prior to PW ingress by IEEE registration protocols for the
> purpose of multicast pruning in a single broadcast domain.  
> Registration
> of filtering needs to be tied to topology change being what I think is
> both your interest and concern....
>
> But if I were to back this up to where efforts appear to be going....
>
> 1) preferred forwarding as a means of semaphoring a topology change
> across a VPLS instance appears to be well advanced. That it can be  
> used
> as an aggregated MAC withdraw for PBBNs seems consistent with where  
> PWE
> is already going. That it can stunt double for a topology change  
> BPDU I
> do not think is a stretch as that is exactly what it is
> communicating....
>
> 2) Multicast MAC filtering at the ingress to a broadcast domain does  
> not
> involve modifications to IEEE registration protocols in my proposal,  
> or
> is statically provisioned (as in Ali's proposal),and at least that  
> part
> is exclusive to the bridge module so does not seem to undermine your
> concerns.
>
> Does my analysis align with yours?

No, it does not.

Let's bring this back up a level and attempt to apply a much simpler  
"litmus test".  Specifically, what if VPLS were never invented or  
simply did not exist?  Alternatively, and more practically, what is  
done when VPLS does not exist in certain topologies/deployments?  In  
that case, the IEEE would either have a (scalable) solution that you  
are looking for or people would go to the IEEE and kick-off an effort  
to create such a solution, correct?

When viewed at from that perspective, it should hopefully be clear  
that solutions to this specific problem should belong in the NSP/ 
Bridge Module and, therefore, are out of the hands of the L2VPN WG.   
(Furthermore, if folks want to implement said solutions, they should  
go read the full IEEE spec to do so and we should not duplicate or  
otherwise re-publish it within the L2VPN WG).

Also, to bring this back to the context of VPLS Architecture, you did  
say the following:
---snip---
> 2) In the case of MMRP if the PW is presented as an interface to a
> bridge module...
---snip---
Currently, a VPLS instance on a VPLS-PE is defined (at least from a  
theoretical standpoint) as having a single LAN emulation interface  
between the Bridge Module and the VPLS Forwarder, which likely  
prevents one from applying IEEE filtering/forwarding Control Protocols  
against an individual PW, such as what you're attempting to define in  
draft-allan-mrrp (as an example).  Again, the larger question that  
should be being asked is: do we have a broken architecture and need to  
consider fixing it to allow it to more accurately (but, not perfectly)  
"emulate" a IEEE LAN?

Thanks,

-shane


From l2vpn-bounces@ietf.org  Sat Jul 26 09:38:15 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B7963A6A5E;
	Sat, 26 Jul 2008 09:38:15 -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 1C5A43A6A5E
	for <l2vpn@core3.amsl.com>; Sat, 26 Jul 2008 09:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 TmCcpU0i38Xa for <l2vpn@core3.amsl.com>;
	Sat, 26 Jul 2008 09:38:14 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 214973A67A7
	for <l2vpn@ietf.org>; Sat, 26 Jul 2008 09:38:14 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id EE9FF26866A; Sat, 26 Jul 2008 10:38:18 -0600 (MDT)
Received: from pmac.castlepoint.net (71-215-77-82.hlrn.qwest.net
	[71.215.77.82]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Sat, 26 Jul 2008 10:38:18 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.77.82;
	client-port=2781; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <D311CBB5-7E6B-4DD8-B708-B1E5C1CA2C21@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: David Allan <dallan@nortel.com>
In-Reply-To: <3D662E05-507C-452D-860A-7706ED69C215@castlepoint.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Subject: Re: VPLS Architecture
Date: Sat, 26 Jul 2008 10:38:02 -0600
References: <4888C10E.7040602@castlepoint.net>
	<87AC5F88F03E6249AEA68D40BD3E00BE16831861@zcarhxm2.corp.nortel.com>
	<3D662E05-507C-452D-860A-7706ED69C215@castlepoint.net>
X-Mailer: Apple Mail (2.928.1)
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

One follow-up to my own message, just to make sure I'm more clear ...

On Jul 26, 2008, at 10:16 AM, Shane Amante wrote:

> Dave,
>
> On Jul 25, 2008, at 3:28 AM, David Allan wrote:
>> HI Shane: I'm trying to understand this in the context of
>> draft-allan-mmrp... And other proposals....
>>
>> What I get out of this raises a number of points of interest....
>>
>> 1) No interaction with L2 protocols in theory takes all possibility  
>> of
>> resilient access off the table except as a pure overlay over totally
>> static and unfiltered VPLS instance(s). Some interaction is  
>> required to
>> ensure VPLS is not creating a loop if it has more than one point of
>> attachment to a broadcast domain. However if that interaction is  
>> off the
>> table then (for example) preferred forwarding which implies  
>> interaction
>> with peer networks protocols such as LACP, is a piece of work that
>> should be abandoned by this criteria...
>>
>> MAC withdraw is effectively interaction with IEEE control protocols  
>> of
>> some form similar to 1. Topology change BPDUs transparently passed  
>> over
>> PWs between bridge modules would appear to be the only acceptable
>> approach by this criteria...
>>
>> Which actually would work just fine as far as draft allan is
>> concerned... But for the case where ALL bridge modules do not have  
>> STP
>> enabled, preferred forwarding needs to stunt double...
>>
>> 2) In the case of MMRP if the PW is presented as an interface to a
>> bridge module...I do not think there is a conflict. It is filtering
>> programmed prior to PW ingress by IEEE registration protocols for the
>> purpose of multicast pruning in a single broadcast domain.  
>> Registration
>> of filtering needs to be tied to topology change being what I think  
>> is
>> both your interest and concern....
>>
>> But if I were to back this up to where efforts appear to be going....
>>
>> 1) preferred forwarding as a means of semaphoring a topology change
>> across a VPLS instance appears to be well advanced. That it can be  
>> used
>> as an aggregated MAC withdraw for PBBNs seems consistent with where  
>> PWE
>> is already going. That it can stunt double for a topology change  
>> BPDU I
>> do not think is a stretch as that is exactly what it is
>> communicating....
>>
>> 2) Multicast MAC filtering at the ingress to a broadcast domain  
>> does not
>> involve modifications to IEEE registration protocols in my  
>> proposal, or
>> is statically provisioned (as in Ali's proposal),and at least that  
>> part
>> is exclusive to the bridge module so does not seem to undermine your
>> concerns.
>>
>> Does my analysis align with yours?
>
> No, it does not.
>
> Let's bring this back up a level and attempt to apply a much simpler  
> "litmus test".  Specifically, what if VPLS were never invented or  
> simply did not exist?  Alternatively, and more practically, what is  
> done when VPLS does not exist in certain topologies/deployments?  In  
> that case, the IEEE would either have a (scalable) solution that you  
> are looking for or people would go to the IEEE and kick-off an  
> effort to create such a solution, correct?
>
> When viewed at from that perspective, it should hopefully be clear  
> that solutions to this specific problem should belong in the NSP/ 
> Bridge Module and, therefore, are out of the hands of the L2VPN WG.   
> (Furthermore, if folks want to implement said solutions, they should  
> go read the full IEEE spec to do so and we should not duplicate or  
> otherwise re-publish it within the L2VPN WG).
>
> Also, to bring this back to the context of VPLS Architecture, you  
> did say the following:
> ---snip---
>> 2) In the case of MMRP if the PW is presented as an interface to a
>> bridge module...
> ---snip---
> Currently, a VPLS instance on a VPLS-PE is defined (at least from a  
> theoretical standpoint) as having a single LAN emulation interface  
> between the Bridge Module and the VPLS Forwarder, which likely  
> prevents one from applying IEEE filtering/forwarding Control  
> Protocols against an individual PW, such as what you're attempting  
> to define in draft-allan-mrrp (as an example).  Again, the larger  
> question that should be being asked is: do we have a broken  
> architecture and need to consider fixing it to allow it to more  
> accurately (but, not perfectly) "emulate" a IEEE LAN?

I should have added on to the last sentence the following: " ... by,  
perhaps, considering an architectural change to VPLS such as exposing  
individual PW's to the Bridge Module".

-shane


From l2vpn-bounces@ietf.org  Sun Jul 27 01:42:50 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 574B83A68A0;
	Sun, 27 Jul 2008 01:42:50 -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 CAB033A68A0
	for <l2vpn@core3.amsl.com>; Sun, 27 Jul 2008 01:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 Ye7Ly8zR7svT for <l2vpn@core3.amsl.com>;
	Sun, 27 Jul 2008 01:42:47 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 3BF573A689D
	for <l2vpn@ietf.org>; Sun, 27 Jul 2008 01:42:47 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m6R8goI11241; Sun, 27 Jul 2008 08:42:50 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8EFC4.C015BD92"
Subject: Re: VPLS Architecture
Date: Sun, 27 Jul 2008 04:42:49 -0400
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE16831877@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjvPgRqhtIf+qOoT3iBNFD5IW2/MAAhrs5S
From: "David Allan" <dallan@nortel.com>
To: <shane@castlepoint.net>
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8EFC4.C015BD92
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGkgc2hhbmUNCg0KT0sgSSBnZXQgdGhlIG1vZGVsIGFuZCB0aGUgaW1wbGljYXRpb25zLiBMZXQn
cyBmb2xsb3cgdXAgaW4gRHVibGluDQoNCkQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpU
aHVtYiB0eXBlZCBieSBEYXZlIEFsbGFuLCBOb3J0ZWwNCg0KDQotLS0tLSBPcmlnaW5hbCBNZXNz
YWdlIC0tLS0tDQpGcm9tOiBTaGFuZSBBbWFudGUgPHNoYW5lQGNhc3RsZXBvaW50Lm5ldD4NClRv
OiBBbGxhbiwgRGF2aWQgKENBUjpOUzAwKQ0KQ2M6IGwydnBuQGlldGYub3JnIDxsMnZwbkBpZXRm
Lm9yZz4NClNlbnQ6IFNhdCBKdWwgMjYgMTI6Mzg6MDIgMjAwOA0KU3ViamVjdDogUmU6IFZQTFMg
QXJjaGl0ZWN0dXJlDQoNCk9uZSBmb2xsb3ctdXAgdG8gbXkgb3duIG1lc3NhZ2UsIGp1c3QgdG8g
bWFrZSBzdXJlIEknbSBtb3JlIGNsZWFyIC4uLg0KDQpPbiBKdWwgMjYsIDIwMDgsIGF0IDEwOjE2
IEFNLCBTaGFuZSBBbWFudGUgd3JvdGU6DQoNCj4gRGF2ZSwNCj4NCj4gT24gSnVsIDI1LCAyMDA4
LCBhdCAzOjI4IEFNLCBEYXZpZCBBbGxhbiB3cm90ZToNCj4+IEhJIFNoYW5lOiBJJ20gdHJ5aW5n
IHRvIHVuZGVyc3RhbmQgdGhpcyBpbiB0aGUgY29udGV4dCBvZg0KPj4gZHJhZnQtYWxsYW4tbW1y
cC4uLiBBbmQgb3RoZXIgcHJvcG9zYWxzLi4uLg0KPj4NCj4+IFdoYXQgSSBnZXQgb3V0IG9mIHRo
aXMgcmFpc2VzIGEgbnVtYmVyIG9mIHBvaW50cyBvZiBpbnRlcmVzdC4uLi4NCj4+DQo+PiAxKSBO
byBpbnRlcmFjdGlvbiB3aXRoIEwyIHByb3RvY29scyBpbiB0aGVvcnkgdGFrZXMgYWxsIHBvc3Np
YmlsaXR5ICANCj4+IG9mDQo+PiByZXNpbGllbnQgYWNjZXNzIG9mZiB0aGUgdGFibGUgZXhjZXB0
IGFzIGEgcHVyZSBvdmVybGF5IG92ZXIgdG90YWxseQ0KPj4gc3RhdGljIGFuZCB1bmZpbHRlcmVk
IFZQTFMgaW5zdGFuY2UocykuIFNvbWUgaW50ZXJhY3Rpb24gaXMgIA0KPj4gcmVxdWlyZWQgdG8N
Cj4+IGVuc3VyZSBWUExTIGlzIG5vdCBjcmVhdGluZyBhIGxvb3AgaWYgaXQgaGFzIG1vcmUgdGhh
biBvbmUgcG9pbnQgb2YNCj4+IGF0dGFjaG1lbnQgdG8gYSBicm9hZGNhc3QgZG9tYWluLiBIb3dl
dmVyIGlmIHRoYXQgaW50ZXJhY3Rpb24gaXMgIA0KPj4gb2ZmIHRoZQ0KPj4gdGFibGUgdGhlbiAo
Zm9yIGV4YW1wbGUpIHByZWZlcnJlZCBmb3J3YXJkaW5nIHdoaWNoIGltcGxpZXMgIA0KPj4gaW50
ZXJhY3Rpb24NCj4+IHdpdGggcGVlciBuZXR3b3JrcyBwcm90b2NvbHMgc3VjaCBhcyBMQUNQLCBp
cyBhIHBpZWNlIG9mIHdvcmsgdGhhdA0KPj4gc2hvdWxkIGJlIGFiYW5kb25lZCBieSB0aGlzIGNy
aXRlcmlhLi4uDQo+Pg0KPj4gTUFDIHdpdGhkcmF3IGlzIGVmZmVjdGl2ZWx5IGludGVyYWN0aW9u
IHdpdGggSUVFRSBjb250cm9sIHByb3RvY29scyAgDQo+PiBvZg0KPj4gc29tZSBmb3JtIHNpbWls
YXIgdG8gMS4gVG9wb2xvZ3kgY2hhbmdlIEJQRFVzIHRyYW5zcGFyZW50bHkgcGFzc2VkICANCj4+
IG92ZXINCj4+IFBXcyBiZXR3ZWVuIGJyaWRnZSBtb2R1bGVzIHdvdWxkIGFwcGVhciB0byBiZSB0
aGUgb25seSBhY2NlcHRhYmxlDQo+PiBhcHByb2FjaCBieSB0aGlzIGNyaXRlcmlhLi4uDQo+Pg0K
Pj4gV2hpY2ggYWN0dWFsbHkgd291bGQgd29yayBqdXN0IGZpbmUgYXMgZmFyIGFzIGRyYWZ0IGFs
bGFuIGlzDQo+PiBjb25jZXJuZWQuLi4gQnV0IGZvciB0aGUgY2FzZSB3aGVyZSBBTEwgYnJpZGdl
IG1vZHVsZXMgZG8gbm90IGhhdmUgIA0KPj4gU1RQDQo+PiBlbmFibGVkLCBwcmVmZXJyZWQgZm9y
d2FyZGluZyBuZWVkcyB0byBzdHVudCBkb3VibGUuLi4NCj4+DQo+PiAyKSBJbiB0aGUgY2FzZSBv
ZiBNTVJQIGlmIHRoZSBQVyBpcyBwcmVzZW50ZWQgYXMgYW4gaW50ZXJmYWNlIHRvIGENCj4+IGJy
aWRnZSBtb2R1bGUuLi5JIGRvIG5vdCB0aGluayB0aGVyZSBpcyBhIGNvbmZsaWN0LiBJdCBpcyBm
aWx0ZXJpbmcNCj4+IHByb2dyYW1tZWQgcHJpb3IgdG8gUFcgaW5ncmVzcyBieSBJRUVFIHJlZ2lz
dHJhdGlvbiBwcm90b2NvbHMgZm9yIHRoZQ0KPj4gcHVycG9zZSBvZiBtdWx0aWNhc3QgcHJ1bmlu
ZyBpbiBhIHNpbmdsZSBicm9hZGNhc3QgZG9tYWluLiAgDQo+PiBSZWdpc3RyYXRpb24NCj4+IG9m
IGZpbHRlcmluZyBuZWVkcyB0byBiZSB0aWVkIHRvIHRvcG9sb2d5IGNoYW5nZSBiZWluZyB3aGF0
IEkgdGhpbmsgIA0KPj4gaXMNCj4+IGJvdGggeW91ciBpbnRlcmVzdCBhbmQgY29uY2Vybi4uLi4N
Cj4+DQo+PiBCdXQgaWYgSSB3ZXJlIHRvIGJhY2sgdGhpcyB1cCB0byB3aGVyZSBlZmZvcnRzIGFw
cGVhciB0byBiZSBnb2luZy4uLi4NCj4+DQo+PiAxKSBwcmVmZXJyZWQgZm9yd2FyZGluZyBhcyBh
IG1lYW5zIG9mIHNlbWFwaG9yaW5nIGEgdG9wb2xvZ3kgY2hhbmdlDQo+PiBhY3Jvc3MgYSBWUExT
IGluc3RhbmNlIGFwcGVhcnMgdG8gYmUgd2VsbCBhZHZhbmNlZC4gVGhhdCBpdCBjYW4gYmUgIA0K
Pj4gdXNlZA0KPj4gYXMgYW4gYWdncmVnYXRlZCBNQUMgd2l0aGRyYXcgZm9yIFBCQk5zIHNlZW1z
IGNvbnNpc3RlbnQgd2l0aCB3aGVyZSAgDQo+PiBQV0UNCj4+IGlzIGFscmVhZHkgZ29pbmcuIFRo
YXQgaXQgY2FuIHN0dW50IGRvdWJsZSBmb3IgYSB0b3BvbG9neSBjaGFuZ2UgIA0KPj4gQlBEVSBJ
DQo+PiBkbyBub3QgdGhpbmsgaXMgYSBzdHJldGNoIGFzIHRoYXQgaXMgZXhhY3RseSB3aGF0IGl0
IGlzDQo+PiBjb21tdW5pY2F0aW5nLi4uLg0KPj4NCj4+IDIpIE11bHRpY2FzdCBNQUMgZmlsdGVy
aW5nIGF0IHRoZSBpbmdyZXNzIHRvIGEgYnJvYWRjYXN0IGRvbWFpbiAgDQo+PiBkb2VzIG5vdA0K
Pj4gaW52b2x2ZSBtb2RpZmljYXRpb25zIHRvIElFRUUgcmVnaXN0cmF0aW9uIHByb3RvY29scyBp
biBteSAgDQo+PiBwcm9wb3NhbCwgb3INCj4+IGlzIHN0YXRpY2FsbHkgcHJvdmlzaW9uZWQgKGFz
IGluIEFsaSdzIHByb3Bvc2FsKSxhbmQgYXQgbGVhc3QgdGhhdCAgDQo+PiBwYXJ0DQo+PiBpcyBl
eGNsdXNpdmUgdG8gdGhlIGJyaWRnZSBtb2R1bGUgc28gZG9lcyBub3Qgc2VlbSB0byB1bmRlcm1p
bmUgeW91cg0KPj4gY29uY2VybnMuDQo+Pg0KPj4gRG9lcyBteSBhbmFseXNpcyBhbGlnbiB3aXRo
IHlvdXJzPw0KPg0KPiBObywgaXQgZG9lcyBub3QuDQo+DQo+IExldCdzIGJyaW5nIHRoaXMgYmFj
ayB1cCBhIGxldmVsIGFuZCBhdHRlbXB0IHRvIGFwcGx5IGEgbXVjaCBzaW1wbGVyICANCj4gImxp
dG11cyB0ZXN0Ii4gIFNwZWNpZmljYWxseSwgd2hhdCBpZiBWUExTIHdlcmUgbmV2ZXIgaW52ZW50
ZWQgb3IgIA0KPiBzaW1wbHkgZGlkIG5vdCBleGlzdD8gIEFsdGVybmF0aXZlbHksIGFuZCBtb3Jl
IHByYWN0aWNhbGx5LCB3aGF0IGlzICANCj4gZG9uZSB3aGVuIFZQTFMgZG9lcyBub3QgZXhpc3Qg
aW4gY2VydGFpbiB0b3BvbG9naWVzL2RlcGxveW1lbnRzPyAgSW4gIA0KPiB0aGF0IGNhc2UsIHRo
ZSBJRUVFIHdvdWxkIGVpdGhlciBoYXZlIGEgKHNjYWxhYmxlKSBzb2x1dGlvbiB0aGF0IHlvdSAg
DQo+IGFyZSBsb29raW5nIGZvciBvciBwZW9wbGUgd291bGQgZ28gdG8gdGhlIElFRUUgYW5kIGtp
Y2stb2ZmIGFuICANCj4gZWZmb3J0IHRvIGNyZWF0ZSBzdWNoIGEgc29sdXRpb24sIGNvcnJlY3Q/
DQo+DQo+IFdoZW4gdmlld2VkIGF0IGZyb20gdGhhdCBwZXJzcGVjdGl2ZSwgaXQgc2hvdWxkIGhv
cGVmdWxseSBiZSBjbGVhciAgDQo+IHRoYXQgc29sdXRpb25zIHRvIHRoaXMgc3BlY2lmaWMgcHJv
YmxlbSBzaG91bGQgYmVsb25nIGluIHRoZSBOU1AvIA0KPiBCcmlkZ2UgTW9kdWxlIGFuZCwgdGhl
cmVmb3JlLCBhcmUgb3V0IG9mIHRoZSBoYW5kcyBvZiB0aGUgTDJWUE4gV0cuICAgDQo+IChGdXJ0
aGVybW9yZSwgaWYgZm9sa3Mgd2FudCB0byBpbXBsZW1lbnQgc2FpZCBzb2x1dGlvbnMsIHRoZXkg
c2hvdWxkICANCj4gZ28gcmVhZCB0aGUgZnVsbCBJRUVFIHNwZWMgdG8gZG8gc28gYW5kIHdlIHNo
b3VsZCBub3QgZHVwbGljYXRlIG9yICANCj4gb3RoZXJ3aXNlIHJlLXB1Ymxpc2ggaXQgd2l0aGlu
IHRoZSBMMlZQTiBXRykuDQo+DQo+IEFsc28sIHRvIGJyaW5nIHRoaXMgYmFjayB0byB0aGUgY29u
dGV4dCBvZiBWUExTIEFyY2hpdGVjdHVyZSwgeW91ICANCj4gZGlkIHNheSB0aGUgZm9sbG93aW5n
Og0KPiAtLS1zbmlwLS0tDQo+PiAyKSBJbiB0aGUgY2FzZSBvZiBNTVJQIGlmIHRoZSBQVyBpcyBw
cmVzZW50ZWQgYXMgYW4gaW50ZXJmYWNlIHRvIGENCj4+IGJyaWRnZSBtb2R1bGUuLi4NCj4gLS0t
c25pcC0tLQ0KPiBDdXJyZW50bHksIGEgVlBMUyBpbnN0YW5jZSBvbiBhIFZQTFMtUEUgaXMgZGVm
aW5lZCAoYXQgbGVhc3QgZnJvbSBhICANCj4gdGhlb3JldGljYWwgc3RhbmRwb2ludCkgYXMgaGF2
aW5nIGEgc2luZ2xlIExBTiBlbXVsYXRpb24gaW50ZXJmYWNlICANCj4gYmV0d2VlbiB0aGUgQnJp
ZGdlIE1vZHVsZSBhbmQgdGhlIFZQTFMgRm9yd2FyZGVyLCB3aGljaCBsaWtlbHkgIA0KPiBwcmV2
ZW50cyBvbmUgZnJvbSBhcHBseWluZyBJRUVFIGZpbHRlcmluZy9mb3J3YXJkaW5nIENvbnRyb2wg
IA0KPiBQcm90b2NvbHMgYWdhaW5zdCBhbiBpbmRpdmlkdWFsIFBXLCBzdWNoIGFzIHdoYXQgeW91
J3JlIGF0dGVtcHRpbmcgIA0KPiB0byBkZWZpbmUgaW4gZHJhZnQtYWxsYW4tbXJycCAoYXMgYW4g
ZXhhbXBsZSkuICBBZ2FpbiwgdGhlIGxhcmdlciAgDQo+IHF1ZXN0aW9uIHRoYXQgc2hvdWxkIGJl
IGJlaW5nIGFza2VkIGlzOiBkbyB3ZSBoYXZlIGEgYnJva2VuICANCj4gYXJjaGl0ZWN0dXJlIGFu
ZCBuZWVkIHRvIGNvbnNpZGVyIGZpeGluZyBpdCB0byBhbGxvdyBpdCB0byBtb3JlICANCj4gYWNj
dXJhdGVseSAoYnV0LCBub3QgcGVyZmVjdGx5KSAiZW11bGF0ZSIgYSBJRUVFIExBTj8NCg0KSSBz
aG91bGQgaGF2ZSBhZGRlZCBvbiB0byB0aGUgbGFzdCBzZW50ZW5jZSB0aGUgZm9sbG93aW5nOiAi
IC4uLiBieSwgIA0KcGVyaGFwcywgY29uc2lkZXJpbmcgYW4gYXJjaGl0ZWN0dXJhbCBjaGFuZ2Ug
dG8gVlBMUyBzdWNoIGFzIGV4cG9zaW5nICANCmluZGl2aWR1YWwgUFcncyB0byB0aGUgQnJpZGdl
IE1vZHVsZSIuDQoNCi1zaGFuZQ0K

------_=_NextPart_001_01C8EFC4.C015BD92
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTMuMzAiPg0KPFRJVExFPlJlOiBWUExTIEFy
Y2hpdGVjdHVyZTwvVElUTEU+DQo8L0hFQUQ+DQo8Qk9EWT4NCjwhLS0gQ29udmVydGVkIGZyb20g
dGV4dC9wbGFpbiBmb3JtYXQgLS0+DQoNCjxQPjxGT05UIFNJWkU9Mj5IaSBzaGFuZTxCUj4NCjxC
Uj4NCk9LIEkgZ2V0IHRoZSBtb2RlbCBhbmQgdGhlIGltcGxpY2F0aW9ucy4gTGV0J3MgZm9sbG93
IHVwIGluIER1YmxpbjxCUj4NCjxCUj4NCkQ8QlI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LTxCUj4NClRodW1iIHR5cGVkIGJ5IERhdmUgQWxsYW4sIE5vcnRlbDxCUj4NCjxCUj4NCjxCUj4N
Ci0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS08QlI+DQpGcm9tOiBTaGFuZSBBbWFudGUgJmx0
O3NoYW5lQGNhc3RsZXBvaW50Lm5ldCZndDs8QlI+DQpUbzogQWxsYW4sIERhdmlkIChDQVI6TlMw
MCk8QlI+DQpDYzogbDJ2cG5AaWV0Zi5vcmcgJmx0O2wydnBuQGlldGYub3JnJmd0OzxCUj4NClNl
bnQ6IFNhdCBKdWwgMjYgMTI6Mzg6MDIgMjAwODxCUj4NClN1YmplY3Q6IFJlOiBWUExTIEFyY2hp
dGVjdHVyZTxCUj4NCjxCUj4NCk9uZSBmb2xsb3ctdXAgdG8gbXkgb3duIG1lc3NhZ2UsIGp1c3Qg
dG8gbWFrZSBzdXJlIEknbSBtb3JlIGNsZWFyIC4uLjxCUj4NCjxCUj4NCk9uIEp1bCAyNiwgMjAw
OCwgYXQgMTA6MTYgQU0sIFNoYW5lIEFtYW50ZSB3cm90ZTo8QlI+DQo8QlI+DQomZ3Q7IERhdmUs
PEJSPg0KJmd0OzxCUj4NCiZndDsgT24gSnVsIDI1LCAyMDA4LCBhdCAzOjI4IEFNLCBEYXZpZCBB
bGxhbiB3cm90ZTo8QlI+DQomZ3Q7Jmd0OyBISSBTaGFuZTogSSdtIHRyeWluZyB0byB1bmRlcnN0
YW5kIHRoaXMgaW4gdGhlIGNvbnRleHQgb2Y8QlI+DQomZ3Q7Jmd0OyBkcmFmdC1hbGxhbi1tbXJw
Li4uIEFuZCBvdGhlciBwcm9wb3NhbHMuLi4uPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBX
aGF0IEkgZ2V0IG91dCBvZiB0aGlzIHJhaXNlcyBhIG51bWJlciBvZiBwb2ludHMgb2YgaW50ZXJl
c3QuLi4uPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyAxKSBObyBpbnRlcmFjdGlvbiB3aXRo
IEwyIHByb3RvY29scyBpbiB0aGVvcnkgdGFrZXMgYWxsIHBvc3NpYmlsaXR5Jm5ic3A7PEJSPg0K
Jmd0OyZndDsgb2Y8QlI+DQomZ3Q7Jmd0OyByZXNpbGllbnQgYWNjZXNzIG9mZiB0aGUgdGFibGUg
ZXhjZXB0IGFzIGEgcHVyZSBvdmVybGF5IG92ZXIgdG90YWxseTxCUj4NCiZndDsmZ3Q7IHN0YXRp
YyBhbmQgdW5maWx0ZXJlZCBWUExTIGluc3RhbmNlKHMpLiBTb21lIGludGVyYWN0aW9uIGlzJm5i
c3A7PEJSPg0KJmd0OyZndDsgcmVxdWlyZWQgdG88QlI+DQomZ3Q7Jmd0OyBlbnN1cmUgVlBMUyBp
cyBub3QgY3JlYXRpbmcgYSBsb29wIGlmIGl0IGhhcyBtb3JlIHRoYW4gb25lIHBvaW50IG9mPEJS
Pg0KJmd0OyZndDsgYXR0YWNobWVudCB0byBhIGJyb2FkY2FzdCBkb21haW4uIEhvd2V2ZXIgaWYg
dGhhdCBpbnRlcmFjdGlvbiBpcyZuYnNwOzxCUj4NCiZndDsmZ3Q7IG9mZiB0aGU8QlI+DQomZ3Q7
Jmd0OyB0YWJsZSB0aGVuIChmb3IgZXhhbXBsZSkgcHJlZmVycmVkIGZvcndhcmRpbmcgd2hpY2gg
aW1wbGllcyZuYnNwOzxCUj4NCiZndDsmZ3Q7IGludGVyYWN0aW9uPEJSPg0KJmd0OyZndDsgd2l0
aCBwZWVyIG5ldHdvcmtzIHByb3RvY29scyBzdWNoIGFzIExBQ1AsIGlzIGEgcGllY2Ugb2Ygd29y
ayB0aGF0PEJSPg0KJmd0OyZndDsgc2hvdWxkIGJlIGFiYW5kb25lZCBieSB0aGlzIGNyaXRlcmlh
Li4uPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBNQUMgd2l0aGRyYXcgaXMgZWZmZWN0aXZl
bHkgaW50ZXJhY3Rpb24gd2l0aCBJRUVFIGNvbnRyb2wgcHJvdG9jb2xzJm5ic3A7PEJSPg0KJmd0
OyZndDsgb2Y8QlI+DQomZ3Q7Jmd0OyBzb21lIGZvcm0gc2ltaWxhciB0byAxLiBUb3BvbG9neSBj
aGFuZ2UgQlBEVXMgdHJhbnNwYXJlbnRseSBwYXNzZWQmbmJzcDs8QlI+DQomZ3Q7Jmd0OyBvdmVy
PEJSPg0KJmd0OyZndDsgUFdzIGJldHdlZW4gYnJpZGdlIG1vZHVsZXMgd291bGQgYXBwZWFyIHRv
IGJlIHRoZSBvbmx5IGFjY2VwdGFibGU8QlI+DQomZ3Q7Jmd0OyBhcHByb2FjaCBieSB0aGlzIGNy
aXRlcmlhLi4uPEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBXaGljaCBhY3R1YWxseSB3b3Vs
ZCB3b3JrIGp1c3QgZmluZSBhcyBmYXIgYXMgZHJhZnQgYWxsYW4gaXM8QlI+DQomZ3Q7Jmd0OyBj
b25jZXJuZWQuLi4gQnV0IGZvciB0aGUgY2FzZSB3aGVyZSBBTEwgYnJpZGdlIG1vZHVsZXMgZG8g
bm90IGhhdmUmbmJzcDs8QlI+DQomZ3Q7Jmd0OyBTVFA8QlI+DQomZ3Q7Jmd0OyBlbmFibGVkLCBw
cmVmZXJyZWQgZm9yd2FyZGluZyBuZWVkcyB0byBzdHVudCBkb3VibGUuLi48QlI+DQomZ3Q7Jmd0
OzxCUj4NCiZndDsmZ3Q7IDIpIEluIHRoZSBjYXNlIG9mIE1NUlAgaWYgdGhlIFBXIGlzIHByZXNl
bnRlZCBhcyBhbiBpbnRlcmZhY2UgdG8gYTxCUj4NCiZndDsmZ3Q7IGJyaWRnZSBtb2R1bGUuLi5J
IGRvIG5vdCB0aGluayB0aGVyZSBpcyBhIGNvbmZsaWN0LiBJdCBpcyBmaWx0ZXJpbmc8QlI+DQom
Z3Q7Jmd0OyBwcm9ncmFtbWVkIHByaW9yIHRvIFBXIGluZ3Jlc3MgYnkgSUVFRSByZWdpc3RyYXRp
b24gcHJvdG9jb2xzIGZvciB0aGU8QlI+DQomZ3Q7Jmd0OyBwdXJwb3NlIG9mIG11bHRpY2FzdCBw
cnVuaW5nIGluIGEgc2luZ2xlIGJyb2FkY2FzdCBkb21haW4uJm5ic3A7PEJSPg0KJmd0OyZndDsg
UmVnaXN0cmF0aW9uPEJSPg0KJmd0OyZndDsgb2YgZmlsdGVyaW5nIG5lZWRzIHRvIGJlIHRpZWQg
dG8gdG9wb2xvZ3kgY2hhbmdlIGJlaW5nIHdoYXQgSSB0aGluayZuYnNwOzxCUj4NCiZndDsmZ3Q7
IGlzPEJSPg0KJmd0OyZndDsgYm90aCB5b3VyIGludGVyZXN0IGFuZCBjb25jZXJuLi4uLjxCUj4N
CiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsgQnV0IGlmIEkgd2VyZSB0byBiYWNrIHRoaXMgdXAgdG8g
d2hlcmUgZWZmb3J0cyBhcHBlYXIgdG8gYmUgZ29pbmcuLi4uPEJSPg0KJmd0OyZndDs8QlI+DQom
Z3Q7Jmd0OyAxKSBwcmVmZXJyZWQgZm9yd2FyZGluZyBhcyBhIG1lYW5zIG9mIHNlbWFwaG9yaW5n
IGEgdG9wb2xvZ3kgY2hhbmdlPEJSPg0KJmd0OyZndDsgYWNyb3NzIGEgVlBMUyBpbnN0YW5jZSBh
cHBlYXJzIHRvIGJlIHdlbGwgYWR2YW5jZWQuIFRoYXQgaXQgY2FuIGJlJm5ic3A7PEJSPg0KJmd0
OyZndDsgdXNlZDxCUj4NCiZndDsmZ3Q7IGFzIGFuIGFnZ3JlZ2F0ZWQgTUFDIHdpdGhkcmF3IGZv
ciBQQkJOcyBzZWVtcyBjb25zaXN0ZW50IHdpdGggd2hlcmUmbmJzcDs8QlI+DQomZ3Q7Jmd0OyBQ
V0U8QlI+DQomZ3Q7Jmd0OyBpcyBhbHJlYWR5IGdvaW5nLiBUaGF0IGl0IGNhbiBzdHVudCBkb3Vi
bGUgZm9yIGEgdG9wb2xvZ3kgY2hhbmdlJm5ic3A7PEJSPg0KJmd0OyZndDsgQlBEVSBJPEJSPg0K
Jmd0OyZndDsgZG8gbm90IHRoaW5rIGlzIGEgc3RyZXRjaCBhcyB0aGF0IGlzIGV4YWN0bHkgd2hh
dCBpdCBpczxCUj4NCiZndDsmZ3Q7IGNvbW11bmljYXRpbmcuLi4uPEJSPg0KJmd0OyZndDs8QlI+
DQomZ3Q7Jmd0OyAyKSBNdWx0aWNhc3QgTUFDIGZpbHRlcmluZyBhdCB0aGUgaW5ncmVzcyB0byBh
IGJyb2FkY2FzdCBkb21haW4mbmJzcDs8QlI+DQomZ3Q7Jmd0OyBkb2VzIG5vdDxCUj4NCiZndDsm
Z3Q7IGludm9sdmUgbW9kaWZpY2F0aW9ucyB0byBJRUVFIHJlZ2lzdHJhdGlvbiBwcm90b2NvbHMg
aW4gbXkmbmJzcDs8QlI+DQomZ3Q7Jmd0OyBwcm9wb3NhbCwgb3I8QlI+DQomZ3Q7Jmd0OyBpcyBz
dGF0aWNhbGx5IHByb3Zpc2lvbmVkIChhcyBpbiBBbGkncyBwcm9wb3NhbCksYW5kIGF0IGxlYXN0
IHRoYXQmbmJzcDs8QlI+DQomZ3Q7Jmd0OyBwYXJ0PEJSPg0KJmd0OyZndDsgaXMgZXhjbHVzaXZl
IHRvIHRoZSBicmlkZ2UgbW9kdWxlIHNvIGRvZXMgbm90IHNlZW0gdG8gdW5kZXJtaW5lIHlvdXI8
QlI+DQomZ3Q7Jmd0OyBjb25jZXJucy48QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IERvZXMg
bXkgYW5hbHlzaXMgYWxpZ24gd2l0aCB5b3Vycz88QlI+DQomZ3Q7PEJSPg0KJmd0OyBObywgaXQg
ZG9lcyBub3QuPEJSPg0KJmd0OzxCUj4NCiZndDsgTGV0J3MgYnJpbmcgdGhpcyBiYWNrIHVwIGEg
bGV2ZWwgYW5kIGF0dGVtcHQgdG8gYXBwbHkgYSBtdWNoIHNpbXBsZXImbmJzcDs8QlI+DQomZ3Q7
ICZxdW90O2xpdG11cyB0ZXN0JnF1b3Q7LiZuYnNwOyBTcGVjaWZpY2FsbHksIHdoYXQgaWYgVlBM
UyB3ZXJlIG5ldmVyIGludmVudGVkIG9yJm5ic3A7PEJSPg0KJmd0OyBzaW1wbHkgZGlkIG5vdCBl
eGlzdD8mbmJzcDsgQWx0ZXJuYXRpdmVseSwgYW5kIG1vcmUgcHJhY3RpY2FsbHksIHdoYXQgaXMm
bmJzcDs8QlI+DQomZ3Q7IGRvbmUgd2hlbiBWUExTIGRvZXMgbm90IGV4aXN0IGluIGNlcnRhaW4g
dG9wb2xvZ2llcy9kZXBsb3ltZW50cz8mbmJzcDsgSW4mbmJzcDs8QlI+DQomZ3Q7IHRoYXQgY2Fz
ZSwgdGhlIElFRUUgd291bGQgZWl0aGVyIGhhdmUgYSAoc2NhbGFibGUpIHNvbHV0aW9uIHRoYXQg
eW91Jm5ic3A7PEJSPg0KJmd0OyBhcmUgbG9va2luZyBmb3Igb3IgcGVvcGxlIHdvdWxkIGdvIHRv
IHRoZSBJRUVFIGFuZCBraWNrLW9mZiBhbiZuYnNwOzxCUj4NCiZndDsgZWZmb3J0IHRvIGNyZWF0
ZSBzdWNoIGEgc29sdXRpb24sIGNvcnJlY3Q/PEJSPg0KJmd0OzxCUj4NCiZndDsgV2hlbiB2aWV3
ZWQgYXQgZnJvbSB0aGF0IHBlcnNwZWN0aXZlLCBpdCBzaG91bGQgaG9wZWZ1bGx5IGJlIGNsZWFy
Jm5ic3A7PEJSPg0KJmd0OyB0aGF0IHNvbHV0aW9ucyB0byB0aGlzIHNwZWNpZmljIHByb2JsZW0g
c2hvdWxkIGJlbG9uZyBpbiB0aGUgTlNQLzxCUj4NCiZndDsgQnJpZGdlIE1vZHVsZSBhbmQsIHRo
ZXJlZm9yZSwgYXJlIG91dCBvZiB0aGUgaGFuZHMgb2YgdGhlIEwyVlBOIFdHLiZuYnNwOyZuYnNw
OzxCUj4NCiZndDsgKEZ1cnRoZXJtb3JlLCBpZiBmb2xrcyB3YW50IHRvIGltcGxlbWVudCBzYWlk
IHNvbHV0aW9ucywgdGhleSBzaG91bGQmbmJzcDs8QlI+DQomZ3Q7IGdvIHJlYWQgdGhlIGZ1bGwg
SUVFRSBzcGVjIHRvIGRvIHNvIGFuZCB3ZSBzaG91bGQgbm90IGR1cGxpY2F0ZSBvciZuYnNwOzxC
Uj4NCiZndDsgb3RoZXJ3aXNlIHJlLXB1Ymxpc2ggaXQgd2l0aGluIHRoZSBMMlZQTiBXRykuPEJS
Pg0KJmd0OzxCUj4NCiZndDsgQWxzbywgdG8gYnJpbmcgdGhpcyBiYWNrIHRvIHRoZSBjb250ZXh0
IG9mIFZQTFMgQXJjaGl0ZWN0dXJlLCB5b3UmbmJzcDs8QlI+DQomZ3Q7IGRpZCBzYXkgdGhlIGZv
bGxvd2luZzo8QlI+DQomZ3Q7IC0tLXNuaXAtLS08QlI+DQomZ3Q7Jmd0OyAyKSBJbiB0aGUgY2Fz
ZSBvZiBNTVJQIGlmIHRoZSBQVyBpcyBwcmVzZW50ZWQgYXMgYW4gaW50ZXJmYWNlIHRvIGE8QlI+
DQomZ3Q7Jmd0OyBicmlkZ2UgbW9kdWxlLi4uPEJSPg0KJmd0OyAtLS1zbmlwLS0tPEJSPg0KJmd0
OyBDdXJyZW50bHksIGEgVlBMUyBpbnN0YW5jZSBvbiBhIFZQTFMtUEUgaXMgZGVmaW5lZCAoYXQg
bGVhc3QgZnJvbSBhJm5ic3A7PEJSPg0KJmd0OyB0aGVvcmV0aWNhbCBzdGFuZHBvaW50KSBhcyBo
YXZpbmcgYSBzaW5nbGUgTEFOIGVtdWxhdGlvbiBpbnRlcmZhY2UmbmJzcDs8QlI+DQomZ3Q7IGJl
dHdlZW4gdGhlIEJyaWRnZSBNb2R1bGUgYW5kIHRoZSBWUExTIEZvcndhcmRlciwgd2hpY2ggbGlr
ZWx5Jm5ic3A7PEJSPg0KJmd0OyBwcmV2ZW50cyBvbmUgZnJvbSBhcHBseWluZyBJRUVFIGZpbHRl
cmluZy9mb3J3YXJkaW5nIENvbnRyb2wmbmJzcDs8QlI+DQomZ3Q7IFByb3RvY29scyBhZ2FpbnN0
IGFuIGluZGl2aWR1YWwgUFcsIHN1Y2ggYXMgd2hhdCB5b3UncmUgYXR0ZW1wdGluZyZuYnNwOzxC
Uj4NCiZndDsgdG8gZGVmaW5lIGluIGRyYWZ0LWFsbGFuLW1ycnAgKGFzIGFuIGV4YW1wbGUpLiZu
YnNwOyBBZ2FpbiwgdGhlIGxhcmdlciZuYnNwOzxCUj4NCiZndDsgcXVlc3Rpb24gdGhhdCBzaG91
bGQgYmUgYmVpbmcgYXNrZWQgaXM6IGRvIHdlIGhhdmUgYSBicm9rZW4mbmJzcDs8QlI+DQomZ3Q7
IGFyY2hpdGVjdHVyZSBhbmQgbmVlZCB0byBjb25zaWRlciBmaXhpbmcgaXQgdG8gYWxsb3cgaXQg
dG8gbW9yZSZuYnNwOzxCUj4NCiZndDsgYWNjdXJhdGVseSAoYnV0LCBub3QgcGVyZmVjdGx5KSAm
cXVvdDtlbXVsYXRlJnF1b3Q7IGEgSUVFRSBMQU4/PEJSPg0KPEJSPg0KSSBzaG91bGQgaGF2ZSBh
ZGRlZCBvbiB0byB0aGUgbGFzdCBzZW50ZW5jZSB0aGUgZm9sbG93aW5nOiAmcXVvdDsgLi4uIGJ5
LCZuYnNwOzxCUj4NCnBlcmhhcHMsIGNvbnNpZGVyaW5nIGFuIGFyY2hpdGVjdHVyYWwgY2hhbmdl
IHRvIFZQTFMgc3VjaCBhcyBleHBvc2luZyZuYnNwOzxCUj4NCmluZGl2aWR1YWwgUFcncyB0byB0
aGUgQnJpZGdlIE1vZHVsZSZxdW90Oy48QlI+DQo8QlI+DQotc2hhbmU8QlI+DQo8L0ZPTlQ+DQo8
L1A+DQoNCjwvQk9EWT4NCjwvSFRNTD4=

------_=_NextPart_001_01C8EFC4.C015BD92--


From l2vpn-bounces@ietf.org  Sun Jul 27 10:36:09 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68A793A680A;
	Sun, 27 Jul 2008 10:36:09 -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 ED9AD3A680A
	for <l2vpn@core3.amsl.com>; Sun, 27 Jul 2008 10:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 vXmXNm4KuZwQ for <l2vpn@core3.amsl.com>;
	Sun, 27 Jul 2008 10:36:07 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 144D23A6806
	for <l2vpn@ietf.org>; Sun, 27 Jul 2008 10:36:07 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 8348A268675; Sun, 27 Jul 2008 11:36:14 -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; Sun, 27 Jul 2008 11:36:14 -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=35247; data-bytes=0
Message-ID: <488CB20D.3040607@castlepoint.net>
Date: Sun, 27 Jul 2008 11:36:13 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Subject: Re: VPLS Architecture
References: <4888C10E.7040602@castlepoint.net>
	<483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Ali,

I'm going to break this response up into two parts.  In this thread, I 
continue on the points related to the architecture of VPLS.

Ali Sajassi (sajassi) wrote:

[--snip--]

> "raw" and "tagged" modes were debated many times since the genesis of
> PWE3 and the WG decided on using them as specified and we got not RFC in
> both PWE3 and L2VPN regarding their applications. Are you suggesting
> that we start from square one again ??

Ultimately, since we're talking about the need to support a new IEEE 
data-plane format, it appears that debate has (already) been re-opened.

I'm hopeful that starting from "square one" will be unnecessary, so long 
as the chosen solution provides *both* backward compatibility with the 
two, previous PW types (raw and tagged) as well as much more flexibility 
for incorporating "new" data plane formats.


[--snip--]

> Also, I think a point may be getting missed here with respect to L2VPN
> services using these PWs. The type of the PW frankly is not as important
> as having the two sides agree on exchanging the same packet format and
> agree on the interpretation of such format; whether that is done
> explicitly or implicitly (via PW type) is a small point. The precedence
> for last seven years has been explicit indication via PW type (e.g., raw
> mode versus tagged mode).    

Actually, I think this is the key point of this entire conversation and 
must not be lightly dismissed.  Specifically, explicit signaling of the 
PW type creates a variety of headaches with respect to interoperability 
of data-plane protocols carried by the PW's, as well as inability to 
easily adapt to emerging/new data-plane formats.

Furthermore, why is the onus on VPLS (or PWE3) to provide interworking 
of IEEE data-plane formats?  Isn't that a function of the IEEE and the 
Bridge Module?


[--snip--]

> There are pros/cons for this where we can discuss in the PWE3 or L2VPN
> sessions but frankly I don't think of this explicit v.s. implicit PW
> type indication as a significant one which deserves such attention and
> being made center piece of "VPLS architecture".  

I disagree.  See above.


[--snip--]

> The nature of service being offered in VPLS (e.g., qualified v.s.
> non-qualifed modes) affect the interaction with some of these bridging
> protocols which needs to be captured. If there was no affect, I would
> have agreed with you but if there is an impact then we need to at least
> specify what we expect from this magic box (bridge module). Regarding
> how it is done, it can simply be referred to IEEE spec. 

Actually, this is another very key point and I'm glad you brought it up, 
because it again goes directly to the heart of the discussion around the 
architecture of VPLS.

Again, as I stated in my originally e-mail, I submit that if there is an 
impact on the Bridging Module, which requires new specifications on our 
part, then we haven't properly designed the Bridge Module function and 
need to re-visit that to provide better "emulation" of Ethernet.


> Remember that
> VPLS (as a service) is defined among a set of Attachment Circuits !!

Right, and that's it!  We SHOULD NOT be defining functions within the 
Bridge Module, including interaction, adaptation or interworking of IEEE 
protocols, since that is the IEEE's bailiwick.



[--snip--]

> I think we first need to decide whether we are going to rehash all the
> PW type discussion all over again and change the application of existing
> "raw" and "tagged" mode as being defined in both PWE3 and L2VPN RFCs. 

See above.

-shane


From l2vpn-bounces@ietf.org  Sun Jul 27 23:43:24 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67FB228C174;
	Sun, 27 Jul 2008 23:43:24 -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 3F79328C174
	for <l2vpn@core3.amsl.com>; Sun, 27 Jul 2008 23:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 DvWLVoEghrsC for <l2vpn@core3.amsl.com>;
	Sun, 27 Jul 2008 23:43:22 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 7E44828C16D
	for <l2vpn@ietf.org>; Sun, 27 Jul 2008 23:43:22 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 76FA9268675; Mon, 28 Jul 2008 00:43:31 -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;
	Mon, 28 Jul 2008 00:43:31 -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=35372; data-bytes=0
Message-ID: <488D6A92.6010907@castlepoint.net>
Date: Mon, 28 Jul 2008 00:43:30 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: l2vpn@ietf.org
Subject: Re: IETF 72: Draft Agenda Posted
References: <52D1DED1-549C-4314-B73B-D0E9CACCB62A@castlepoint.net>
In-Reply-To: <52D1DED1-549C-4314-B73B-D0E9CACCB62A@castlepoint.net>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

FYI.  I've only received 2 of the 8 presentations, so far.  Thanks Yuji 
& Jiang.  The rest of you: please send your slides ASAP, or risk losing 
your slot.

-shane


Shane Amante wrote:
> The draft agenda can be found here: 
> http://www.ietf.org/proceedings/08jul/agenda/l2vpn.txt
> 
> Please let the chairs know if we've missed any requests.
> 
> Since our meeting is Monday afternoon, we kindly request that all 
> presenters send us their slides no later than Sunday evening so they may 
> be posted to the Meeting Materials Web site, prior to the start of the 
> WG meeting.
> 
> -shane



From l2vpn-bounces@ietf.org  Mon Jul 28 00:36:29 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99F7C3A6880;
	Mon, 28 Jul 2008 00:36:29 -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 978A53A6989
	for <l2vpn@core3.amsl.com>; Mon, 28 Jul 2008 00:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5
	tests=[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 QyXmQHjjCM+8 for <l2vpn@core3.amsl.com>;
	Mon, 28 Jul 2008 00:36:27 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id B6B273A67FD
	for <l2vpn@ietf.org>; Mon, 28 Jul 2008 00:36:27 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id DF652268675; Mon, 28 Jul 2008 01:36:36 -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; Mon, 28 Jul 2008 01:36:36 -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=60831; data-bytes=0
Message-ID: <488D7701.9080600@castlepoint.net>
Date: Mon, 28 Jul 2008 01:36:33 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Subject: Re: VPLS Architecture
References: <4888C10E.7040602@castlepoint.net>
	<483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Ali,

This is second part of the earlier response.  See below.

Ali Sajassi (sajassi) wrote:
>  
> Shane,
> 
>> -----Original Message-----
>> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] 
>> On Behalf Of Shane Amante
>> Sent: Thursday, July 24, 2008 10:51 AM
>> To: l2vpn@ietf.org
>> Subject: VPLS Architecture
>>
>> Recently, a significant number of drafts have been submitted, 
>> and discussed, to address incorporating 802.1ag, 802.1ah and 
>> other IEEE/ITU protocols within the VPLS Architecture.  These 
>> drafts appear to largely
>> be: a) a re-specification of how IEEE protocols work over top 
>> of a VPLS; or, b) how IEEE protocols inter-work with other 
>> IEEE data-plane formats within a VPLS (or PWE3's).  In 
>> addition, for completeness, there is a question which L2VPN 
>> hasn't addressed: the potential for inter-working Native 
>> Service Layer control protocols from the IEEE/ITU with those 
>> created and maintained by L2VPN.
>>
> 
> Can you be more precise on which drafts you are talking about. It is
> hard to formulate a response to your comments without knowing what
> drafts you mean specifically. 

The one I'm most concerned with is:
draft-mohan-l2vpn-vpls-oam-01

And, to a large extent the following, as well:
draft-sajassi-l2vpn-pbb-vpls-cmac-flush-00
draft-sajassi-l2vpn-pbb-vpls-mpls-access-00
draft-sajassi-l2vpn-pbb-vpls-multicast-00
draft-sajassi-l2vpn-vpls-pbb-interop-03
draft-balus-l2vpn-vpls-802.1ah-03
Although, to be fair, this latter group is IMO more likely a consequence 
of the current architecture of VPLS.  So, for this group in particular, 
I would prefer if we focus instead on discussing what might be 
limitations with the architecture of VPLS and what might be done to fix 
it in order that we reduce the volume of drafts in order to support a 
new IEEE data-plane.

In addition, you do realize that the sum total of draft-sajassi* & 
draft-balus* is currently at 87 pages.  However, RFC 4762 is a mere 29 
pages?  IMO, the reason for the volume of pages is detailed descriptions 
of interworking (or, "interoperability scenarios") of IEEE data-plane 
technologies, which should be found in IEEE documents, not in IETF drafts.



>> With respect to the first question (re-specification of other 
>> SDO's protocols), there are a significant number of concerns. 
>>  Specifically, when protocols from another SDO are 
>> re-specified within the IETF, there is the potential for 
>> errors or omissions to be introduced.  In general, there is 
>> likely to be insufficient expertise widely available within 
>> the IETF to review those drafts, in-depth, for accuracy or 
>> "faithfulness" to the original SDO's standard as they 
>> progress through the IETF standards process.  Finally, there 
>> is always the [unanswered] question of what SDO's document is 
>> considered authoritative in case a conflict, error or 
>> omission develops.  In summary, there is both little value 
>> and significant risk in widespread re-publication of IEEE/ITU 
>> specifications within the L2VPN WG.  In a well written draft, 
>> Normative References to another SDO's detailed architecture, 
>> protocol or technology documents should be more than 
>> adequate, and seems to have worked well, so far, particularly 
>> in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761] 
>> to cite just two examples.
>>
> 
> I concur. There should be no reason for the re-specification of IEEE
> drafts for many reasons some of which you have mentioned above.

I'm glad you agree.


> As the
> matter of fact in my pbb-interop draft, I put a short primer on PBB in
> the Appendix for just this purpose so that any re-specification be
> avoided in the main body of the draft. And I was told by many people
> that this one page primer was very helpful to them.

-shane


From l2vpn-bounces@ietf.org  Mon Jul 28 06:07:41 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9593F3A691C;
	Mon, 28 Jul 2008 06:07:41 -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 A85FC3A69DF
	for <l2vpn@core3.amsl.com>; Mon, 28 Jul 2008 06:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 b-B4qfxEta2U for <l2vpn@core3.amsl.com>;
	Mon, 28 Jul 2008 06:07:36 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 2AB8F3A6813
	for <l2vpn@ietf.org>; Mon, 28 Jul 2008 06:07:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,265,1215388800"; d="scan'208";a="69592260"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 28 Jul 2008 13:07:46 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m6SD7jeR003460; 
	Mon, 28 Jul 2008 06:07:45 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m6SD7jTp026535;
	Mon, 28 Jul 2008 13:07:45 GMT
Received: from xmb-sjc-239.amer.cisco.com ([128.107.191.105]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 28 Jul 2008 06:07:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Mon, 28 Jul 2008 06:07:42 -0700
Message-ID: <483F121CD2155B43B56DB71228DBAF1501F352AD@xmb-sjc-239.amer.cisco.com>
In-Reply-To: <488D7701.9080600@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjwhK5toaAvc3qkSIW+vwQ+FS9gNgAK5hNQ
References: <4888C10E.7040602@castlepoint.net>
	<483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
	<488D7701.9080600@castlepoint.net>
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Shane Amante" <shane@castlepoint.net>
X-OriginalArrivalTime: 28 Jul 2008 13:07:45.0680 (UTC)
	FILETIME=[ED56E900:01C8F0B2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4279; t=1217250465;
	x=1218114465; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sajassi@cisco.com;
	z=From:=20=22Ali=20Sajassi=20(sajassi)=22=20<sajassi@cisco.c
	om> |Subject:=20RE=3A=20VPLS=20Architecture |Sender:=20;
	bh=YUaT/8QBU9CHgTM9woiqdqz5wIQLiZNzBZKALOVGGVU=;
	b=MvgSgr+xyFExEPcOz1pHk2Ubfyrf3As3snD2XL3VLBJKxTqXOorVyko1YP
	AOZl/UO9eTB11mmSXoaGLWtOXtihTZVWTYKoChZ2//HKGeVZ/UTk+Rs8YcK+
	EbQxV5+8+h;
Authentication-Results: sj-dkim-3; header.From=sajassi@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Shane,=20

> > Can you be more precise on which drafts you are talking=20
> about. It is=20
> > hard to formulate a response to your comments without knowing what=20
> > drafts you mean specifically.
>=20
> The one I'm most concerned with is:
> draft-mohan-l2vpn-vpls-oam-01
>=20

Can you tell me what the concern is exactly. This is a draft which
describes oam-vpls solution adherent to all the requirements of
vpls-oam-req-frwk which has passed last WG call quite a while ago. In
the last meeting, there was a very good consensus to move this draft to
WG status.=20

> And, to a large extent the following, as well:
> draft-sajassi-l2vpn-pbb-vpls-cmac-flush-00
> draft-sajassi-l2vpn-pbb-vpls-mpls-access-00
> draft-sajassi-l2vpn-pbb-vpls-multicast-00
> draft-sajassi-l2vpn-vpls-pbb-interop-03
> draft-balus-l2vpn-vpls-802.1ah-03

Did you leave out any drafts :-) All this work is within the new updated
WG charter. The scenario drafts describes what scenarios we need to
concern with and the solution drafts talk about the solutions.
Unfortunately, the progress of the work in this working group has been
very slow because the issues are not being understood and as the result
any work to address these issues are not being look at properly.=20


> Although, to be fair, this latter group is IMO more likely a=20
> consequence of the current architecture of VPLS.  So, for=20
> this group in particular, I would prefer if we focus instead=20
> on discussing what might be limitations with the architecture=20
> of VPLS and what might be done to fix it in order that we=20
> reduce the volume of drafts in order to support a new IEEE data-plane.
>

That's the objective. To address the issues at hand without creating any
unnecessary work.=20
=20
> In addition, you do realize that the sum total of draft-sajassi* &
> draft-balus* is currently at 87 pages.  However, RFC 4762 is=20
> a mere 29 pages?  IMO, the reason for the volume of pages is=20
> detailed descriptions of interworking (or, "interoperability=20
> scenarios") of IEEE data-plane technologies, which should be=20
> found in IEEE documents, not in IETF drafts.
>=20

And there will be more. Take a look at where MPLS WG got started and
were they are now. We need to continue improve our solutions to the
market need. If WG thought that RFC 4762 was sufficient, then we
wouldn't need to do the re-chartering.

Regards,
Ali

>=20
>=20
> >> With respect to the first question (re-specification of=20
> other SDO's=20
> >> protocols), there are a significant number of concerns.
> >>  Specifically, when protocols from another SDO are re-specified=20
> >> within the IETF, there is the potential for errors or=20
> omissions to be=20
> >> introduced.  In general, there is likely to be=20
> insufficient expertise=20
> >> widely available within the IETF to review those drafts, in-depth,=20
> >> for accuracy or "faithfulness" to the original SDO's=20
> standard as they=20
> >> progress through the IETF standards process.  Finally, there is=20
> >> always the [unanswered] question of what SDO's document is=20
> considered=20
> >> authoritative in case a conflict, error or omission develops.  In=20
> >> summary, there is both little value and significant risk in=20
> >> widespread re-publication of IEEE/ITU specifications=20
> within the L2VPN=20
> >> WG.  In a well written draft, Normative References to=20
> another SDO's=20
> >> detailed architecture, protocol or technology documents should be=20
> >> more than adequate, and seems to have worked well, so far,=20
> >> particularly in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC=20
> >> 4761] to cite just two examples.
> >>
> >=20
> > I concur. There should be no reason for the=20
> re-specification of IEEE=20
> > drafts for many reasons some of which you have mentioned above.
>=20
> I'm glad you agree.
>=20
>=20
> > As the
> > matter of fact in my pbb-interop draft, I put a short=20
> primer on PBB in=20
> > the Appendix for just this purpose so that any re-specification be=20
> > avoided in the main body of the draft. And I was told by=20
> many people=20
> > that this one page primer was very helpful to them.
>=20
> -shane
>=20


From l2vpn-bounces@ietf.org  Mon Jul 28 14:01:51 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF4963A693E;
	Mon, 28 Jul 2008 14:01:51 -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 255473A683A
	for <l2vpn@core3.amsl.com>; Mon, 28 Jul 2008 14:01:50 -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=[AWL=0.000, 
	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 M7NtQuix7aVH for <l2vpn@core3.amsl.com>;
	Mon, 28 Jul 2008 14:01:49 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id 19E853A693E
	for <l2vpn@ietf.org>; Mon, 28 Jul 2008 14:01:48 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id m6SL1hXN020090;
	Mon, 28 Jul 2008 16:01:47 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Mon, 28 Jul 2008 16:01:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: VPLS Architecture
Date: Mon, 28 Jul 2008 16:01:41 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B04791A7E@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <488D7701.9080600@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VPLS Architecture
Thread-Index: AcjwhK4dpewSVES4SRKgIqQ7O5dDOQAbsvOQ
References: <4888C10E.7040602@castlepoint.net><483F121CD2155B43B56DB71228DBAF1501F34EEB@xmb-sjc-239.amer.cisco.com>
	<488D7701.9080600@castlepoint.net>
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "Shane Amante" <shane@castlepoint.net>,
	"Ali Sajassi \(sajassi\)" <sajassi@cisco.com>
X-OriginalArrivalTime: 28 Jul 2008 21:01:43.0654 (UTC)
	FILETIME=[23B16060:01C8F0F5]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Cc: l2vpn@ietf.org
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

Shane,


> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
> Of Shane Amante
> Sent: Monday, July 28, 2008 12:37 AM
> To: Ali Sajassi (sajassi)
> Cc: l2vpn@ietf.org
> Subject: Re: VPLS Architecture
>=20
> Ali,
>=20
> This is second part of the earlier response.  See below.
>=20
> Ali Sajassi (sajassi) wrote:
> >
> > Shane,
> >
> >> -----Original Message-----
> >> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]
> >> On Behalf Of Shane Amante
> >> Sent: Thursday, July 24, 2008 10:51 AM
> >> To: l2vpn@ietf.org
> >> Subject: VPLS Architecture
> >>
> >> Recently, a significant number of drafts have been submitted,
> >> and discussed, to address incorporating 802.1ag, 802.1ah and
> >> other IEEE/ITU protocols within the VPLS Architecture.  These
> >> drafts appear to largely
> >> be: a) a re-specification of how IEEE protocols work over top
> >> of a VPLS; or, b) how IEEE protocols inter-work with other
> >> IEEE data-plane formats within a VPLS (or PWE3's).  In
> >> addition, for completeness, there is a question which L2VPN
> >> hasn't addressed: the potential for inter-working Native
> >> Service Layer control protocols from the IEEE/ITU with those
> >> created and maintained by L2VPN.
> >>
> >
> > Can you be more precise on which drafts you are talking about. It is
> > hard to formulate a response to your comments without knowing what
> > drafts you mean specifically.
>=20
> The one I'm most concerned with is:
> draft-mohan-l2vpn-vpls-oam-01
>=20
> And, to a large extent the following, as well:
> draft-sajassi-l2vpn-pbb-vpls-cmac-flush-00
> draft-sajassi-l2vpn-pbb-vpls-mpls-access-00
> draft-sajassi-l2vpn-pbb-vpls-multicast-00
> draft-sajassi-l2vpn-vpls-pbb-interop-03
> draft-balus-l2vpn-vpls-802.1ah-03
> Although, to be fair, this latter group is IMO more likely a
> consequence
> of the current architecture of VPLS.  So, for this group in
particular,
> I would prefer if we focus instead on discussing what might be
> limitations with the architecture of VPLS and what might be done to
fix
> it in order that we reduce the volume of drafts in order to support a
> new IEEE data-plane.
>=20
> In addition, you do realize that the sum total of draft-sajassi* &
> draft-balus* is currently at 87 pages.  However, RFC 4762 is a mere 29
> pages?  IMO, the reason for the volume of pages is detailed
> descriptions
> of interworking (or, "interoperability scenarios") of IEEE data-plane
> technologies, which should be found in IEEE documents, not in IETF
> drafts.
>=20
[[FB]] We believe there are a number of items in
draft-balus-l2vpn-vpls-802.1ah-03 that fit the L2VPN scope and address
the VPLS scalability: the discussion around VPLS Addressing for both BGP
AD and LDP Signaling, the extension to LDP MAC Flush and the
introduction of NSP capabilities specific to PBB NSP. The rest of the
text was supposed to help the understanding of the solution space. I can
work with the other authors to summarize the later part/eventually
include it in the Appendix for the next version of the document.=20

Florin






>=20
>=20
> >> With respect to the first question (re-specification of other
> >> SDO's protocols), there are a significant number of concerns.
> >>  Specifically, when protocols from another SDO are
> >> re-specified within the IETF, there is the potential for
> >> errors or omissions to be introduced.  In general, there is
> >> likely to be insufficient expertise widely available within
> >> the IETF to review those drafts, in-depth, for accuracy or
> >> "faithfulness" to the original SDO's standard as they
> >> progress through the IETF standards process.  Finally, there
> >> is always the [unanswered] question of what SDO's document is
> >> considered authoritative in case a conflict, error or
> >> omission develops.  In summary, there is both little value
> >> and significant risk in widespread re-publication of IEEE/ITU
> >> specifications within the L2VPN WG.  In a well written draft,
> >> Normative References to another SDO's detailed architecture,
> >> protocol or technology documents should be more than
> >> adequate, and seems to have worked well, so far, particularly
> >> in the cases of VPLS-LDP [RFC 4762] and VPLS-BGP [RFC 4761]
> >> to cite just two examples.
> >>
> >
> > I concur. There should be no reason for the re-specification of IEEE
> > drafts for many reasons some of which you have mentioned above.
>=20
> I'm glad you agree.
>=20
>=20
> > As the
> > matter of fact in my pbb-interop draft, I put a short primer on PBB
> in
> > the Appendix for just this purpose so that any re-specification be
> > avoided in the main body of the draft. And I was told by many people
> > that this one page primer was very helpful to them.
>=20
> -shane


From l2vpn-bounces@ietf.org  Wed Jul 30 00:07:40 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 157193A6AC8;
	Wed, 30 Jul 2008 00:07:40 -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 7137D3A6AED
	for <l2vpn@core3.amsl.com>; Wed, 30 Jul 2008 00:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5
	tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4, 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 vXZguPhF5PG8 for <l2vpn@core3.amsl.com>;
	Wed, 30 Jul 2008 00:07:37 -0700 (PDT)
Received: from mail203.messagelabs.com (mail203.messagelabs.com
	[216.82.254.243])
	by core3.amsl.com (Postfix) with ESMTP id 44C9B3A6AC8
	for <l2vpn@ietf.org>; Wed, 30 Jul 2008 00:07:37 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: uttaro@att.com
X-Msg-Ref: server-5.tower-203.messagelabs.com!1217401647!3770298!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 22256 invoked from network); 30 Jul 2008 07:07:27 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-5.tower-203.messagelabs.com with AES256-SHA encrypted SMTP;
	30 Jul 2008 07:07:27 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m6U77mQk013918 for <l2vpn@ietf.org>; Wed, 30 Jul 2008 03:07:48 -0400
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com
	[144.155.43.107])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m6U77ioX013885 for <l2vpn@ietf.org>; Wed, 30 Jul 2008 03:07:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8F212.F681A3F4"
Subject: l2vpn-vpls-multi-homing-01.txt
Date: Wed, 30 Jul 2008 03:07:43 -0400
Message-ID: <1477DEAE19DD884CB004730D0FD77FD708CBC6@misout7msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: l2vpn-vpls-multi-homing-01.txt
Thread-Index: AcjyEvaDOhOLxQlwSf6GgIV0bnIwJw==
From: "UTTARO, JAMES, ATTLABS" <uttaro@att.com>
To: <l2vpn@ietf.org>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F212.F681A3F4
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

The current approach being used to accomplish leaking "multi-homed"
information between AS's is too tag the primary with some CV and then
take action as it crosses the AS boundary ( set LP ).. The draft seems
to take the approach of mapping the LP to a VE preference for a route (
VE-ID) in the local AS ( AS1). The advantage of the first solution is
that a route may be leaked across multiple AS boundaries. As the CV
remains ( transitive ) I can always key off of it to set  LP in the
current AS domain. How can I accomplish this with VE pref? Is it kept as
the route transits through multiple AS? I assume that VE pref is
transitive and not reset upon re-advertisement from remote AS2 to remote
AS3.=20
=20
It states for "BGP Path Selection" that ADs with the same exact <RD,
VE-ID, VBO> are candidates for BGP Path Selection.. In our network we
use unique RDs to reduce convergence time for primary/backup. Our
approach is to ensure that both the primary and backup sites are opaque
to the BGP topology. In this way both routes are sent to all PEs
participating in the L2VPN. So how would a receiving PE treat to routes
that have the same VE-ID but different RDs? The draft states the they
would not be candidates for "BGP Path Selection". This implies I cannot
manipulate LP to select a primary when I use unique RDs. This definitely
is in conflict with our fast convergence goals for our L2VPN customers.
=20
Jim Uttaro

------_=_NextPart_001_01C8F212.F681A3F4
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3354" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D860392606-30072008>The =
current approach=20
being used to accomplish leaking "multi-homed" information between AS's =
is too=20
tag the primary with some CV and then take action as it crosses the AS =
boundary=20
( set LP ).. The draft seems to take the approach of mapping the LP to a =
VE=20
preference for a route ( VE-ID) in the local AS ( AS1). The advantage of =
the=20
first solution is that a route may&nbsp;be leaked across&nbsp;multiple =
AS=20
boundaries. As the CV remains ( transitive ) I can always key off of it =
to=20
set&nbsp; LP in the current AS domain. How can I accomplish this with VE =
pref?=20
Is it kept as the route transits through multiple AS? I assume that VE =
pref is=20
transitive and not reset upon re-advertisement from remote AS2 to remote =
AS3.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D860392606-30072008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D860392606-30072008>It =
states for "BGP=20
Path Selection" that ADs with&nbsp;the same exact&nbsp;&lt;RD, VE-ID, =
VBO&gt;=20
are candidates for BGP Path Selection.. In our network we use unique RDs =
to=20
reduce convergence time for primary/backup. Our approach is to ensure =
that both=20
the primary and backup sites&nbsp;are opaque to the BGP topology. In =
this way=20
both routes are sent to all PEs participating in the L2VPN. So how would =
a=20
receiving PE treat to routes that have the same VE-ID but different RDs? =
The=20
draft states the they would not be candidates for "BGP Path Selection". =
This=20
implies I cannot manipulate LP to select&nbsp;a primary when I use =
unique RDs.=20
This definitely is in conflict with our fast convergence goals for our =
L2VPN=20
customers.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D860392606-30072008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D860392606-30072008>Jim=20
Uttaro</SPAN></FONT></DIV></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C8F212.F681A3F4--


From l2vpn-bounces@ietf.org  Wed Jul 30 23:51:13 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A17A128C12D;
	Wed, 30 Jul 2008 23:51:13 -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 3BE413A6C2F
	for <l2vpn@core3.amsl.com>; Wed, 30 Jul 2008 23:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[AWL=0.238, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 DQPwGi6818Bn for <l2vpn@core3.amsl.com>;
	Wed, 30 Jul 2008 23:51:06 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id EC5D028C11A
	for <l2vpn@ietf.org>; Wed, 30 Jul 2008 23:51:05 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m6V6p9mx019585
	for <l2vpn@ietf.org>; Thu, 31 Jul 2008 08:51:09 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 31 Jul 2008 08:51:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8F2D9.CF9C6E7A"
Subject: draft-kompella-l2vpn-vpls-multihoming-01
Date: Thu, 31 Jul 2008 08:51:17 +0200
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D702F859BF@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: Acjy2dTqRslOb5JrSsWPww96NURuBA==
From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be>
To: <l2vpn@ietf.org>
X-OriginalArrivalTime: 31 Jul 2008 06:51:09.0076 (UTC)
	FILETIME=[CFF40540:01C8F2D9]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F2D9.CF9C6E7A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

During the session I expressed concerns regarding 2 dual homes CE(s) on
2 PE(s) with multi-homing. Here is the scenario I had in mind.

                            (VE1, VE2)
                ____ PE1....................
              /  ____/  :                               :
        __/   /         :                                PE3
CE1 __   /          :                                 :
            \ /             :                              :
             / \_____ PE2 ..................
       __/               /  (VE1, VE2)
CE2 _________/

PE3 picks a designated forwarder lets say PE1 for both CE1 and CE2.
After discussion what I understood is that when CE1 fails PE3 reelects
the designated forwarder for both CE1 and CE2 and PE3 also flushes the
Mac table.

This should be addressed as an impact on CE1 should not impact other
CE(s) according to me.

Cheers,
Wim

------_=_NextPart_001_01C8F2D9.CF9C6E7A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>draft-kompella-l2vpn-vpls-multihoming-01</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">During the session I expressed concerns =
regarding 2 dual homes CE(s) on 2 PE(s) with multi-homing. Here is the =
scenario I had in mind.</FONT></P>

<P><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (VE1, VE2)</FONT>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; ____ =
PE1&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; /&nbsp; ____/&nbsp; =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; __/&nbsp;&nbsp; =
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PE3</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New Roman">CE1 =
__&nbsp;&nbsp; /&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 \ =
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; / \_____ PE2 =
&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; /&nbsp;</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">(VE1, VE2)</FONT></SPAN><SPAN LANG=3D"nl-be"></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New Roman">CE2 =
_________/</FONT></SPAN>
</P>

<P><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New Roman">PE3 picks a =
designated forwarder lets say PE1 for both CE1 and CE2. After discussion =
what I understood is that when CE1 fails PE3 reelects the designated =
forwarder for both CE1 and CE2 and PE3 also flushes the Mac =
table.</FONT></SPAN></P>

<P><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New Roman">This should be =
addressed as an impact on CE1 should not impact other CE(s) according to =
me.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">Cheers,</FONT></SPAN>

<BR><SPAN LANG=3D"nl-be"><FONT FACE=3D"Times New =
Roman">Wim</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8F2D9.CF9C6E7A--


From l2vpn-bounces@ietf.org  Thu Jul 31 13:01:17 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DD3D3A6993;
	Thu, 31 Jul 2008 13:01:17 -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 DD1B03A6A3C
	for <l2vpn@core3.amsl.com>; Thu, 31 Jul 2008 13:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.013, 
	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 OykMaUzt8ST1 for <l2vpn@core3.amsl.com>;
	Thu, 31 Jul 2008 13:01:10 -0700 (PDT)
Received: from audl952.usa.alcatel.com (audl952.usa.alcatel.com
	[143.209.238.159])
	by core3.amsl.com (Postfix) with ESMTP id 662623A69DA
	for <l2vpn@ietf.org>; Thu, 31 Jul 2008 13:01:10 -0700 (PDT)
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com
	[172.22.216.13])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id m6VK1SgK019022
	for <l2vpn@ietf.org>; Thu, 31 Jul 2008 15:01:28 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs02.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 31 Jul 2008 15:01:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8F348.37D3EC0F"
Subject: RE: draft-kompella-l2vpn-vpls-multihoming-01
Date: Thu, 31 Jul 2008 15:01:22 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0479210A@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <B128F666D4C8BD4FBF56CEAFB2DB66D702F859BF@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: Acjy2dTqRslOb5JrSsWPww96NURuBAAVt9Zw
References: <B128F666D4C8BD4FBF56CEAFB2DB66D702F859BF@FRVELSMBS22.ad2.ad.alcatel.com>
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 31 Jul 2008 20:01:27.0756 (UTC)
	FILETIME=[37B060C0:01C8F348]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F348.37D3EC0F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have some other comments, questions I want to raise on this draft:

-          Let's assume PE1 is chosen by PE3 over PE2 in the diagram
below

-          The distribution model for BGP VPLS information (through BGP)
is one to many with no individual p2p communication between PE2-PE3.=20

-          How does PE2 know that he was not chosen by PE3? PE3 needs to
know that to bring down its own data plane towards PE2 or otherwise I
see some problems (e.g. PE3 sending BUM traffic to PE2 wasting bandwidth
in the core, even confusion at PE3 for the PHP case when receiving
traffic from both PE2 and PE1 from the same VE ID).

=20

Adding to the comments raised below by Wim

-          I think the case of a single homed CE mixed with the
dual-homed ones seems even more problematic: i.e. the single-homed CE
could be left hanging, isolated from the other VPLS sites.=20

-          I was under the impression this could be done by assigning
separate VE IDs & label blocks for each dual-homed CEs/single-homed CE
group (a complex solution, wasting a lot of label block resources).  I
understood from hallway discussions that the authors said the separate
VE IDs are not anyhow the solution. Can we get a confirmation about how
this is addressed?=20

Thanks,

Florin

=20

=20

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of HENDERICKX Wim
Sent: Wednesday, July 30, 2008 11:51 PM
To: l2vpn@ietf.org
Subject: draft-kompella-l2vpn-vpls-multihoming-01

=20

During the session I expressed concerns regarding 2 dual homes CE(s) on
2 PE(s) with multi-homing. Here is the scenario I had in mind.

                            (VE1, VE2)=20
                ____ PE1....................=20
              /  ____/  :                               :=20
        __/   /         :                                PE3=20
CE1 __   /          :                                 :=20
            \ /             :                              :=20
             / \_____ PE2 ..................=20
       __/               /  (VE1, VE2)=20
CE2 _________/=20

PE3 picks a designated forwarder lets say PE1 for both CE1 and CE2.
After discussion what I understood is that when CE1 fails PE3 reelects
the designated forwarder for both CE1 and CE2 and PE3 also flushes the
Mac table.

This should be addressed as an impact on CE1 should not impact other
CE(s) according to me.=20

Cheers,=20
Wim=20


------_=_NextPart_001_01C8F348.37D3EC0F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<title>draft-kompella-l2vpn-vpls-multihoming-01</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1076588601;
	mso-list-type:hybrid;
	mso-list-template-ids:-195232180 -1535720648 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have some other comments, questions I want to raise on =
this draft:<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Let&#8217;s assume PE1 is chosen by PE3 over PE2 in the =
diagram
below<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The distribution model for BGP VPLS information (through =
BGP) is
one to many with no individual p2p communication between PE2-PE3. =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>How does PE2 know that he was not chosen by PE3? PE3 =
needs to
know that to bring down its own data plane towards PE2 or otherwise I =
see some
problems (e.g. PE3 sending BUM traffic to PE2 wasting bandwidth in the =
core,
even confusion at PE3 for the PHP case when receiving traffic from both =
PE2 and
PE1 from the same VE ID).<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span=
></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Adding to the comments =
raised
below by Wim<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think the case of a single homed CE mixed with the =
dual-homed ones
seems even more problematic: i.e. the single-homed CE could be left =
hanging,
isolated from the other VPLS sites. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I was under the impression this could be done by =
assigning
separate VE IDs &amp; label blocks for each dual-homed CEs/single-homed =
CE
group (a complex solution, wasting a lot of label block resources). =
&nbsp;I
understood from hallway discussions that the authors said the separate =
VE IDs are
not anyhow the solution. Can we get a confirmation about how this is =
addressed?
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Florin<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] <b>On Behalf Of =
</b>HENDERICKX
Wim<br>
<b>Sent:</b> Wednesday, July 30, 2008 11:51 PM<br>
<b>To:</b> l2vpn@ietf.org<br>
<b>Subject:</b> =
draft-kompella-l2vpn-vpls-multihoming-01<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>During the
session I expressed concerns regarding 2 dual homes CE(s) on 2 PE(s) =
with
multi-homing. Here is the scenario I had in mind.</span><o:p></o:p></p>

<p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
(VE1, VE2)</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
____ PE1&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
/&nbsp; ____/&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__/&nbsp;&nbsp;
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
PE3</span> <br>
<span lang=3DNL-BE>CE1 __&nbsp;&nbsp;
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
\ =
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=

:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
/ \_____ PE2 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;</span> <br>
<span lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
__/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
/&nbsp; </span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>(VE1,
VE2)</span> <br>
<span lang=3DNL-BE>CE2 _________/ </span><o:p></o:p></p>

<p><span lang=3DNL-BE>PE3 picks a designated forwarder lets say PE1 for =
both CE1
and CE2. After discussion what I understood is that when CE1 fails PE3 =
reelects
the designated forwarder for both CE1 and CE2 and PE3 also flushes the =
Mac
table.</span><o:p></o:p></p>

<p><span lang=3DNL-BE>This should be addressed as an impact on CE1 =
should not
impact other CE(s) according to me. </span><o:p></o:p></p>

<p><span lang=3DNL-BE>Cheers,</span> <br>
<span lang=3DNL-BE>Wim </span><o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C8F348.37D3EC0F--


From l2vpn-bounces@ietf.org  Thu Jul 31 13:08:06 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCA1F3A6AFB;
	Thu, 31 Jul 2008 13:08:06 -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 8E79B3A6C37
	for <l2vpn@core3.amsl.com>; Thu, 31 Jul 2008 13:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.011, 
	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 9sZZD-rrqGWh for <l2vpn@core3.amsl.com>;
	Thu, 31 Jul 2008 13:07:59 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id 8DC6F3A6AFB
	for <l2vpn@ietf.org>; Thu, 31 Jul 2008 13:07:59 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id m6VK8GwZ026186
	for <l2vpn@ietf.org>; Thu, 31 Jul 2008 15:08:17 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 31 Jul 2008 15:08:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8F349.2B8D46FD"
Subject: RE: draft-kompella-l2vpn-vpls-multihoming-01
Date: Thu, 31 Jul 2008 15:08:11 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0479210F@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <4A5028372622294A99B8FFF6BD06EB7B0479210A@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: Acjy2dTqRslOb5JrSsWPww96NURuBAAVt9ZwAAX+qLA=
References: <B128F666D4C8BD4FBF56CEAFB2DB66D702F859BF@FRVELSMBS22.ad2.ad.alcatel.com>
	<4A5028372622294A99B8FFF6BD06EB7B0479210A@USDALSMBS03.ad3.ad.alcatel.com>
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>,
	"HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 31 Jul 2008 20:08:16.0704 (UTC)
	FILETIME=[2B70E400:01C8F349]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F349.2B8D46FD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I had an error in my email below - PE3 got switched with PE2. Here is
the correct paragraph should have been:

-How does PE2 know that he was not chosen by PE3? PE2 needs to know that
to bring down its own data plane towards PE3 or otherwise I see some
problems (e.g. PE2 sending BUM traffic to PE3 wasting bandwidth in the
core, confusion can be created at PE3 for the PHP case when receiving
traffic from both PE2 and PE1 from the same VE ID)."

=20

Sorry about that,

Florin

=20

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of BALUS Florin
Sent: Thursday, July 31, 2008 1:01 PM
To: HENDERICKX Wim; l2vpn@ietf.org
Subject: RE: draft-kompella-l2vpn-vpls-multihoming-01

=20

I have some other comments, questions I want to raise on this draft:

-          Let's assume PE1 is chosen by PE3 over PE2 in the diagram
below

-          The distribution model for BGP VPLS information (through BGP)
is one to many with no individual p2p communication between PE2-PE3.=20

-          How does PE2 know that he was not chosen by PE3? PE3 needs to
know that to bring down its own data plane towards PE2 or otherwise I
see some problems (e.g. PE3 sending BUM traffic to PE2 wasting bandwidth
in the core, even confusion at PE3 for the PHP case when receiving
traffic from both PE2 and PE1 from the same VE ID).

=20

Adding to the comments raised below by Wim

-          I think the case of a single homed CE mixed with the
dual-homed ones seems even more problematic: i.e. the single-homed CE
could be left hanging, isolated from the other VPLS sites.=20

-          I was under the impression this could be done by assigning
separate VE IDs & label blocks for each dual-homed CEs/single-homed CE
group (a complex solution, wasting a lot of label block resources).  I
understood from hallway discussions that the authors said the separate
VE IDs are not anyhow the solution. Can we get a confirmation about how
this is addressed?=20

Thanks,

Florin

=20

=20

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of HENDERICKX Wim
Sent: Wednesday, July 30, 2008 11:51 PM
To: l2vpn@ietf.org
Subject: draft-kompella-l2vpn-vpls-multihoming-01

=20

During the session I expressed concerns regarding 2 dual homes CE(s) on
2 PE(s) with multi-homing. Here is the scenario I had in mind.

                            (VE1, VE2)=20
                ____ PE1....................=20
              /  ____/  :                               :=20
        __/   /         :                                PE3=20
CE1 __   /          :                                 :=20
            \ /             :                              :=20
             / \_____ PE2 ..................=20
       __/               /  (VE1, VE2)=20
CE2 _________/=20

PE3 picks a designated forwarder lets say PE1 for both CE1 and CE2.
After discussion what I understood is that when CE1 fails PE3 reelects
the designated forwarder for both CE1 and CE2 and PE3 also flushes the
Mac table.

This should be addressed as an impact on CE1 should not impact other
CE(s) according to me.=20

Cheers,=20
Wim=20


------_=_NextPart_001_01C8F349.2B8D46FD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<title>draft-kompella-l2vpn-vpls-multihoming-01</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1076588601;
	mso-list-type:hybrid;
	mso-list-template-ids:-195232180 -1535720648 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I had an error in my email below - PE3 got switched with =
PE2.
Here is the correct paragraph should have been:<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>How
does PE2 know that he was not chosen by PE3? PE2 needs to know that to =
bring
down its own data plane towards PE3 or otherwise I see some problems =
(e.g. PE2
sending BUM traffic to PE3 wasting bandwidth in the core, confusion can =
be
created at PE3 for the PHP case when receiving traffic from both PE2 and =
PE1
from the same VE ID).&#8221;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sorry about that,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Florin<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] <b>On Behalf Of =
</b>BALUS
Florin<br>
<b>Sent:</b> Thursday, July 31, 2008 1:01 PM<br>
<b>To:</b> HENDERICKX Wim; l2vpn@ietf.org<br>
<b>Subject:</b> RE: =
draft-kompella-l2vpn-vpls-multihoming-01<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have some other comments, questions I want to raise on =
this
draft:<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Let&#8217;s assume PE1 is chosen by PE3 over PE2 in the =
diagram
below<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The distribution model for BGP VPLS information (through =
BGP) is
one to many with no individual p2p communication between PE2-PE3. =
<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>How does PE2 know that he was not chosen by PE3? PE3 =
needs to
know that to bring down its own data plane towards PE2 or otherwise I =
see some
problems (e.g. PE3 sending BUM traffic to PE2 wasting bandwidth in the =
core,
even confusion at PE3 for the PHP case when receiving traffic from both =
PE2 and
PE1 from the same VE ID).<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span=
></p>

<p class=3DMsoListParagraph style=3D'margin-left:0in'><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Adding to the comments =
raised
below by Wim<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think the case of a single homed CE mixed with the =
dual-homed
ones seems even more problematic: i.e. the single-homed CE could be left
hanging, isolated from the other VPLS sites. <o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I was under the impression this could be done by =
assigning
separate VE IDs &amp; label blocks for each dual-homed CEs/single-homed =
CE
group (a complex solution, wasting a lot of label block resources). =
&nbsp;I
understood from hallway discussions that the authors said the separate =
VE IDs
are not anyhow the solution. Can we get a confirmation about how this is
addressed? <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Florin<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] <b>On Behalf Of =
</b>HENDERICKX
Wim<br>
<b>Sent:</b> Wednesday, July 30, 2008 11:51 PM<br>
<b>To:</b> l2vpn@ietf.org<br>
<b>Subject:</b> =
draft-kompella-l2vpn-vpls-multihoming-01<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>During the
session I expressed concerns regarding 2 dual homes CE(s) on 2 PE(s) =
with
multi-homing. Here is the scenario I had in mind.</span><o:p></o:p></p>

<p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
(VE1, VE2)</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
____ PE1&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
/&nbsp; ____/&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__/&nbsp;&nbsp;
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
PE3</span> <br>
<span lang=3DNL-BE>CE1 __&nbsp;&nbsp;
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
\ =
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=

:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
/ \_____ PE2 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;</span><span =
lang=3DNL-BE>
</span><br>
<span lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
__/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
/&nbsp; </span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>(VE1,
VE2)</span> <br>
<span lang=3DNL-BE>CE2 _________/ </span><o:p></o:p></p>

<p><span lang=3DNL-BE>PE3 picks a designated forwarder lets say PE1 for =
both CE1
and CE2. After discussion what I understood is that when CE1 fails PE3 =
reelects
the designated forwarder for both CE1 and CE2 and PE3 also flushes the =
Mac
table.</span><o:p></o:p></p>

<p><span lang=3DNL-BE>This should be addressed as an impact on CE1 =
should not
impact other CE(s) according to me. </span><o:p></o:p></p>

<p><span lang=3DNL-BE>Cheers,</span> <br>
<span lang=3DNL-BE>Wim </span><o:p></o:p></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C8F349.2B8D46FD--


From l2vpn-bounces@ietf.org  Thu Jul 31 15:07:35 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F0DC3A6B05;
	Thu, 31 Jul 2008 15:07:35 -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 0258F3A67FF;
	Thu, 31 Jul 2008 15:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5
	tests=[AWL=-0.051, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	SARE_SUB_OBFU_OTHER=0.135]
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 sCuG5PhA55OE; Thu, 31 Jul 2008 15:07:32 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com
	[143.209.238.162])
	by core3.amsl.com (Postfix) with ESMTP id 84C0D3A680E;
	Thu, 31 Jul 2008 15:07:32 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com
	[172.22.216.19])
	by audl953.usa.alcatel.com (ALCANET) with ESMTP id m6VM7YFX014974;
	Thu, 31 Jul 2008 17:07:34 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by
	usdalsbhs01.ad3.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 31 Jul 2008 17:07:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8F359.D5A639CB"
Subject: RE: [PWE3] A litmus test for the NSP Capabilities TLV
	indraft-vkompella-pwe3-ethernet-pw-bis-01.txt
Date: Thu, 31 Jul 2008 17:07:28 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0479215E@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <4A5028372622294A99B8FFF6BD06EB7B04792155@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] A litmus test for the NSP Capabilities TLV
	indraft-vkompella-pwe3-ethernet-pw-bis-01.txt
Thread-Index: Acjxk5pHqMWxJSryTMSA+UPP2gxM7gBtxwWQAANqatA=
References: <A3C5DF08D38B6049839A6F553B331C7680265CE467@ILPTMAIL02.ecitele.com>
	<4A5028372622294A99B8FFF6BD06EB7B04792155@USDALSMBS03.ad3.ad.alcatel.com>
From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>
To: <pwe3@ietf.org>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 31 Jul 2008 22:07:34.0096 (UTC)
	FILETIME=[D5943D00:01C8F359]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F359.D5A639CB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

I would like to add here that we welcome feedback also from L2VPN WG
about the possible applicability of the NSP capability TLV.=20

For the example described below this is a new functionality IEEE did not
consider for the IEEE 802.1ah (PBB) specification.=20

=20

Florin

=20

From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
BALUS Florin
Sent: Thursday, July 31, 2008 2:53 PM
To: Alexander Vainshtein; pwe3@ietf.org
Subject: Re: [PWE3] A litmus test for the NSP Capabilities TLV
indraft-vkompella-pwe3-ethernet-pw-bis-01.txt

=20

Sasha,

The main purpose of draft-vkompella-pwe3-ethernet-pw-bis was to clearly
differentiate between the NSP and the PW termination functions so that
it is easier to accommodate new specifications from other SDOs (e.g.
IEEE) without having to rewrite every time the IETF documents.=20

=20

The NSP capabilities TLV was introduced to address some specific
requirements we heard from Service Providers. For example, see slide  8
of the package we presented during L2VPN for PBB-VPLS extensions
(draft-balus-l2vpn-vpls-802.1ah-03) at
http://www3.ietf.org/proceedings/08jul/slides/l2vpn-5.ppt .  Address
separation between the I-VPLS and B-VPLS domains can provide a way to
minimize the occurrences of PW miss-connectivity but if a Service
Providers wants to avoid it altogether then the NSP capability TLV can
be used together with an implementation knob.

=20

It is important to note that there are some use cases where in fact
connectivity between an I-VPLS, a B-VPLS and regular VPLS instances
might be required: i.e. in some migration scenarios there might be a
need to connect B-VPLS or I-VPLS instances to regular VPLS ones just
because existing PEs do not support the PBB-VPLS. Another example might
be future Carrier of Carrier services where a B-VPLS might connect to
the I-VPLS.  That is why an implementation knob should be used where a
Service Provider can control whether to use or not the NSP capability on
a per remote PE.=20

=20
I hope this answers your question.
Florin

=20

=20

From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Alexander Vainshtein
Sent: Tuesday, July 29, 2008 8:56 AM
To: pwe3@ietf.org
Subject: [PWE3] A litmus test for the NSP Capabilities TLV in
draft-vkompella-pwe3-ethernet-pw-bis-01.txt

=20

Hi all,

=20

IMHO there is a simple enough litmus test regarding usefulness (or lack
thereof) of the NSP Capabilities TLV in the above-mentioned draft:

=20

If there is a valid use case when mismatch between expected and actual
capabilities of the NSPs prevents normal operation of the PW, such a TLV
is required.

=20

Otherwise it looks as if we could do without...

=20

My 2c.

    Sasha


------_=_NextPart_001_01C8F359.D5A639CB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I would like to add here that we welcome feedback also =
from L2VPN
WG about the possible applicability of the NSP capability TLV. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For the example described below this is a new =
functionality IEEE
did not consider for the IEEE 802.1ah (PBB) specification. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Florin<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] <b>On Behalf Of =
</b>BALUS
Florin<br>
<b>Sent:</b> Thursday, July 31, 2008 2:53 PM<br>
<b>To:</b> Alexander Vainshtein; pwe3@ietf.org<br>
<b>Subject:</b> Re: [PWE3] A litmus test for the NSP Capabilities TLV
indraft-vkompella-pwe3-ethernet-pw-bis-01.txt<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sasha,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The main purpose of draft-vkompella-pwe3-ethernet-pw-bis =
was to
clearly differentiate between the NSP and the PW termination functions =
so that
it is easier to accommodate new specifications from other SDOs (e.g. =
IEEE)
without having to rewrite every time the IETF documents. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The NSP capabilities TLV was introduced to address some =
specific
requirements we heard from Service Providers. For example, see =
slide&nbsp; 8 of
the package we presented during L2VPN for PBB-VPLS extensions =
(draft-balus-l2vpn-vpls-802.1ah-03)
at <a =
href=3D"http://www3.ietf.org/proceedings/08jul/slides/l2vpn-5.ppt">http:/=
/www3.ietf.org/proceedings/08jul/slides/l2vpn-5.ppt</a>
. &nbsp;Address separation between the I-VPLS and B-VPLS domains can =
provide a
way to minimize the occurrences of PW miss-connectivity but if a Service
Providers wants to avoid it altogether then the NSP capability TLV can =
be used
together with an implementation knob.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It is important to note that there are some use cases =
where in
fact connectivity between an I-VPLS, a B-VPLS and regular VPLS instances =
might
be required: i.e. in some migration scenarios there might be a need to =
connect
B-VPLS or I-VPLS instances to regular VPLS ones just because existing =
PEs do
not support the PBB-VPLS. Another example might be future Carrier of =
Carrier
services where a B-VPLS might connect to the I-VPLS. &nbsp;That is why =
an
implementation knob should be used where a Service Provider can control =
whether
to use or not the NSP capability on a per remote PE. =
<o:p></o:p></span></p>

<pre><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></pre><pre><span =
style=3D'font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I hope this answers =
your question.<o:p></o:p></span></pre><pre><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Florin</span><o:p></o:p></pre>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] <b>On Behalf Of =
</b>Alexander
Vainshtein<br>
<b>Sent:</b> Tuesday, July 29, 2008 8:56 AM<br>
<b>To:</b> pwe3@ietf.org<br>
<b>Subject:</b> [PWE3] A litmus test for the NSP Capabilities TLV in =
draft-vkompella-pwe3-ethernet-pw-bis-01.txt<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi
all,</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>IMHO
there is a simple enough litmus test regarding usefulness (or lack =
thereof) of
the NSP Capabilities TLV in the above-mentioned =
draft:</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>If
there is a valid use case when mismatch between expected and actual
capabilities of the NSPs prevents normal operation of the PW, such a TLV =
is
required.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Otherwise
it looks as if we could do without...</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>My
2c.</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span =
style=3D'font-size:10.0pt;font-family:
"Arial","sans-serif"'>Sasha</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C8F359.D5A639CB--


From l2vpn-bounces@ietf.org  Thu Jul 31 23:45:35 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5886B3A6B45;
	Thu, 31 Jul 2008 23:45:35 -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 F12363A6B45
	for <l2vpn@core3.amsl.com>; Thu, 31 Jul 2008 23:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Jdb6AH7+apPo for <l2vpn@core3.amsl.com>;
	Thu, 31 Jul 2008 23:45:25 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157])
	by core3.amsl.com (Postfix) with ESMTP id 23F7C3A697E
	for <l2vpn@ietf.org>; Thu, 31 Jul 2008 23:45:17 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob102.postini.com
	([64.18.6.12]) with SMTP; Thu, 31 Jul 2008 23:44:28 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp03.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 31 Jul 2008 23:44:52 -0700
Received: from emailbng1.jnpr.net ([10.209.194.15]) by p-emlb01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 31 Jul 2008 23:44:51 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8F3A2.177A8B1D"
Subject: RE: draft-kompella-l2vpn-vpls-multihoming-01
Date: Fri, 1 Aug 2008 12:14:48 +0530
Message-ID: <CD705FABA8532448AA1FB7A96C88FF14074C13B2@emailbng1.jnpr.net>
In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B0479210F@USDALSMBS03.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: Acjy2dTqRslOb5JrSsWPww96NURuBAAVt9ZwAAX+qLAAFFf3kA==
References: <B128F666D4C8BD4FBF56CEAFB2DB66D702F859BF@FRVELSMBS22.ad2.ad.alcatel.com><4A5028372622294A99B8FFF6BD06EB7B0479210A@USDALSMBS03.ad3.ad.alcatel.com>
	<4A5028372622294A99B8FFF6BD06EB7B0479210F@USDALSMBS03.ad3.ad.alcatel.com>
From: "Kaliraj Vairavakkalai" <kaliraj@juniper.net>
To: "BALUS Florin" <Florin.Balus@alcatel-lucent.com>,
	"HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be>, <l2vpn@ietf.org>
X-OriginalArrivalTime: 01 Aug 2008 06:44:51.0577 (UTC)
	FILETIME=[195BFE90:01C8F3A2]
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-Archive: <https://www.ietf.org/mailman/private/l2vpn>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8F3A2.177A8B1D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> -How does PE2 know that he was not chosen by PE3?

=20

I'll try answering this; experts can correct/clarify where required:

=20

PE1, PE2 and PE3 will run the BGP-selection-process for the
Layer2-BGP-NLRI (VE-id VE1) routes announced by PE1 and PE2, and will
arrive at the same result - that either PE2 or PE1 is the
designated-forwarder for site "VE1".=20

=20

When PE2 determines that it-is-not the designated-forwarder-PE for VE1,
it tears-down any PW(dataplane) it may have to the other PEs - with VE1
as the local-endpoint.=20

=20

When PE1 determines that it-is the designated-forwarder-PE for VE1, it
initiates a PW to other PEs (in this case only PE3, supposing PE3 is
housing a layer2-site VE3) as appropriate - where VE1 will be the
local-endpoint of PW, and VE3 the remote-endpoint.=20

=20

PE3 on determining the designated-forwarder-PE for VE1(as PE1 in current
example), will tear-down any PW with PE1 w/ remote-endpoint-as-VE1, and
initiate a PW with PE1 - where VE3 will be the local-endpoint of the PW,
and VE1 the remote-endpoint.=20

=20

> PE3 picks a designated forwarder lets say PE1 for both CE1 and CE2.
After discussion what I understood is that when CE1 fails PE3 reelects
the designated forwarder for both CE1 and CE2

=20

As I understand, when PE3 re-elects PE2 as the designated-forwarder for
site VE1(because CE1-PE1 link failed), PE3 may still elect PE1 as the
designated-forwarder for site VE2 provided CE2 is still connected to PE2
and everything else is fine between PE2-PE3. The designated-forwarder
selection is done per-Site-Id (VE-id), so the results for VE1 would not
necessarily affect the results for VE2.

=20

Thanks,

Kaliraj=20

________________________________

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of BALUS Florin
Sent: Friday, August 01, 2008 1:38 AM
To: BALUS Florin; HENDERICKX Wim; l2vpn@ietf.org
Subject: RE: draft-kompella-l2vpn-vpls-multihoming-01

=20

I had an error in my email below - PE3 got switched with PE2. Here is
the correct paragraph should have been:

-How does PE2 know that he was not chosen by PE3? PE2 needs to know that
to bring down its own data plane towards PE3 or otherwise I see some
problems (e.g. PE2 sending BUM traffic to PE3 wasting bandwidth in the
core, confusion can be created at PE3 for the PHP case when receiving
traffic from both PE2 and PE1 from the same VE ID)."

=20

Sorry about that,

Florin

=20

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of BALUS Florin
Sent: Thursday, July 31, 2008 1:01 PM
To: HENDERICKX Wim; l2vpn@ietf.org
Subject: RE: draft-kompella-l2vpn-vpls-multihoming-01

=20

I have some other comments, questions I want to raise on this draft:

-      Let's assume PE1 is chosen by PE3 over PE2 in the diagram below

-      The distribution model for BGP VPLS information (through BGP) is
one to many with no individual p2p communication between PE2-PE3.=20

-      How does PE2 know that he was not chosen by PE3? PE3 needs to
know that to bring down its own data plane towards PE2 or otherwise I
see some problems (e.g. PE3 sending BUM traffic to PE2 wasting bandwidth
in the core, even confusion at PE3 for the PHP case when receiving
traffic from both PE2 and PE1 from the same VE ID).

=20

Adding to the comments raised below by Wim

-      I think the case of a single homed CE mixed with the dual-homed
ones seems even more problematic: i.e. the single-homed CE could be left
hanging, isolated from the other VPLS sites.=20

-      I was under the impression this could be done by assigning
separate VE IDs & label blocks for each dual-homed CEs/single-homed CE
group (a complex solution, wasting a lot of label block resources).  I
understood from hallway discussions that the authors said the separate
VE IDs are not anyhow the solution. Can we get a confirmation about how
this is addressed?=20

Thanks,

Florin

=20

=20

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of HENDERICKX Wim
Sent: Wednesday, July 30, 2008 11:51 PM
To: l2vpn@ietf.org
Subject: draft-kompella-l2vpn-vpls-multihoming-01

=20

During the session I expressed concerns regarding 2 dual homes CE(s) on
2 PE(s) with multi-homing. Here is the scenario I had in mind.

                            (VE1, VE2)=20
                ____ PE1....................=20
              /  ____/  :                               :=20
        __/   /         :                                PE3=20
CE1 __   /          :                                 :=20
            \ /             :                              :=20
             / \_____ PE2 ..................=20
       __/               /  (VE1, VE2)=20
CE2 _________/=20

PE3 picks a designated forwarder lets say PE1 for both CE1 and CE2.
After discussion what I understood is that when CE1 fails PE3 reelects
the designated forwarder for both CE1 and CE2 and PE3 also flushes the
Mac table.

This should be addressed as an impact on CE1 should not impact other
CE(s) according to me.=20

Cheers,=20
Wim=20


------_=_NextPart_001_01C8F3A2.177A8B1D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40"
xmlns:ns1=3D"http://schemas.microsoft.com/office/2004/12/omml">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>draft-kompella-l2vpn-vpls-multihoming-01</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
	{mso-style-priority:99;}
span.MSOHYPERLINK
	{mso-style-priority:99;}
a:visited
	{mso-style-priority:99;}
span.MSOHYPERLINKFOLLOWED
	{mso-style-priority:99;}
p
	{mso-style-priority:99;}
p.MSOACETATE
	{mso-style-priority:99;}
li.MSOACETATE
	{mso-style-priority:99;}
div.MSOACETATE
	{mso-style-priority:99;}
p.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
li.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
div.MSOLISTPARAGRAPH
	{mso-style-priority:34;}
span.BALLOONTEXTCHAR
	{mso-style-priority:99;}

 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Calibri;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
span.BalloonTextChar
	{font-family:Tahoma;}
p.msolistparagraph, li.msolistparagraph, div.msolistparagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:Calibri;
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1076588601;
	mso-list-type:hybrid;
	mso-list-template-ids:-195232180 -1535720648 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&gt; =
</span></font><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'>-How does PE2 know that he was not chosen by =
PE3?</span></font><font
size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New";color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>I&#8217;ll try
answering this; experts can correct/clarify where =
required:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>PE1, PE2 =
and PE3 will
run the BGP-selection-process for the Layer2-BGP-NLRI (VE-id VE1) routes =
announced
by PE1 and PE2, and will arrive at the same result &#8211; that either =
PE2 or
PE1 is the designated-forwarder for site &#8220;VE1&#8221;. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><font size=3D2 =
color=3Dnavy
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:navy'>When PE2 determines that it-is-not the =
designated-forwarder-PE for
VE1, it tears-down any PW(dataplane) it may have to the other PEs - with =
VE1 as
the local-endpoint. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><font size=3D2 =
color=3Dnavy
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:navy'>When PE1 determines that it-is the designated-forwarder-PE =
for VE1,
it initiates a PW to other PEs (in this case only PE3, supposing PE3 is =
housing
a layer2-site VE3) as appropriate - where VE1 will be the local-endpoint =
of PW,
and VE3 the remote-endpoint. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><font size=3D2 =
color=3Dnavy
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:navy'>PE3 on determining the designated-forwarder-PE for VE1(as =
PE1 in
current example), will tear-down any PW with PE1 w/ =
remote-endpoint-as-VE1, and
initiate a PW with PE1 - where VE3 will be the local-endpoint of the PW, =
and VE1
the remote-endpoint. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&gt; =
</span></font>PE3
picks a designated forwarder lets say PE1 for both CE1 and CE2. After
discussion what I understood is that when CE1 fails PE3 reelects the =
designated
forwarder for both CE1 and CE2<font size=3D2 color=3Dnavy =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>As I =
understand, when
PE3 re-elects PE2 as the designated-forwarder for site VE1(because =
CE1-PE1 link
failed), PE3 may still elect PE1 as the designated-forwarder for site =
VE2
provided CE2 is still connected to PE2 and everything else is fine =
between
PE2-PE3. The designated-forwarder selection is done per-Site-Id (VE-id), =
so the
results for VE1 would not necessarily affect the results for =
VE2.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Kaliraj =
<o:p></o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>BALUS Florin<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, August 01, =
2008 1:38
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> BALUS Florin; =
HENDERICKX Wim;
l2vpn@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE:
draft-kompella-l2vpn-vpls-multihoming-01</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>I had an =
error in my
email below - PE3 got switched with PE2. Here is the correct paragraph =
should
have been:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>-How
does PE2 know that he was not chosen by PE3? PE2 needs to know that to =
bring
down its own data plane towards PE3 or otherwise I see some problems =
(e.g. PE2
sending BUM traffic to PE3 wasting bandwidth in the core, confusion can =
be
created at PE3 for the PHP case when receiving traffic from both PE2 and =
PE1
from the same VE ID).&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Sorry about =
that,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:place w:st=3D"on"><font size=3D2 =
color=3D"#1f497d"
 face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Florin</span=
></font></st1:place><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;<=
/o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>BALUS Florin<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, July 31, =
2008 1:01
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> HENDERICKX Wim; =
l2vpn@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE:
draft-kompella-l2vpn-vpls-multihoming-01<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>I have some =
other
comments, questions I want to raise on this =
draft:<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><span style=3D'mso-list:Ignore'>-<font size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Let&#8217;s
assume PE1 is chosen by PE3 over PE2 in the diagram =
below<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><span style=3D'mso-list:Ignore'>-<font size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>The
distribution model for BGP VPLS information (through BGP) is one to many =
with
no individual p2p communication between PE2-PE3. =
<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><span style=3D'mso-list:Ignore'>-<font size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>How
does PE2 know that he was not chosen by PE3? PE3 needs to know that to =
bring
down its own data plane towards PE2 or otherwise I see some problems =
(e.g. PE3
sending BUM traffic to PE2 wasting bandwidth in the core, even confusion =
at PE3
for the PHP case when receiving traffic from both PE2 and PE1 from the =
same VE
ID).<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'margin-left:0in'><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'margin-left:0in'><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Adding
to the comments raised below by Wim<o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><span style=3D'mso-list:Ignore'>-<font size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>I
think the case of a single homed CE mixed with the dual-homed ones seems =
even
more problematic: i.e. the single-homed CE could be left hanging, =
isolated from
the other VPLS sites. <o:p></o:p></span></font></p>

<p class=3Dmsolistparagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><span style=3D'mso-list:Ignore'>-<font size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#1f497d"
face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>I
was under the impression this could be done by assigning separate VE IDs =
&amp;
label blocks for each dual-homed CEs/single-homed CE group (a complex =
solution,
wasting a lot of label block resources). &nbsp;I understood from hallway
discussions that the authors said the separate VE IDs are not anyhow the
solution. Can we get a confirmation about how this is addressed? =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Thanks,<o:p>=
</o:p></span></font></p>

<p class=3DMsoNormal><st1:place w:st=3D"on"><font size=3D2 =
color=3D"#1f497d"
 face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'>Florin</span=
></font></st1:place><font
size=3D2 color=3D"#1f497d" face=3DCalibri><span =
style=3D'font-size:11.0pt;font-family:
Calibri;color:#1F497D'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#1f497d" =
face=3DCalibri><span
style=3D'font-size:11.0pt;font-family:Calibri;color:#1F497D'><o:p>&nbsp;<=
/o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>HENDERICKX Wim<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, July 30, =
2008 11:51
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> l2vpn@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b>
draft-kompella-l2vpn-vpls-multihoming-01<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>During
the session I expressed concerns regarding 2 dual homes CE(s) on 2 PE(s) =
with
multi-homing. Here is the scenario I had in =
mind.</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(VE1, VE2)</span></font> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
____ PE1&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
/&nbsp; ____/&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
__/&nbsp;&nbsp;
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
PE3</span> <br>
<span lang=3DNL-BE>CE1 __&nbsp;&nbsp;
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
\ =
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=

:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
:</span> <br>
<span =
lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
/ \_____ PE2 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230; </span><br>
<span lang=3DNL-BE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
__/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
/&nbsp; </span><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>(VE1, VE2)</span></font> <br>
<span lang=3DNL-BE>CE2 _________/ </span><o:p></o:p></p>

<p><font size=3D3 face=3D"Times New Roman"><span lang=3DNL-BE =
style=3D'font-size:12.0pt'>PE3
picks a designated forwarder lets say PE1 for both CE1 and CE2. After
discussion what I understood is that when CE1 fails PE3 reelects the =
designated
forwarder for both CE1 and CE2 and PE3 also flushes the Mac =
table.</span><o:p></o:p></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span lang=3DNL-BE =
style=3D'font-size:12.0pt'>This
should be addressed as an impact on CE1 should not impact other CE(s) =
according
to me. </span><o:p></o:p></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span lang=3DNL-BE =
style=3D'font-size:12.0pt'>Cheers,</span>
<br>
</font><span lang=3DNL-BE>Wim </span><o:p></o:p></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C8F3A2.177A8B1D--


