Time slots for IETF 74 L2VPN WG?
Shane Amante <shane@castlepoint.net> Mon, 02 March 2009 02:20 UTC
Return-Path: <shane@castlepoint.net>
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 2F2A43A6A72 for <l2vpn@core3.amsl.com>; Sun, 1 Mar 2009 18:20:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.373
X-Spam-Level:
X-Spam-Status: No, score=-0.373 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, 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 X-Mk8cn9ss52 for <l2vpn@core3.amsl.com>; Sun, 1 Mar 2009 18:20:13 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 5F8183A689E for <l2vpn@ietf.org>; Sun, 1 Mar 2009 18:20:13 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id CD1C92684EA; Sun, 1 Mar 2009 19:20:38 -0700 (MST)
Received: from mbpw.castlepoint.net (71-215-93-49.hlrn.qwest.net [71.215.93.49]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 01 Mar 2009 19:20:38 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.93.49; client-port=3728; syn-fingerprint=65535:55:1:64:M1452,N,W3,N,N,T,S; data-bytes=0
Message-Id: <E48F94F1-711C-4545-80A1-38CDE73EB7A9@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 v930.3)
Subject: Time slots for IETF 74 L2VPN WG?
Date: Sun, 01 Mar 2009 19:20:23 -0700
X-Mailer: Apple Mail (2.930.3)
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>
X-List-Received-Date: Mon, 02 Mar 2009 02:20:14 -0000
Hi All, Please let the chairs know if you would like a time slot for the L2VPN WG meeting at IETF 74. We have been tentatively allocated a 2.5 hour slot on Tuesday, 3/24: TUESDAY, March 24, 2009 0900-1130 Morning Session I Continental 4 INT l2vpn Layer 2 Virtual Private Networks WG -shane From l2vpn@punk.co.nz Tue Mar 3 23:34:24 2009 Return-Path: <l2vpn@punk.co.nz> 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 624943A6A03 for <l2vpn@core3.amsl.com>; Tue, 3 Mar 2009 23:34:24 -0800 (PST) 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 DVpa-s7K4FD0 for <l2vpn@core3.amsl.com>; Tue, 3 Mar 2009 23:34:23 -0800 (PST) Received: from titania.wxnz.net (titania.wxnz.net [58.28.4.13]) by core3.amsl.com (Postfix) with ESMTP id DDD5A28C217 for <l2vpn@ietf.org>; Tue, 3 Mar 2009 23:34:22 -0800 (PST) Received: from [10.1.1.3] (ip-118-90-30-249.xdsl.xnet.co.nz [118.90.30.249]) by titania.wxnz.net (Postfix) with ESMTP id F34A81DB80D7 for <l2vpn@ietf.org>; Wed, 4 Mar 2009 20:34:46 +1300 (NZDT) Message-ID: <49AE2F16.6040401@punk.co.nz> Date: Wed, 04 Mar 2009 20:34:46 +1300 From: Kris Price <l2vpn@punk.co.nz> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: l2vpn@ietf.org Subject: MPLS version of RBridges 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 04 Mar 2009 07:34:24 -0000 Hi, I apologise if this is seen as off topic, but what I have been pondering may be seen to resemble l2vpns, and some people here (who may not be on the RBridge mailing list) may have considered this or have something to say about it. I am talking about approaches to overcoming the shortcomings of bridged IEEE LANs. RBridge is probably the most notable, and most advanced, but there is other work around, such as Nortel's PLSB. It seems to me that these could be achieved using MPLS encapsulation and forwarding. It may resemble VPLS in many ways, but would use new or adapted control-plane protocols operating at layer-2 instead of layer-3. Such a system would share many similarities to RBridges and the problems that TRILL has already solved (or is solving) for RBridges, but the encapsulation and forwarding would be different. Why MPLS? Mainly for the re-use of existing hardware. I assume adding new control-planes is much simpler as it is predominantly a matter of software development. Re-using this hardware would reduce development costs and the time to market (again, I'm assuming). Also, since MPLS seems to have become very popular in transport and provider areas, there may be practical advantages to consolidating on using MPLS hardware for aggregation and campus areas as well. (Rather than splitting effort on the ongoing hardware development front.) But that's well beyond me to say. In summary: Routers run a link-state protocol, building a topological database from which they identify the shortest paths to other routers. Routers set up label switched paths (LSPs) to the other routers. Routers use either control-plane or data-plane learning of reachability information. In control-plane learning, routers learn the MAC addresses of active end stations on attached links, as a normal IEEE bridge would, and distribute this over the link-state protocol so that sending routers can identify the appropriate LSPs on which to forward frames. If using data-plane learning, each router learns the appropriate LSPs by examining packets during decapsulation. When a frame from an end station arrives at a router, the router looks up the destination MAC address, identifying the egress router and appropriate label switch path. The router encapsulates the frame in an MPLS header, and the encapsulated frame is then label switched across the network to the egress node. At the egress node the label is popped and the frame forwarded out the appropriate interface. Single-destination frames would be forwarded on multipoint-to-point (MP2P) LSPs. For single-destination forwarding, scaling is essentially O(n) using MP2P LSPs compared to O(n^2) using P2P LSPs. It appears from the experience of TRILL that data-plane learning is a desirable feature. To achieve this, there are two options apparent to me that could be explored: The first is to place an extra label in the stack when encapsulating a frame in MPLS, which can be used by the egress router to identify the ingress router. In essence these are P2P LSPs tunnelled over the MP2P LSPs. The second is to look at using some kind of MAC-in-MAC encapsulation before the MPLS encapsulation, with the outer MAC header identifying the source and destination addresses of the routers in question (where only the source address is actually relevant). The egress router, after popping the MPLS label, would learn the ingress router via this outer MAC header. Multi-destination forwarding is naturally trickier. Trees would need to be set up, either shared trees as per RBridges using MP2MP LSPs, or source-based trees similar to PLSB and approaches considered for VPLS using P2MP LSPs. Additional trees would be set up for constrained distribution in VLANs and/or IP multicast groups (more later). With multi-destination forwarding there are so many ways to skin it, and it depends on many factors such as: how VLANs and IP multicast is to be handled; trade offs between bending the rules in the MPLS architecture, any requirements for data-plane learning, and balancing the intricacy of the control-plane. VLANs could be managed in a couple of ways: Some form of multi-topology routing could be used to discover the topology of each VLAN, and when transmitting across each link the outer MAC header would contain the VLAN tag of the topology in question, on receipt the router can use this additional information to classify the packet. This can be seen to increase the MPLS label space ("per-subinterface") and constrain the forwarding of frames in a VLAN to links which are in those VLANs. Directly coupled router to router links would simply be full 802.1Q trunks. Another option is not to be concerned about constraining frames to only those links which allow those VLANs, and each router advertises VLAN membership, with constrained distribution trees established for each VLAN. The outer VLAN tags used on each link wouldn't be relevant. IP multicast can also be optimised with constrained trees, and the mcast group membership information distributed by the link-state protocol. I did discover that MPLS encapsulation was proposed for RBridges in draft-bryant-perlman-trill-pwe-encap-00, which from my understanding violates the MPLS architecture, because label assignments are made upstream, but that upstream allocation does certainly make things easier for the control-plane in a system like this (if it's a violation you can live with). The draft does discuss how the paths would be established and it is possible to conceive ways of establishing additional constrained trees for VLANs and IP multicast optimisation too. However, after cursory examination of methods for this, it would seem to require routers to do SPF computations for all routers in the network. A router would need to know its position in the tree to decide if it needed to install relevant forwarding state. This may be considerable overhead, but that does not seem to bother the people behind PLSB, and I do not have the wisdom to declare whether it is or is not. A signalling protocol in the control-plane (perhaps separate, or perhaps carried on the link-state protocol) could remove the need to do these SPF computations, and remove the upstream assignment of labels, making it compliant to the MPLS architecture. But this would be a trade off in that the resulting protocol might be considered more intricate. That is the sum of it. The rest gets into the details of weighing the possible approaches for each part against each other and designing the protocols. I apologise if this is seen as off topic, unfortunately I've no one who understands these subjects well enough that I can bounce the idea off. I just wanted to put it out there in case there were likeminded people who have considered this before, are working on it, thought it worthy of discussion (perhaps in another forum), or were able to open my mind to the flaws in it. Regards Kris Price From root@core3.amsl.com Fri Mar 6 15:00:02 2009 Return-Path: <root@core3.amsl.com> X-Original-To: l2vpn@ietf.org Delivered-To: l2vpn@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id F3F713A696E; Fri, 6 Mar 2009 15:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Subject: I-D ACTION:draft-ietf-l2vpn-arp-mediation-10.txt Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090306230001.F3F713A696E@core3.amsl.com> Date: Fri, 6 Mar 2009 15:00:01 -0800 (PST) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Fri, 06 Mar 2009 23:00:02 -0000 --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 : ARP Mediation for IP Interworking of Layer 2 VPN Author(s) : E. Rosen, H. Shah, G. Heron, V. Kompella Filename : draft-ietf-l2vpn-arp-mediation-10.txt Pages : 28 Date : 2009-3-6 The VPWS service [L2VPN-FRM] provides point-to-point connections between pairs of Customer Edge (CE) devices. It does so by binding two Attachment Circuits (each connecting a CE device with a Provider Edge, PE, device) to a pseudowire (connecting the two PEs). In general, the Attachment Circuits must be of the same technology (e.g., both Ethernet, both ATM), and the pseudowire must carry the frames of that technology. However, if it is known that the frames' payload consists solely of IP datagrams, it is possible to provide a point-to-point connection in which the pseudowire connects Attachment Circuits of different technologies. This requires the PEs to perform a function known as "ARP Mediation". ARP Mediation refers to the process of resolving Layer 2 addresses when different resolution protocols are used on either Attachment Circuit. The methods described in this document are applicable even when the CEs run a routing protocol between them, as long as the routing protocol runs over IP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-arp-mediation-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-arp-mediation-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-3-6145630.I-D@ietf.org> --NextPart-- From mswathi@ceeyes.com Mon Mar 9 03:52:26 2009 Return-Path: <mswathi@ceeyes.com> 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 82F293A6BFC for <l2vpn@core3.amsl.com>; Mon, 9 Mar 2009 03:52:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 k5yNNZw8btQ7 for <l2vpn@core3.amsl.com>; Mon, 9 Mar 2009 03:52:25 -0700 (PDT) Received: from omr15.networksolutionsemail.com (omr15.networksolutionsemail.com [205.178.146.65]) by core3.amsl.com (Postfix) with ESMTP id 76F733A6BEC for <l2vpn@ietf.org>; Mon, 9 Mar 2009 03:52:25 -0700 (PDT) Received: from mail.networksolutionsemail.com (ns-omr15.mgt.hosting.dc2.netsol.com [10.49.6.78]) by omr15.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id n29AqwrK021953 for <l2vpn@ietf.org>; Mon, 9 Mar 2009 06:52:58 -0400 Received: (qmail 21192 invoked by uid 78); 9 Mar 2009 10:52:57 -0000 Received: from unknown (HELO csa17) (mswathi@ceeyes.com@59.162.168.79) by ns-omr15.lb.hosting.dc2.netsol.com with SMTP; 9 Mar 2009 10:52:57 -0000 Message-ID: <001c01c9a0a4$85c9b7c0$1183a8c0@ceeyes.com> From: "swathi" <mswathi@ceeyes.com> To: <l2vpn@ietf.org> Subject: Doubt on BGP based L2VPN Date: Mon, 9 Mar 2009 16:18:00 +0530 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=neXtPaRt_1236644443" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 09 Mar 2009 10:52:26 -0000 ------=neXtPaRt_1236644443 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01C9A0D2.9DE581D0" This is a multi-part message in MIME format. ------=_NextPart_000_0019_01C9A0D2.9DE581D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, In L2vpn autodiscovery what are the RT and RD's and what's = the exact format to advertise the vpn information to other pe's using = BGP. THANKS & REGARDS, M.Swathi, ------=_NextPart_000_0019_01C9A0D2.9DE581D0 Content-Type: text/html; charset="iso-8859-1" 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=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV> <DIV><FONT face=3DArial=20 size=3D2> &nbs= p; In=20 L2vpn autodiscovery what are the RT and RD's and what's the exact = format to=20 advertise the vpn information to other pe's using BGP.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>THANKS & REGARDS,<BR></FONT><FONT = face=3DArial=20 size=3D2>M.Swathi,<BR></FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML> ------=_NextPart_000_0019_01C9A0D2.9DE581D0-- ------=neXtPaRt_1236644443 Content-Type: text/plain; ************************* www.ceeyes.com ************************************** CONFIDENTIALITY AND DISCLAIMER NOTICE Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by e-mailing info@ceeyes.com, then delete the message from your system without making, distributing or retaining any copies of it. Any views or opinions presented are solely those of the sender and do not necessarily represent those of Ceeyes unless otherwise specifically stated. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message. ------=neXtPaRt_1236644443-- From hshah@ciena.com Mon Mar 9 11:27:36 2009 Return-Path: <hshah@ciena.com> 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 E766A28C261 for <l2vpn@core3.amsl.com>; Mon, 9 Mar 2009 11:27:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.722 X-Spam-Level: X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[AWL=0.877, 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 l0LDdj5Q6vN2 for <l2vpn@core3.amsl.com>; Mon, 9 Mar 2009 11:27:35 -0700 (PDT) Received: from hicks.ciena.com (hicks.ciena.com [63.118.34.22]) by core3.amsl.com (Postfix) with ESMTP id 62ED128C247 for <l2vpn@ietf.org>; Mon, 9 Mar 2009 11:27:30 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAGH8tEk/dicX/2dsb2JhbADROoQFBg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Subject: RE: IPDir Review of draft-ietf-l2vpn-arp-mediation-09.txt Date: Mon, 9 Mar 2009 14:10:14 -0400 Message-ID: <6535C9CED6F87446B41D20EF170F23622ACB3D@mamxm01.ciena.com> In-Reply-To: <7AF2A4E2-8971-46AB-9150-4014A0688F7C@thingmagic.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Importance: normal Priority: normal Thread-Topic: IPDir Review of draft-ietf-l2vpn-arp-mediation-09.txt Thread-Index: Acmg4ktWDGwZ8Eo/TderBA9BZLVWUA== References: <7AF2A4E2-8971-46AB-9150-4014A0688F7C@thingmagic.com> From: "Shah, Himanshu" <hshah@ciena.com> To: "Margaret Wasserman" <margaret@thingmagic.com>, <l2vpn@ietf.org> X-OriginalArrivalTime: 09 Mar 2009 18:10:15.0697 (UTC) FILETIME=[4C1FB810:01C9A0E2] Cc: Mark Townsley <townsley@cisco.com>, Himanshu Shah <hcshah@verizon.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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 09 Mar 2009 18:27:37 -0000 L2VPN Group, We have posted an updated version of the arp-mediation draft (draft-ietf-l2vpn-arp-mediation-10.txt) that addresses some=20 of the concerns raised by IPDir review. In summary,=20 1) the IPv6 support for ARP-Med is completely re-written (contributed by Neil Hart and Andrew Dolganow from Alcatel/Lucent). 2) Clarification texts added to address some of the concern listed=20 below 3) Minor Editorial changes We apologize for the super late response on the following IPDir review.=20 Please see the detailed comments in line... Also, please the review the new draft and provide comments before the meeting, if possible. /himanshu=20 -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Margaret Wasserman Sent: Friday, March 21, 2008 4:55 PM To: l2vpn@ietf.org Cc: Mark Townsley; Jari Arkko Subject: IPDir Review of draft-ietf-l2vpn-arp-mediation-09.txt NOTE: I am not on the L2VPN mailing list, so please include me explicitly on any discussion. Hi L2VPN Folks, At Mark Townsley's request, I performed an IP Directorate review of draft-ietf-l2vpn-arp-mediation-09.txt, paying special attention to the IPv6 portions of the document. I found three fairly major IPv6-related issues with the document: (1) This document makes the incorrect assumption an IPv6 host (non- router) will only have a single IP address associated with an interface. Virtually all IPv6 nodes will have more than one address per interface, and the mechanisms described in this document are incompatible with that fact in multiple ways: - If there is more than one IPv6 address in the IP Address List TLV, it is assumed that the first address is the address of the CE and the other addresses are "on-link addresses". - It is assumed that an Inverse Neighbor Discovery Advertisement will only contain a single address, when it actually contains an address list. - The PE operates on the assumption that there is a single CE with a single IP address, so once it discovers a single address during the "monitoring state", it communicates that address to the remote PE and thinks that discovery is complete. However, this is not valid for an IPv6 node that may have more than one address on the interface and may configure new addresses on that interface (such as IPv6 Privacy Addresses) at any time. (2) The document reflects a misunderstanding of the contents of an IPv6 Router Advertisement message, referring to "on-link addresses" =20 while the Router Advertisement actually contains on-link prefixes. =20 This misunderstanding is reflected in the format of the Address List TLV which does not include prefix lengths for the on-link prefixes. (3) I'd like to see some explanation of how this mechanism interacts with Duplicate Address Detection (DAD). I believe that DAD will only function on the AC and not across the PW. Will the PE-to-PE communication include a check that no address duplication has occurred? If not, is there a reason to believe that DAD isn't needed? himanshu> IPv6 section is completely re-written I also had concerns or questions about several other portions of the document: (4) The document says: "The establishment of the PW occurs independently from local CE IP address discovery. During the period when the PW has been established but the local CE IP device has not been discovered, only broadcast/multicast IP frames are propagated between the Attachment Circuit and pseudowire; unicast IP datagrams are dropped. The IP destination address is used to classify unicast/multicast packets." Why are unicast packets dropped during this phase? What are the implications of dropping these packets if, for example, the CE device is attempting to perform DHCP? himanshu> A clarifying text has been added to the draft. In a nutshell, remote PE can not process himanshu> unicast IP-DA packet if it does not have the link address of the attached CE. And note=20 himanshu> that IP-DA in the packet is not necessarily that of the attached CE. (5) The document also says: "The unicast IP frames are propagated between AC and pseudowire only when CE IP devices on both Attachment Circuits have been discovered, notified and proxy functions have completed." How will both sides know when the other side has completed these functions? himanshu> By way of exchanging the IP addresses of the local CE, each PE himanshu> now has adequate information to complete the proxy function with himanshu> the local CE. It is possible that a PE may get IP address himanshu> from the remote PE, advertise local CE's IP address to remote PE himanshu> and follows immediately with IP unicast data packet. There is a himanshu> small window here whereby remote PE has started the proxy function himanshu> but has not completed it but has started receiving IP data packets. himanshu> This should not be an issue, because at this point PE should have himanshu> local CE's link information (but CE may-not-yet-have-completed PE's himanshu> proxy function). This still allows unicast IP packets received over himanshu> PW to be sent out over local AC. (6) In section 5.1.4, the document says: "o The PE learns the IP address of the local CE from the Configure-Request received with the IP-Address option (0x03). The PE verifies that the IP address present in the IP-Address option is non-zero. If the IP address is zero, PE responds with Configure-Reject (as this is a request from CE to assign it an IP address). Also, the Configure- Reject copies the IP-Address option with a zero value to instruct the CE to not include that option in new Configure-Request. If the IP address is non-zero, PE responds with Configure-Ack." It also says: "The IPCP IP-Address option MAY be negotiated between the PE and the local CE device." This does not seem to be internally consistent. Up above, the document seems to indicate that the PE will reject a configure request with an IP address of zero (indicating a request to provide one) and in this paragraph it indicates that the IP-Address option may be "negotiated". What does this mean? himanshu> This only means that PE will not engage in assigning the IP address to local CE himanshu> The following text from the draft right below the bullet that you mention above himanshu> sheds more light on this. himanshu> ----- begin of text ---- =20 "o If the PE does not know the IP address of the remote CE,=20 it sends a Configure-Request without the IP-Address=20 option. =20 =20 o If the PE knows the IP address of the remote CE, it sends=20 a Configure-Request with the IP-Address option containing=20 the IP address of the remote CE. " himanshu> ---- end of text --- (7) In section 5.1.5, the document says: In order to learn the IP address of the CE device for a given Attachment Circuit, the PE device may execute Router Discovery Protocol [RFC 1256] whereby a Router Discovery Request (ICMP - router solicitation) message is sent using a source IP address of zero. Why is the router discovery packet sent with a source address of zero? himanshu> Because PE may not have remote CE's IP address that it can use as proxy as the source IP address (8) How would this mechanism interact with Secure Neighbor Discovery (SEND)? This issue should be covered in the security considerations section, IMO. I also found a few borderline-editorial issues that, IMO, merited a mention: (9) There is no reference for Inverse ND. You need to add RFC 3122 as a normative reference and refer to it in the appropriate location. himanshu>> fixed in the update. (10) The document says: "Address Family Two octet quantity containing a value from the ADDRESS FAMILY NUMBERS from ADDRESS FAMILY NUMBERS in [RFC 3232] that encodes the address contained in the Address field." There must be an IANA registry for this that it would be better to use than RFC 3232. himanshu> Those numbers are referenced, right below in the draft, exactly a paragraph below. himanshu> here is the text.. =20 himanshu> ----- begin of text ----- =20 The following address encodings are defined by this version of=20 the protocol: =20 =20 Address Family Address Encoding =20 =20 IPv4 (1) 4 octet full IPv4 address =20 IPv6 (2) Absent=20 himanshu> ------ end of text ------- (11) The reference to RFC 1256: ICMP Router Discovery Messages, should be normative not informative. himanshu>> fixed in the update (12) There are numerous "nits" in the document -- references in the abstract, acronyms that aren't expanded at first use, etc. You should address these in the next update. Margaret From Martin.Vigoureux@alcatel-lucent.com Tue Mar 10 03:11:18 2009 Return-Path: <Martin.Vigoureux@alcatel-lucent.com> 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 214A33A68F9; Tue, 10 Mar 2009 03:11:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 dnWKWYLBx1UC; Tue, 10 Mar 2009 03:11:17 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 221163A6920; Tue, 10 Mar 2009 03:11:16 -0700 (PDT) Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2AABDd7018043; Tue, 10 Mar 2009 11:11:47 +0100 Received: from [172.27.205.200] ([172.27.205.200]) by FRVELSBHS05.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.2499); Tue, 10 Mar 2009 11:11:34 +0100 Message-ID: <49B63CD6.6030200@alcatel-lucent.com> Date: Tue, 10 Mar 2009 11:11:34 +0100 From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Organization: Alcatel-Lucent User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: mpls@ietf.org, pwe3@ietf.org, ccamp@ops.ietf.org, l2vpn@ietf.org Subject: Time slots for IETF74 joint mpls-tp session Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Mar 2009 10:11:34.0906 (UTC) FILETIME=[979C8DA0:01C9A168] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Cc: mpls-tp@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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 10 Mar 2009 10:11:18 -0000 all, this is reminder. If you wish to have a presentation slot during the joint mpls-tp session, let me know. This session is planned Wednesday 25th, 09:00-11:30 am. martin From phe@soapstonenetworks.com Tue Mar 10 18:19:24 2009 Return-Path: <phe@soapstonenetworks.com> 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 90FD93A6828 for <l2vpn@core3.amsl.com>; Tue, 10 Mar 2009 18:19:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.949 X-Spam-Level: X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=2.650, 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 2Uy2-SbZjFIb for <l2vpn@core3.amsl.com>; Tue, 10 Mar 2009 18:19:23 -0700 (PDT) Received: from p01c12o141.mxlogic.net (p01c12o141.mxlogic.net [208.65.145.64]) by core3.amsl.com (Postfix) with ESMTP id 4F40F3A69BF for <l2vpn@ietf.org>; Tue, 10 Mar 2009 18:19:23 -0700 (PDT) Received: from unknown [12.230.177.130] (EHLO p01c12o141.mxlogic.net) by p01c12o141.mxlogic.net (mxl_mta-6.1.1-1) with ESMTP id eb117b94.2731608976.24904.00-501.p01c12o141.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 10 Mar 2009 19:19:59 -0600 (MDT) Received: from unknown [12.230.177.130] (EHLO smtp.soapstonenetworks.com) by p01c12o141.mxlogic.net (mxl_mta-6.1.1-1) over TLS secured channel with ESMTP id fa117b94.3749125008.24886.00-007.p01c12o141.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 10 Mar 2009 19:19:47 -0600 (MDT) Received: from corp-e2k7-mbx01.Soapstone.local ([172.24.2.72]) by corp-e2k7-hub01.Soapstone.local ([172.24.2.84]) with mapi; Tue, 10 Mar 2009 21:19:42 -0400 From: Peng He <phe@soapstonenetworks.com> To: "wim.henderickx@alcatel-lucent.be" <wim.henderickx@alcatel-lucent.be>, "florin.balus@alcatel-lucent.com" <florin.balus@alcatel-lucent.com> Date: Tue, 10 Mar 2009 21:19:42 -0400 Subject: RE: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt Thread-Topic: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt Thread-Index: Acmc4nGx2AfyZb8IQTejRnw2ugQ5kQFArW6G Message-ID: <E6D5CAC0ACC932498E6AC1A692E0CBA1229776F645@corp-e2k7-mbx01.Soapstone.local> References: <20090304160001.32BA528C3B5@core3.amsl.com> In-Reply-To: <20090304160001.32BA528C3B5@core3.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam: [F=0.2000000000; S=0.200(2009020301)] X-MAIL-FROM: <phe@soapstonenetworks.com> X-SOURCE-IP: [12.230.177.130] Cc: "l2vpn@ietf.org" <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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 11 Mar 2009 01:19:24 -0000 Hello Wim and Florin, I got a question regarding your newly-published I.D. 'BGP based Multi-homin= g in Virtual Private LAN Service': Given the following dual-homing CE to dual-homing CE scenario, suppose you = can not set-up full-meshed PWs among PE1-4 for whatever reason; PE1 can onl= y communicate to PE3 while PE2 can only communicate to PE4. Then I suppose = that a link failure in CE1 dual-homing may affect designated PE selection o= n the remote dual-homed CE2? or, the designated PE selections in the two du= al-homing CEs are not independent due to the non-full-meshed PW connections= . This is regarding your following statements: "3. BGP based Multi-homing procedures This section describes BGP based procedures for electing a designated forwarder among the set of PEs that are multi-homed to a customer site. Only the local PEs are actively participating in the selection algorithm. The PE(s) remote from the dual homed CE are not required to participate in the designated forwarding election for a remote dual-homed CE. " PE1---------------------PE3 / \ __/ \__ CE1 C= E2 __ __ \ / \ / PE2-----------------------PE4 Regards, Peng ________________________________________ From: i-d-announce-bounces@ietf.org [i-d-announce-bounces@ietf.org] On Beha= lf Of Internet-Drafts@ietf.org [Internet-Drafts@ietf.org] Sent: Wednesday, March 04, 2009 11:00 AM To: i-d-announce@ietf.org Subject: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : BGP based Multi-homing in Virtual Private LAN Ser= vice Author(s) : W. Henderickx, F. Balus Filename : draft-henderickx-l2vpn-vpls-multihoming-00.txt Pages : 11 Date : 2009-03-04 Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private Network (VPN) that gives its customers the appearance that their sites are connected via a Local Area Network (LAN). It is often required for the Service Provider (SP) to give the customer redundant connectivity to some sites, often called "multi-homing". This memo shows how multi-homing can be offered in the context of LDP-based VPLS using BGP-AD. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-henderickx-l2vpn-vpls-multihoming= -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 phe@soapstonenetworks.com Tue Mar 10 18:48:37 2009 Return-Path: <phe@soapstonenetworks.com> 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 C887828C12D for <l2vpn@core3.amsl.com>; Tue, 10 Mar 2009 18:48:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.832 X-Spam-Level: X-Spam-Status: No, score=-2.832 tagged_above=-999 required=5 tests=[AWL=-0.233, 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 ijdwX83Ubu+P for <l2vpn@core3.amsl.com>; Tue, 10 Mar 2009 18:48:37 -0700 (PDT) Received: from p01c11o142.mxlogic.net (p01c11o142.mxlogic.net [208.65.144.65]) by core3.amsl.com (Postfix) with ESMTP id D902E28C101 for <l2vpn@ietf.org>; Tue, 10 Mar 2009 18:48:36 -0700 (PDT) Received: from unknown [12.230.177.130] (EHLO p01c11o142.mxlogic.net) by p01c11o142.mxlogic.net (mxl_mta-6.1.1-1) with ESMTP id 89817b94.2726787984.2283.00-500.p01c11o142.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 10 Mar 2009 19:49:12 -0600 (MDT) Received: from unknown [12.230.177.130] (EHLO smtp.soapstonenetworks.com) by p01c11o142.mxlogic.net (mxl_mta-6.1.1-1) over TLS secured channel with ESMTP id d8817b94.2779237264.2280.00-002.p01c11o142.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 10 Mar 2009 19:49:08 -0600 (MDT) Received: from corp-e2k7-mbx01.Soapstone.local ([172.24.2.72]) by cratos.Soapstone.local ([172.24.2.65]) with mapi; Tue, 10 Mar 2009 21:49:00 -0400 From: Peng He <phe@soapstonenetworks.com> To: "song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn> Date: Tue, 10 Mar 2009 21:49:00 -0400 Subject: Questions about I.D. 'VPLS protection switching with ring access' Thread-Topic: Questions about I.D. 'VPLS protection switching with ring access' Thread-Index: AQHJoeuMCiBJKkxcrkiEX2icoC+JvA== Message-ID: <E6D5CAC0ACC932498E6AC1A692E0CBA1229776F646@corp-e2k7-mbx01.Soapstone.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam: [F=0.2000000000; S=0.200(2009020301)] X-MAIL-FROM: <phe@soapstonenetworks.com> X-SOURCE-IP: [12.230.177.130] Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn> 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 11 Mar 2009 01:48:37 -0000 Hello Xiaojun, I have a few questions about your ID of 'VPLS protection switching with rin= g access', which sounds like an interesting approach. 1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS CE'? 2. page 4, middle, by 'PE-CE-CE-PE forms a non-close ring', you mean 'PE1-C= E1-CE2-PE2' forms a non-close ring as a close ring should be ''PE1-CE1-CE2-= PE2-PE1'? 3. Both CE and PE can be a master node (there is only one at a time)? 4. What happens if a node, e.g., CE or PE, fails? What happens if a link/no= de is recovered from a failure? Seems to me that although there are many Ethernet ring protocols, but most = of the deployed ones are vendor-specified, expect G.8032, which does not su= pport overlapping rings yet. So it might be a little bit difficult for a VP= LS device vendor (L2.5/L3) to implement/emulate a L2 vendor's specific ring= protocol, unless everybody supports G.8032. =20 Regards, Peng= From wim.henderickx@alcatel-lucent.be Tue Mar 10 23:33:50 2009 Return-Path: <wim.henderickx@alcatel-lucent.be> 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 5C4603A6962 for <l2vpn@core3.amsl.com>; Tue, 10 Mar 2009 23:33:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 YB26OeCjtlXp for <l2vpn@core3.amsl.com>; Tue, 10 Mar 2009 23:33:49 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 2DE133A694A for <l2vpn@ietf.org>; Tue, 10 Mar 2009 23:33:48 -0700 (PDT) Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2B6YMEL016554; Wed, 11 Mar 2009 07:34:23 +0100 Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.54]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Wed, 11 Mar 2009 07:34:22 +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: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt Date: Wed, 11 Mar 2009 07:34:21 +0100 Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D704793E0A@FRVELSMBS22.ad2.ad.alcatel.com> In-Reply-To: <E6D5CAC0ACC932498E6AC1A692E0CBA1229776F645@corp-e2k7-mbx01.Soapstone.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt Thread-index: Acmc4nGx2AfyZb8IQTejRnw2ugQ5kQFArW6GAAuEgeA= References: <20090304160001.32BA528C3B5@core3.amsl.com> <E6D5CAC0ACC932498E6AC1A692E0CBA1229776F645@corp-e2k7-mbx01.Soapstone.local> From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> To: "Peng He" <phe@soapstonenetworks.com>, "BALUS Florin" <Florin.Balus@alcatel-lucent.com> X-OriginalArrivalTime: 11 Mar 2009 06:34:22.0732 (UTC) FILETIME=[6A3E5CC0:01C9A213] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 11 Mar 2009 06:33:50 -0000 Peng, We are assuming a full mesh PW otherwise there are dual failure scenario's which will result in loss as well. There are other mechanisms to solve this particular issue afaik. Cheers, Wim -----Original Message----- From: Peng He [mailto:phe@soapstonenetworks.com]=20 Sent: woensdag 11 maart 2009 2:20 To: HENDERICKX Wim; BALUS Florin Cc: l2vpn@ietf.org Subject: RE: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt=20 Hello Wim and Florin, I got a question regarding your newly-published I.D. 'BGP based Multi-homing in Virtual Private LAN Service': Given the following dual-homing CE to dual-homing CE scenario, suppose you can not set-up full-meshed PWs among PE1-4 for whatever reason; PE1 can only communicate to PE3 while PE2 can only communicate to PE4. Then I suppose that a link failure in CE1 dual-homing may affect designated PE selection on the remote dual-homed CE2? or, the designated PE selections in the two dual-homing CEs are not independent due to the non-full-meshed PW connections. This is regarding your following statements: "3. BGP based Multi-homing procedures This section describes BGP based procedures for electing a designated forwarder among the set of PEs that are multi-homed to a customer site. Only the local PEs are actively participating in the selection algorithm. The PE(s) remote from the dual homed CE are not required to participate in the designated forwarding election for a remote dual-homed CE. " PE1---------------------PE3 / \ __/ \__ CE1 CE2 __ __ \ / \ / PE2-----------------------PE4 Regards, Peng ________________________________________ From: i-d-announce-bounces@ietf.org [i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org [Internet-Drafts@ietf.org] Sent: Wednesday, March 04, 2009 11:00 AM To: i-d-announce@ietf.org Subject: I-D Action:draft-henderickx-l2vpn-vpls-multihoming-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : BGP based Multi-homing in Virtual Private LAN Service Author(s) : W. Henderickx, F. Balus Filename : draft-henderickx-l2vpn-vpls-multihoming-00.txt Pages : 11 Date : 2009-03-04 Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private Network (VPN) that gives its customers the appearance that their sites are connected via a Local Area Network (LAN). It is often required for the Service Provider (SP) to give the customer redundant connectivity to some sites, often called "multi-homing". This memo shows how multi-homing can be offered in the context of LDP-based VPLS using BGP-AD. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-henderickx-l2vpn-vpls-multihom ing-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 phe@soapstonenetworks.com Fri Mar 13 08:22:02 2009 Return-Path: <phe@soapstonenetworks.com> 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 D81883A687E for <l2vpn@core3.amsl.com>; Fri, 13 Mar 2009 08:22:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.128 X-Spam-Level: * X-Spam-Status: No, score=1.128 tagged_above=-999 required=5 tests=[AWL=-4.077, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_82=0.6, J_CHICKENPOX_83=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45] 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 LI8BOraBQudH for <l2vpn@core3.amsl.com>; Fri, 13 Mar 2009 08:21:56 -0700 (PDT) Received: from p01c11o149.mxlogic.net (p01c11o149.mxlogic.net [208.65.144.72]) by core3.amsl.com (Postfix) with ESMTP id E063F28C126 for <l2vpn@ietf.org>; Fri, 13 Mar 2009 08:21:55 -0700 (PDT) Received: from unknown [12.230.177.130] (EHLO p01c11o149.mxlogic.net) by p01c11o149.mxlogic.net (mxl_mta-6.1.1-1) with ESMTP id a3a7ab94.2723847056.5023.00-503.p01c11o149.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Fri, 13 Mar 2009 09:22:34 -0600 (MDT) Received: from unknown [12.230.177.130] (EHLO smtp.soapstonenetworks.com) by p01c11o149.mxlogic.net (mxl_mta-6.1.1-1) over TLS secured channel with ESMTP id a2a7ab94.3279809424.4978.00-004.p01c11o149.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Fri, 13 Mar 2009 09:22:26 -0600 (MDT) Received: from corp-e2k7-mbx01.Soapstone.local ([172.24.2.72]) by corp-e2k7-hub01.Soapstone.local ([172.24.2.84]) with mapi; Fri, 13 Mar 2009 11:22:17 -0400 From: Peng He <phe@soapstonenetworks.com> To: "song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn> Date: Fri, 13 Mar 2009 11:22:15 -0400 Subject: RE: Questions about I.D. 'VPLS protection switching with ring access' Thread-Topic: Questions about I.D. 'VPLS protection switching with ring access' Thread-Index: AcmjuhdvXNzHpNqOQ4eHs5BWiK8C1gAMBAfg Message-ID: <E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDCB@corp-e2k7-mbx01.Soapstone.local> References: <E6D5CAC0ACC932498E6AC1A692E0CBA1229776F646@corp-e2k7-mbx01.Soapstone.local> <OFD9CB0563.34726D3F-ON48257578.002D5803-48257578.0031342F@zte.com.cn> In-Reply-To: <OFD9CB0563.34726D3F-ON48257578.002D5803-48257578.0031342F@zte.com.cn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDCBcorpe2k7mbx01_" MIME-Version: 1.0 X-Spam: [F=0.2000000000; S=0.200(2009020301)] X-MAIL-FROM: <phe@soapstonenetworks.com> X-SOURCE-IP: [12.230.177.130] Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn> 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Fri, 13 Mar 2009 15:22:02 -0000 --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDCBcorpe2k7mbx01_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 WGlhb2p1YW4sDQoNClRoYW5rcyBmb3IgeW91ciByZXBseS4gIEJ1dCBJIGFtIG5vdCBnb25uYSBi ZSBpbiBJRVRGNzRAU2FuIEZyYW5DaXNjbywgc28gSSBwcmVmZXIgdG8gaGF2ZSBkaXNjdXNzaW9u IG9uIGxpbmUgOikNCg0KUGxlYXNlIHNlZSBpbi1saW5lLg0KDQoNClJlZ2FyZHMsDQpQZW5nDQoN CkZyb206IHNvbmcueGlhb2p1YW5AenRlLmNvbS5jbiBbbWFpbHRvOnNvbmcueGlhb2p1YW5AenRl LmNvbS5jbl0NClNlbnQ6IEZyaWRheSwgTWFyY2ggMTMsIDIwMDkgNTowMyBBTQ0KVG86IFBlbmcg SGUNCkNjOiBsMnZwbkBpZXRmLm9yZzsgc2hhby5ob25nQHp0ZS5jb20uY247IHd1LnNoYW95b25n QHp0ZS5jb20uY24NClN1YmplY3Q6ILTwuLQ6IFF1ZXN0aW9ucyBhYm91dCBJLkQuICdWUExTIHBy b3RlY3Rpb24gc3dpdGNoaW5nIHdpdGggcmluZyBhY2Nlc3MnDQoNCg0KIGhlbGxvLHBlbmcNCg0K ICAgICAgIHRoYW5rIGZvciB5b3VyIGF0dGVudGlvbiB0byBteSBkcmFmdC4NCg0KDQogICAgICAg MS4gcGFnZSAzLCBib3R0b20sIHlvdSB1c2UgdGhlIHRlcm0gJ1ZQTFMgQ0UnIHRvIGRpc3Rpbmd1 aXNoICdub24tVlBMUyBDRSc/DQoNCiAgICAgICAgICBhbnN3ZXKjuiAgeWVzLCB5b3UgYXJlIHJp Z2h0DQoNCiAgICAgICAyLiBwYWdlIDQsIG1pZGRsZSwgYnkgJ1BFLUNFLUNFLVBFIGZvcm1zIGEg bm9uLWNsb3NlIHJpbmcnLCB5b3UgbWVhbiAnUEUxLUNFMS1DRTItUEUyJyBmb3JtcyBhIG5vbi1j bG9zZSByaW5nIGFzIGEgY2xvc2UgcmluZyBzaG91bGQgYmUgJydQRTEtQ0UxLUNFMi1QRTItUEUx Jz8NCiAgICAgICAgIGFuc3dlcqO6IHllcyB0b28uDQoNCg0KICAgICAgMy4gQm90aCBDRSBhbmQg UEUgY2FuIGJlIGEgbWFzdGVyIG5vZGUgKHRoZXJlIGlzIG9ubHkgb25lIGF0IGEgdGltZSk/DQog ICAgICAgICAgYW5zd2VyOiAgYSByaW5nIG9ubHkgY2FuIGhhcyBvbmUgbWFzdGVyIG5vZGUgYXQg dGhlIHNhbWUgdGltZSAuDQoNCiAgICAgICA0LiBXaGF0IGhhcHBlbnMgaWYgYSBub2RlLCBlLmcu LCBDRSBvciBQRSwgZmFpbHM/IFdoYXQgaGFwcGVucyBpZiBhIGxpbmsvbm9kZSBpcyByZWNvdmVy ZWQgZnJvbSBhIGZhaWx1cmU/DQogICAgICAgICAgYW5zd2Vyo7ogaSBhbSBzb3JyeSB0aGF0ICBu b2RlIGZhaWx1cmUgIGFuZCBmYWlsdXIgcmVjb3ZlcnkgIGlzIG15IGxpdHRsZSBjb25jZXJuIGlu IHRoaXMgdmVyc2lvbjAudGhhbmsgeW91IGZvciB5b3VyIGNvbW1lbnQuDQoNCiAgICAgICAgICBi dXQgaSB0aGluayBpZiB5b3Ugd2FudCB0aGUgYW5zd2VyIG5vdyAsaSBjYW4gZXhwbGFpbiBicmll Zmx5IG5vdyAuDQoNCg0KICAgICAgICAgICAgICAgaW4gc2NlbmFyaW8gMSAsaWYgTk9ERSBDRSBp cyBkb3duICx0aGUgZmxvdyB3aWxsIGJlIGhhbHRlZCB3aXRob3V0IGRvdWJ0DQogICAgICAgICAg ICAgICAgICAgICAgICAgICAgICBpZiBOT0RFIFBFMSBpcyAgZG93biwgQ0UgY2FuIGRldGVjdCB0 aGUgZmFpbGx1cmUsc28gZG8gIHRoZSBzYW1lIGFjdGlvbiBhcyB0aGUgUEUtQ0UgbGluayBkb3du Lg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgaWYgTk9ERSBQRTIgaXMgIGRvd24gLHRo ZSBzYW1lIHdheSBhcyB0aGF0IFBFMSBpcyBkb3duDQpbUGVuZyBIZV0gd2hhdGV2ZXIgUEUxIG9y IFBFMiBmYWlscywgdGhlcmUgY291bGQgYmUgYSBtZWNoYW5pc20gdG8gaW5mb3JtIHRoZSBmYXIt ZW5kIFBFMyBvciBQRTQgdGhhdCBub3cgdGhlIKGuc2FtZaGvIHRyYWZmaWMgaXMgZnJvbSBQRTEg KG9yIFBFMikgaW5zdGVhZCBvZiBwcmV2aW91cyBQRTIgKG9yIFBFMSkuIFlvdSBtaWdodCBuZWVk IHRvIG1lbnRpb24gdGhpcyBpbiB5b3VyIG5leHQgdmVyc2lvbiBvZiB5b3VyIGRyYWZ0OyBhbmQg d2hhdCBpcyB0aGUgbWVjaGFuaXNtLiAodGhlcmUgYXJlIHNvbWUgSS5ELnMgdGFsa2luZyBhYm91 dCB0aGlzLCBjb25zaWRlcmluZyBQRTEgYW5kIFBFMiBhcyBhIGdyb3VwKQ0KDQogICAgICAgICAg ICAgIGluICBzY2VuYXJpbyAyLCBDRTEgaXMgYSBtYXN0ZXIsc28gIGlmIE5PREUgQ0UxIGlzIGRv d24gLHRoZSBmbG93IGZyb20gQ0UxIHdpbGwgaGFsdCB3aXRoIG5vIGRvdWJ0Lg0KW1BlbmcgSGVd IFllcy4gQnV0IEkgYW0gdGhpbmtpbmcgdG8gZnVsbHkgdGFrZSB0aGUgYWR2YW50YWdlcyBvZiBy aW5nLXRvcG9sb2d5IGFjY2VzcywgZS5nLiwgdGhlIHVzZXIgYWNjZXNzIGNhbiBhbHNvIGpvaW4g dGhlIHJpbmcsIGFzIHNob3duIGluIHlvdXIgc2NlbmFyaW8gMzsgb3IgdGhlIHVzZXJzIGhhdmUg YW5vdGhlciByaW5nKHMpIHRvIHNoYXJlIGEgbGluayB3aXRoIHRoZSChrmJvdW5kYXJ5IHJpbmeh ry4gQXMgc3VjaCwgd2hlbiBDRTEgb3IgQ0UyIGZhaWxzLCB0aGUgdXNlcnMgY2FuIHVzZSBDRTIg b3IgQ0UxLiAgIFdoYXQgZG8geW91IHRoaW5rIHJlZ2FyZGluZyBoYXZpbmcgYW4gaW5kZXBlbmRl bnQgcGFydGljdWxhciChrmJvdW5kYXJ5IHJpbmehryBvciBpdCBtaWdodCBiZSBiZXR0ZXIgdG8g bGV0IHRoZSB1c2VycyBqb2ludCB0aGUgoa5ib3VuZGFyeSByaW5noa8/DQpidXQgdGhlcmUgaXMg bm8NCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBjaGFuZ2UgZm9yIHRoZSBmbG93IGZyb20gQ0UyDQogICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgIGlmIE5PREUgUEUxIGlzIGRvd24sQ0UgY2FuIGRl dGVjdCB0aGUgZmFpbGx1cmUsc28gZG8gIHRoZSBzYW1lIGFjdGlvbiBhcyB0aGUgUEUtQ0UNCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBs aW5rIGRvd24uDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBpZiBOT0RFIENFMiBpcyBkb3duLENFIGNhbiBkZXRlY3QgdGhlIGZhaWxsdXJlLHRoZSBm bG93IGZyb20gQ0UyIHdpbGwgaGF1bHQgd2l0aA0KICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBubyBkb3VidC4gYnV0IHRoZXJlIGlzIG5v IGNoYW5nZSBmb3IgdGhlIGZsb3cgZnJvbSBDRTEuDQoNCiAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgIElGIE5PREUgUEUyIGlzIGRvd24sQ0UyIHdpbGwg ZGV0ZWN0IGl0IGFuZCBzZW50IG1lc3NhZ2UgdG8gbWFzdGVyIG5vZGUgQ0UxLG9wZW4NCiAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0aGUgQ0Ux LUNFMmxpbmsuDQoNCiAgICAgICAgICAgYXMgcmVnYXJkcyAgIGZhaWx1cmUgcmVjb3ZlcnksICBp ZiBmYWlsdXJlIGlzIGRldGVjdGVkIGRpc2FwcGVhciwgbWFzdGVyIHdpbGwgYmxvY2sgb25lIGxp bmsgY29ubmVjdGVkIGl0IGFnYWluLg0KW1BlbmcgSGVdIFRoaXMgaXMgd2hhdCBtb3N0IHJpbmcg cHJvdG9jb2xzIGRpZC4gTXkgcXVlc3Rpb24gaXMgaWYgdGhlIG1hc3RlciBub2RlIGJsb2NrcyB0 aGUgb3JpZ2luYWwgIKGuc2Vjb25kYXJ5oa8gcG9ydCBvciBibG9jayB0aGUgbmV3bHktcmVjb3Zl cmVkIHBvcnQ/IFVzdWFsbHkgdGhlIEwyIHJpbmcgcHJvdG9jb2xzIHdpbGwgYmxvY2sgdGhlIG9y aWdpbmFsIKGuc2Vjb25kYXJ5oa8gcG9ydCBhbmQgc2VuZCBUQyBub3RpZmljYXRpb24gbWVzc2Fn ZSB0byBmbGFzaCB0aGUgRkRCIHRhYmxlcy4gQnV0IGlmIHRoaXMgaXMgcmVhbGx5IG5lY2Vzc2Fy eSwgc2F5LCB5b3UgZ290IHRyYWZmaWMgbG9zcyBkdWUgdG8gYSBsaW5rL25vZGUgZmFpbHVyZSwg dGhhdCBpcyB3aGF0ZXZlciByZWFzb25hYmw7IGJ1dCB3aHkgc2hvdWxkIHlvdSBzdGlsbCBoYXZl IHRyYWZmaWMgbG9zcyBkdWUgdG8gYSBsaW5rL25vZGUgcmVjb3ZlcnksIHdoaWNoIHNlZW1zIHRv IGJlIGEgoa5nb29koa8gbmV3cz8NCg0KDQogICAgICAgICAgIHNvIGxhdGVyIGkgd2lsbCBhZGQg dGhlc2UgZGV0YWlsIHRvIG15IGRyYWZ0LnRoYW5rIHlvdSAuDQoNCiAgaSB3aWxsIGF0dGVuZCA3 NHRoIElFVEYgbWVldGluZ6OsaWYgeW91IHN0aWxsIGhhdmUgc29tZSBpbnRlcmVzdGUgLHdlIGNh biBkaXNjdXNzIHRoZXJlLg0KDQoNCg0KUGVuZyBIZSA8cGhlQHNvYXBzdG9uZW5ldHdvcmtzLmNv bT4NCg0KMjAwOS0wMy0xMSAwOTo0OQ0KDQrK1bz+yMsNCg0KInNvbmcueGlhb2p1YW5AenRlLmNv bS5jbiIgPHNvbmcueGlhb2p1YW5AenRlLmNvbS5jbj4NCg0Ks63LzQ0KDQoid3Uuc2hhb3lvbmdA enRlLmNvbS5jbiIgPHd1LnNoYW95b25nQHp0ZS5jb20uY24+LCAic2hhby5ob25nQHp0ZS5jb20u Y24iIDxzaGFvLmhvbmdAenRlLmNvbS5jbj4sICJsMnZwbkBpZXRmLm9yZyIgPGwydnBuQGlldGYu b3JnPg0KDQrW98ziDQoNClF1ZXN0aW9ucyBhYm91dCBJLkQuICdWUExTIHByb3RlY3Rpb24gc3dp dGNoaW5nIHdpdGggcmluZyBhY2Nlc3MnDQoNCg0KDQoNCg0KDQoNCkhlbGxvIFhpYW9qdW4sDQoN CkkgaGF2ZSBhIGZldyBxdWVzdGlvbnMgYWJvdXQgeW91ciBJRCBvZiAnVlBMUyBwcm90ZWN0aW9u IHN3aXRjaGluZyB3aXRoIHJpbmcgYWNjZXNzJywgd2hpY2ggc291bmRzIGxpa2UgYW4gaW50ZXJl c3RpbmcgYXBwcm9hY2guDQoNCjEuIHBhZ2UgMywgYm90dG9tLCB5b3UgdXNlIHRoZSB0ZXJtICdW UExTIENFJyB0byBkaXN0aW5ndWlzaCAnbm9uLVZQTFMgQ0UnPw0KDQoyLiBwYWdlIDQsIG1pZGRs ZSwgYnkgJ1BFLUNFLUNFLVBFIGZvcm1zIGEgbm9uLWNsb3NlIHJpbmcnLCB5b3UgbWVhbiAnUEUx LUNFMS1DRTItUEUyJyBmb3JtcyBhIG5vbi1jbG9zZSByaW5nIGFzIGEgY2xvc2UgcmluZyBzaG91 bGQgYmUgJydQRTEtQ0UxLUNFMi1QRTItUEUxJz8NCg0KMy4gQm90aCBDRSBhbmQgUEUgY2FuIGJl IGEgbWFzdGVyIG5vZGUgKHRoZXJlIGlzIG9ubHkgb25lIGF0IGEgdGltZSk/DQoNCjQuIFdoYXQg aGFwcGVucyBpZiBhIG5vZGUsIGUuZy4sIENFIG9yIFBFLCBmYWlscz8gV2hhdCBoYXBwZW5zIGlm IGEgbGluay9ub2RlIGlzIHJlY292ZXJlZCBmcm9tIGEgZmFpbHVyZT8NCg0KU2VlbXMgdG8gbWUg dGhhdCBhbHRob3VnaCB0aGVyZSBhcmUgbWFueSBFdGhlcm5ldCByaW5nIHByb3RvY29scywgYnV0 IG1vc3Qgb2YgdGhlIGRlcGxveWVkIG9uZXMgYXJlIHZlbmRvci1zcGVjaWZpZWQsIGV4cGVjdCBH LjgwMzIsIHdoaWNoIGRvZXMgbm90IHN1cHBvcnQgb3ZlcmxhcHBpbmcgcmluZ3MgeWV0LiBTbyBp dCBtaWdodCBiZSBhIGxpdHRsZSBiaXQgZGlmZmljdWx0IGZvciBhIFZQTFMgZGV2aWNlIHZlbmRv ciAoTDIuNS9MMykgdG8gaW1wbGVtZW50L2VtdWxhdGUgYSBMMiB2ZW5kb3IncyBzcGVjaWZpYyBy aW5nIHByb3RvY29sLCB1bmxlc3MgZXZlcnlib2R5IHN1cHBvcnRzIEcuODAzMi4NCg0KDQpSZWdh cmRzLA0KUGVuZw0KDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0NCg0KWlRFIEluZm9ybWF0aW9uIFNlY3VyaXR5IE5vdGljZTogVGhl IGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMgc29sZWx5IHByb3BlcnR5IG9m IHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uIGlzIGNv bmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1lZCBhYm92ZSBhcmUgb2JsaWdhdGVkIHRvIG1haW50 YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVybWl0dGVkIHRvIGRpc2Nsb3NlIHRoZSBjb250ZW50 cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8gb3RoZXJzLg0KDQpUaGlzIGVtYWlsIGFuZCBhbnkg ZmlsZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCBz b2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdob20gdGhl eSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9y IHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YgdGhlIG1lc3NhZ2UuIEFueSB2aWV3cyBl eHByZXNzZWQgaW4gdGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBvZiB0aGUgaW5kaXZpZHVhbCBzZW5k ZXIuDQoNClRoaXMgbWVzc2FnZSBoYXMgYmVlbiBzY2FubmVkIGZvciB2aXJ1c2VzIGFuZCBTcGFt IGJ5IFpURSBBbnRpLVNwYW0gc3lzdGVtLg0K --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDCBcorpe2k7mbx01_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m= icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office= :access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"= uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof= t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co= m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee= t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns= :odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro= soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln= s:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D= "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"http://sc= hemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schemas.micro= soft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2000/09/= xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" xmlns:u= dc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www.w3.org= /2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/= 2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"= http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.micro= soft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-in= stance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xmlns:udc= xf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http:/= /schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.micr= osoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.microsoft= .com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsoft.com/o= ffice/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/package= /2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats.org/ma= rkup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/200= 4/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/re= lationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" xm= lns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types" xml= ns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messages" x= mlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" x= mlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Publis= hedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"" x= mlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"> <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> <style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @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;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:"\@SimSun"; panose-1:2 1 6 0 3 1 1 1 1 1;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:SimSun;} 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:SimSun;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:SimSun;} tt {mso-style-priority:99; font-family:SimSun;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:Consolas;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only;} @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'>Xiaojuan,<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> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Thanks for your reply. But I am not gonna be in IETF74= @San FranCisco, so I prefer to have discussion on line </span><span style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><spa= n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'= ><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> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Please see in-line.<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> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Regards,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Peng<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> </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"'> song.xiaojuan@zte.com.cn [mailto:song.xiaojuan@zte.com.cn] <br> <b>Sent:</b> Friday, March 13, 2009 5:03 AM<br> <b>To:</b> Peng He<br> <b>Cc:</b> l2vpn@ietf.org; shao.hong@zte.com.cn; wu.shaoyong@zte.com.cn<br> <b>Subject:</b> </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=B4=F0= =B8=B4</span><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>: Questions ab= out I.D. 'VPLS protection switching with ring access'<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> hel= lo,peng</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; thank for your attention to my draft.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><tt>1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS CE'?</tt> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > answer</span><span lang=3DZH-CN style=3D'font-s= ize: 10.0pt;color:red'>=A3=BA</span><span style=3D'font-size:10.0pt;font-family:= "Arial","sans-serif"; color:red'> yes, you are right</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><tt>2. page 4, middle, by 'PE-CE-CE-PE forms a non-clos= e ring', you mean 'PE1-CE1-CE2-PE2' forms a non-close ring as a close ring sh= ould be ''PE1-CE1-CE2-PE2-PE1'?</tt> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; <span style=3D'color:red'> answer</span></span><span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style= =3D'font-size: 10.0pt;font-family:"Arial","sans-serif";color:red'> yes too.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <tt> 3. Both CE and PE can be a master node (there is o= nly one at a time)?</tt> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > answer:</span><tt><span style=3D'color:blue'> <= /span><span style=3D'color:red'> </span></tt><span style=3D'font-size:10.0pt;font-= family: "Arial","sans-serif";color:red'>a ring only can has one master node at the = same time .</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><tt> 4. What happens if a node, e.g., CE or PE, fails? W= hat happens if a link/node is recovered from a failure?</tt> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; <span style=3D'color:red'> answer</span></span><span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style= =3D'font-size: 10.0pt;font-family:"Arial","sans-serif";color:red'> i am sorry that n= ode failure and failur recovery is my little concern in this version0.thank you for your comment.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > but i think if you want the answer now ,i can explain briefly now .</span> <br> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > in scenario 1 ,if NODE CE i= s down ,the flow will be halted without doubt</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ; if NODE PE1 is down, CE can detect the faillure,= so do the same action as the PE-CE link down.</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ; if NODE PE2 is down ,the same way as that PE1 is down</span> <span style=3D'color:#1F497D'><o:p></o:p></span></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><i><span style=3D'fo= nt-size: 11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Peng He] whatever= PE1 or PE2 fails, there could be a mechanism to inform the far-end PE3 or PE4 t= hat now the =A1=AEsame=A1=AF traffic is from PE1 (or PE2) instead of previous P= E2 (or PE1). You might need to mention this in your next version of your draft; and what= is the mechanism. (there are some I.D.s talking about this, considering PE1 an= d PE2 as a group)<o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > in scenario 2, CE1 is a master,so if NODE CE1 is down ,the flow from CE1 will halt with no do= ubt.</span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><= o:p></o:p></span></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><i><span style=3D'fo= nt-size: 11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Peng He] Yes. But= I am thinking to fully take the advantages of ring-topology access, e.g., the user access can also join the ring, as shown in your scenario 3; or the use= rs have another ring(s) to share a link with the =A1=AEboundary ring=A1=AF. As= such, when CE1 or CE2 fails, the users can use CE2 or CE1. What do you think regarding having an independent particular =A1=AEboundary ring=A1=AF or it = might be better to let the users joint the =A1=AEboundary ring=A1=AF?<o:p></o:p></span></i>= </b></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'font-siz= e:10.0pt; font-family:"Arial","sans-serif";color:red'>but there is no </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; change for the flow from CE2</spa= n> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; if NODE PE1 is down,CE can detect the faillure,so do th= e same action as the PE-CE</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; link down.</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; if NODE CE2 is down,CE can detect the faillure,the flow from CE2 will hault with </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; no doubt. but there is no change for the flow from CE1.</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > </span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; IF NODE PE2 is down,CE2 will detect it and sent message= to master node CE1,open </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; the CE1-CE2link. </span><br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > as regards failure recovery,  = ;if failure is detected disappear, master will block one link connected it agai= n.</span> <span style=3D'color:#1F497D'><o:p></o:p></span></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><i><span style=3D'fo= nt-size: 11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>[Peng He] This is = what most ring protocols did. My question is if the master node blocks the original =A1=AEsecondary=A1=AF port or block the newly-recovered port= ? Usually the L2 ring protocols will block the original =A1=AEsecondary=A1=AF port and se= nd TC notification message to flash the FDB tables. But if this is really necessa= ry, say, you got traffic loss due to a link/node failure, that is whatever reasonabl; but why should you still have traffic loss due to a link/node re= covery, which seems to be a =A1=AEgood=A1=AF news?<o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; <span style=3D'color:red'> so later i will add th= ese detail to my draft.thank you .</span></span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> i = will attend 74th IETF meeting</span><span lang=3DZH-CN style=3D'font-size:10.0pt= '>=A3=AC</span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>if you still ha= ve some intereste ,we can discuss there. </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span> <br> <br> <br> <o:p></o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td width=3D"26%" valign=3Dtop style=3D'width:26.0%;padding:.75pt .75pt .= 75pt .75pt'> <p class=3DMsoNormal><b><span style=3D'font-size:7.5pt;font-family:"Arial= ","sans-serif"'>Peng He <phe@soapstonenetworks.com></span></b><span style=3D'font-size:7= .5pt; font-family:"Arial","sans-serif"'> </span><o:p></o:p></p> <p><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>2009-= 03-11 09:49</span> <o:p></o:p></p> </td> <td width=3D"73%" valign=3Dtop style=3D'width:73.0%;padding:.75pt .75pt .= 75pt .75pt'> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=CA=D5=BC=FE=C8=CB</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=B3=AD=CB=CD</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn>, "shao.hong@zte.com.cn" <shao.hong@zte.com.cn>, "l2vpn@ietf.org" <l2vpn@ietf.org></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=D6=F7=CC=E2</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>Questions about I.D. 'VPLS protection switching with ring access'</span><o:p></o:= p></p> </td> </tr> </table> <p class=3DMsoNormal><o:p> </o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td> </tr> </table> </td> </tr> </table> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <br> <br> <tt>Hello Xiaojun,</tt><br> <br> <tt>I have a few questions about your ID of 'VPLS protection switching with ring access', which sounds like an interesting approach.</tt><br> <br> <tt>1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS = CE'?</tt><br> <br> <tt>2. page 4, middle, by 'PE-CE-CE-PE forms a non-close ring', you mean 'PE1-CE1-CE2-PE2' forms a non-close ring as a close ring should be ''PE1-CE1-CE2-PE2-PE1'?</tt><br> <br> <tt>3. Both CE and PE can be a master node (there is only one at a time)?</= tt><br> <br> <tt>4. What happens if a node, e.g., CE or PE, fails? What happens if a link/node is recovered from a failure?</tt><br> <br> <tt>Seems to me that although there are many Ethernet ring protocols, but m= ost of the deployed ones are vendor-specified, expect G.8032, which does not support overlapping rings yet. So it might be a little bit difficult for a = VPLS device vendor (L2.5/L3) to implement/emulate a L2 vendor's specific ring protocol, unless everybody supports G.8032. </tt><br> <br> <br> <tt>Regards,</tt><br> <tt>Peng</tt> <o:p></o:p></p> <pre><o:p> </o:p></pre><pre>------------------------------------------= --------------<o:p></o:p></pre><pre>ZTE Information Security = ;Notice: The information contained in this ma= il is solely property of the sender's or= ganization. This mail communication is confidentia= l. Recipients named above are obligated to&nb= sp;maintain secrecy and are not permitted to&= nbsp;disclose the contents of this communication&n= bsp;to others.<o:p></o:p></pre><pre>This email and any&= nbsp;files transmitted with it are confidential&nb= sp;and intended solely for the use of th= e individual or entity to whom they are&= nbsp;addressed. If you have received this ema= il in error please notify the originator = ;of the message. Any views expressed in = this message are those of the individual = ;sender.<o:p></o:p></pre><pre>This message has been sca= nned for viruses and Spam by ZTE Anti-Sp= am system.<o:p></o:p></pre></div> </div> </body> </html> --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDCBcorpe2k7mbx01_-- From phe@soapstonenetworks.com Fri Mar 13 08:33:22 2009 Return-Path: <phe@soapstonenetworks.com> 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 889F628C167 for <l2vpn@core3.amsl.com>; Fri, 13 Mar 2009 08:33:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.243 X-Spam-Level: X-Spam-Status: No, score=0.243 tagged_above=-999 required=5 tests=[AWL=-1.562, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_82=0.6, J_CHICKENPOX_83=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 PxHX93YH0zet for <l2vpn@core3.amsl.com>; Fri, 13 Mar 2009 08:33:16 -0700 (PDT) Received: from p01c12o141.mxlogic.net (p01c12o141.mxlogic.net [208.65.145.64]) by core3.amsl.com (Postfix) with ESMTP id 5FCA828C114 for <l2vpn@ietf.org>; Fri, 13 Mar 2009 08:33:00 -0700 (PDT) Received: from unknown [12.230.177.130] (EHLO p01c12o141.mxlogic.net) by p01c12o141.mxlogic.net (mxl_mta-6.1.1-1) with ESMTP id 2dc7ab94.2727607184.22953.00-501.p01c12o141.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Fri, 13 Mar 2009 09:33:39 -0600 (MDT) Received: from unknown [12.230.177.130] (EHLO smtp.soapstonenetworks.com) by p01c12o141.mxlogic.net (mxl_mta-6.1.1-1) over TLS secured channel with ESMTP id 0cc7ab94.3063282576.22893.00-002.p01c12o141.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Fri, 13 Mar 2009 09:33:28 -0600 (MDT) Received: from corp-e2k7-mbx01.Soapstone.local ([172.24.2.72]) by cratos.Soapstone.local ([172.24.2.65]) with mapi; Fri, 13 Mar 2009 11:33:19 -0400 From: Peng He <phe@soapstonenetworks.com> To: "song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn> Date: Fri, 13 Mar 2009 11:33:18 -0400 Subject: RE: Questions about I.D. 'VPLS protection switching with ring access' Thread-Topic: Questions about I.D. 'VPLS protection switching with ring access' Thread-Index: AcmjuhdvXNzHpNqOQ4eHs5BWiK8C1gANpyRw Message-ID: <E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDD0@corp-e2k7-mbx01.Soapstone.local> References: <E6D5CAC0ACC932498E6AC1A692E0CBA1229776F646@corp-e2k7-mbx01.Soapstone.local> <OFD9CB0563.34726D3F-ON48257578.002D5803-48257578.0031342F@zte.com.cn> In-Reply-To: <OFD9CB0563.34726D3F-ON48257578.002D5803-48257578.0031342F@zte.com.cn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDD0corpe2k7mbx01_" MIME-Version: 1.0 X-Spam: [F=0.2000000000; S=0.200(2009020301)] X-MAIL-FROM: <phe@soapstonenetworks.com> X-SOURCE-IP: [12.230.177.130] Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn> 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Fri, 13 Mar 2009 15:33:22 -0000 --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDD0corpe2k7mbx01_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 T25lIG1vcmU6IGhvdyB5b3UgaW1wbGVtZW50IHRoZSByaW5nLWxpbmsgYmV0d2VlbiBQRTEgYW5k IFBFMiwgUFdFIGVtdWxhdGVkLCBhbmQgY2FuIGJlIHVzZWQgYnkgbm9uLXVzZXItcmVsYXRlZCBk YXRhIGFsc28gb3Igbm90PyBPciBpdCBpcyBhbiBpbmRlcGVuZGVudCBsaW5rIG9ubHkgZm9yIHJp bmcgdXNhZ2U/DQoNCg0KUmVnYXJkcywNClBlbmcNCg0KRnJvbTogc29uZy54aWFvanVhbkB6dGUu Y29tLmNuIFttYWlsdG86c29uZy54aWFvanVhbkB6dGUuY29tLmNuXQ0KU2VudDogRnJpZGF5LCBN YXJjaCAxMywgMjAwOSA1OjAzIEFNDQpUbzogUGVuZyBIZQ0KQ2M6IGwydnBuQGlldGYub3JnOyBz aGFvLmhvbmdAenRlLmNvbS5jbjsgd3Uuc2hhb3lvbmdAenRlLmNvbS5jbg0KU3ViamVjdDogtPC4 tDogUXVlc3Rpb25zIGFib3V0IEkuRC4gJ1ZQTFMgcHJvdGVjdGlvbiBzd2l0Y2hpbmcgd2l0aCBy aW5nIGFjY2VzcycNCg0KDQogaGVsbG8scGVuZw0KDQogICAgICAgdGhhbmsgZm9yIHlvdXIgYXR0 ZW50aW9uIHRvIG15IGRyYWZ0Lg0KDQoNCiAgICAgICAxLiBwYWdlIDMsIGJvdHRvbSwgeW91IHVz ZSB0aGUgdGVybSAnVlBMUyBDRScgdG8gZGlzdGluZ3Vpc2ggJ25vbi1WUExTIENFJz8NCg0KICAg ICAgICAgIGFuc3dlcqO6ICB5ZXMsIHlvdSBhcmUgcmlnaHQNCg0KICAgICAgIDIuIHBhZ2UgNCwg bWlkZGxlLCBieSAnUEUtQ0UtQ0UtUEUgZm9ybXMgYSBub24tY2xvc2UgcmluZycsIHlvdSBtZWFu ICdQRTEtQ0UxLUNFMi1QRTInIGZvcm1zIGEgbm9uLWNsb3NlIHJpbmcgYXMgYSBjbG9zZSByaW5n IHNob3VsZCBiZSAnJ1BFMS1DRTEtQ0UyLVBFMi1QRTEnPw0KICAgICAgICAgYW5zd2Vyo7ogeWVz IHRvby4NCg0KDQogICAgICAzLiBCb3RoIENFIGFuZCBQRSBjYW4gYmUgYSBtYXN0ZXIgbm9kZSAo dGhlcmUgaXMgb25seSBvbmUgYXQgYSB0aW1lKT8NCiAgICAgICAgICBhbnN3ZXI6ICBhIHJpbmcg b25seSBjYW4gaGFzIG9uZSBtYXN0ZXIgbm9kZSBhdCB0aGUgc2FtZSB0aW1lIC4NCg0KICAgICAg IDQuIFdoYXQgaGFwcGVucyBpZiBhIG5vZGUsIGUuZy4sIENFIG9yIFBFLCBmYWlscz8gV2hhdCBo YXBwZW5zIGlmIGEgbGluay9ub2RlIGlzIHJlY292ZXJlZCBmcm9tIGEgZmFpbHVyZT8NCiAgICAg ICAgICBhbnN3ZXKjuiBpIGFtIHNvcnJ5IHRoYXQgIG5vZGUgZmFpbHVyZSAgYW5kIGZhaWx1ciBy ZWNvdmVyeSAgaXMgbXkgbGl0dGxlIGNvbmNlcm4gaW4gdGhpcyB2ZXJzaW9uMC50aGFuayB5b3Ug Zm9yIHlvdXIgY29tbWVudC4NCg0KICAgICAgICAgIGJ1dCBpIHRoaW5rIGlmIHlvdSB3YW50IHRo ZSBhbnN3ZXIgbm93ICxpIGNhbiBleHBsYWluIGJyaWVmbHkgbm93IC4NCg0KDQogICAgICAgICAg ICAgICBpbiBzY2VuYXJpbyAxICxpZiBOT0RFIENFIGlzIGRvd24gLHRoZSBmbG93IHdpbGwgYmUg aGFsdGVkIHdpdGhvdXQgZG91YnQNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGlmIE5P REUgUEUxIGlzICBkb3duLCBDRSBjYW4gZGV0ZWN0IHRoZSBmYWlsbHVyZSxzbyBkbyAgdGhlIHNh bWUgYWN0aW9uIGFzIHRoZSBQRS1DRSBsaW5rIGRvd24uDQogICAgICAgICAgICAgICAgICAgICAg ICAgICAgICBpZiBOT0RFIFBFMiBpcyAgZG93biAsdGhlIHNhbWUgd2F5IGFzIHRoYXQgUEUxIGlz IGRvd24NCiAgICAgICAgICAgICAgaW4gIHNjZW5hcmlvIDIsIENFMSBpcyBhIG1hc3RlcixzbyAg aWYgTk9ERSBDRTEgaXMgZG93biAsdGhlIGZsb3cgZnJvbSBDRTEgd2lsbCBoYWx0IHdpdGggbm8g ZG91YnQuYnV0IHRoZXJlIGlzIG5vDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgY2hhbmdlIGZvciB0aGUgZmxvdyBmcm9tIENFMg0KICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBpZiBOT0RFIFBF MSBpcyBkb3duLENFIGNhbiBkZXRlY3QgdGhlIGZhaWxsdXJlLHNvIGRvICB0aGUgc2FtZSBhY3Rp b24gYXMgdGhlIFBFLUNFDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgbGluayBkb3duLg0KICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgaWYgTk9ERSBDRTIgaXMgZG93bixDRSBjYW4gZGV0ZWN0 IHRoZSBmYWlsbHVyZSx0aGUgZmxvdyBmcm9tIENFMiB3aWxsIGhhdWx0IHdpdGgNCiAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgbm8gZG91 YnQuIGJ1dCB0aGVyZSBpcyBubyBjaGFuZ2UgZm9yIHRoZSBmbG93IGZyb20gQ0UxLg0KDQogICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBJRiBOT0RFIFBF MiBpcyBkb3duLENFMiB3aWxsIGRldGVjdCBpdCBhbmQgc2VudCBtZXNzYWdlIHRvIG1hc3RlciBu b2RlIENFMSxvcGVuDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgdGhlIENFMS1DRTJsaW5rLg0KDQogICAgICAgICAgIGFzIHJlZ2FyZHMgICBm YWlsdXJlIHJlY292ZXJ5LCAgaWYgZmFpbHVyZSBpcyBkZXRlY3RlZCBkaXNhcHBlYXIsIG1hc3Rl ciB3aWxsIGJsb2NrIG9uZSBsaW5rIGNvbm5lY3RlZCBpdCBhZ2Fpbi4NCg0KICAgICAgICAgICBz byBsYXRlciBpIHdpbGwgYWRkIHRoZXNlIGRldGFpbCB0byBteSBkcmFmdC50aGFuayB5b3UgLg0K DQogIGkgd2lsbCBhdHRlbmQgNzR0aCBJRVRGIG1lZXRpbmejrGlmIHlvdSBzdGlsbCBoYXZlIHNv bWUgaW50ZXJlc3RlICx3ZSBjYW4gZGlzY3VzcyB0aGVyZS4NCg0KDQoNClBlbmcgSGUgPHBoZUBz b2Fwc3RvbmVuZXR3b3Jrcy5jb20+DQoNCjIwMDktMDMtMTEgMDk6NDkNCg0KytW8/sjLDQoNCiJz b25nLnhpYW9qdWFuQHp0ZS5jb20uY24iIDxzb25nLnhpYW9qdWFuQHp0ZS5jb20uY24+DQoNCrOt y80NCg0KInd1LnNoYW95b25nQHp0ZS5jb20uY24iIDx3dS5zaGFveW9uZ0B6dGUuY29tLmNuPiwg InNoYW8uaG9uZ0B6dGUuY29tLmNuIiA8c2hhby5ob25nQHp0ZS5jb20uY24+LCAibDJ2cG5AaWV0 Zi5vcmciIDxsMnZwbkBpZXRmLm9yZz4NCg0K1vfM4g0KDQpRdWVzdGlvbnMgYWJvdXQgSS5ELiAn VlBMUyBwcm90ZWN0aW9uIHN3aXRjaGluZyB3aXRoIHJpbmcgYWNjZXNzJw0KDQoNCg0KDQoNCg0K DQpIZWxsbyBYaWFvanVuLA0KDQpJIGhhdmUgYSBmZXcgcXVlc3Rpb25zIGFib3V0IHlvdXIgSUQg b2YgJ1ZQTFMgcHJvdGVjdGlvbiBzd2l0Y2hpbmcgd2l0aCByaW5nIGFjY2VzcycsIHdoaWNoIHNv dW5kcyBsaWtlIGFuIGludGVyZXN0aW5nIGFwcHJvYWNoLg0KDQoxLiBwYWdlIDMsIGJvdHRvbSwg eW91IHVzZSB0aGUgdGVybSAnVlBMUyBDRScgdG8gZGlzdGluZ3Vpc2ggJ25vbi1WUExTIENFJz8N Cg0KMi4gcGFnZSA0LCBtaWRkbGUsIGJ5ICdQRS1DRS1DRS1QRSBmb3JtcyBhIG5vbi1jbG9zZSBy aW5nJywgeW91IG1lYW4gJ1BFMS1DRTEtQ0UyLVBFMicgZm9ybXMgYSBub24tY2xvc2UgcmluZyBh cyBhIGNsb3NlIHJpbmcgc2hvdWxkIGJlICcnUEUxLUNFMS1DRTItUEUyLVBFMSc/DQoNCjMuIEJv dGggQ0UgYW5kIFBFIGNhbiBiZSBhIG1hc3RlciBub2RlICh0aGVyZSBpcyBvbmx5IG9uZSBhdCBh IHRpbWUpPw0KDQo0LiBXaGF0IGhhcHBlbnMgaWYgYSBub2RlLCBlLmcuLCBDRSBvciBQRSwgZmFp bHM/IFdoYXQgaGFwcGVucyBpZiBhIGxpbmsvbm9kZSBpcyByZWNvdmVyZWQgZnJvbSBhIGZhaWx1 cmU/DQoNClNlZW1zIHRvIG1lIHRoYXQgYWx0aG91Z2ggdGhlcmUgYXJlIG1hbnkgRXRoZXJuZXQg cmluZyBwcm90b2NvbHMsIGJ1dCBtb3N0IG9mIHRoZSBkZXBsb3llZCBvbmVzIGFyZSB2ZW5kb3It c3BlY2lmaWVkLCBleHBlY3QgRy44MDMyLCB3aGljaCBkb2VzIG5vdCBzdXBwb3J0IG92ZXJsYXBw aW5nIHJpbmdzIHlldC4gU28gaXQgbWlnaHQgYmUgYSBsaXR0bGUgYml0IGRpZmZpY3VsdCBmb3Ig YSBWUExTIGRldmljZSB2ZW5kb3IgKEwyLjUvTDMpIHRvIGltcGxlbWVudC9lbXVsYXRlIGEgTDIg dmVuZG9yJ3Mgc3BlY2lmaWMgcmluZyBwcm90b2NvbCwgdW5sZXNzIGV2ZXJ5Ym9keSBzdXBwb3J0 cyBHLjgwMzIuDQoNCg0KUmVnYXJkcywNClBlbmcNCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClpURSBJbmZvcm1hdGlvbiBT ZWN1cml0eSBOb3RpY2U6IFRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWlsIGlz IHNvbGVseSBwcm9wZXJ0eSBvZiB0aGUgc2VuZGVyJ3Mgb3JnYW5pemF0aW9uLiBUaGlzIG1haWwg Y29tbXVuaWNhdGlvbiBpcyBjb25maWRlbnRpYWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJl IG9ibGlnYXRlZCB0byBtYWludGFpbiBzZWNyZWN5IGFuZCBhcmUgbm90IHBlcm1pdHRlZCB0byBk aXNjbG9zZSB0aGUgY29udGVudHMgb2YgdGhpcyBjb21tdW5pY2F0aW9uIHRvIG90aGVycy4NCg0K VGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVu dGlhbCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9y IGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQg dGhpcyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBt ZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2Yg dGhlIGluZGl2aWR1YWwgc2VuZGVyLg0KDQpUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBm b3IgdmlydXNlcyBhbmQgU3BhbSBieSBaVEUgQW50aS1TcGFtIHN5c3RlbS4NCg== --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDD0corpe2k7mbx01_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m= icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office= :access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"= uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof= t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co= m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee= t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns= :odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro= soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln= s:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D= "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"http://sc= hemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schemas.micro= soft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2000/09/= xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" xmlns:u= dc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www.w3.org= /2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/= 2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"= http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.micro= soft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-in= stance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xmlns:udc= xf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http:/= /schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.micr= osoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.microsoft= .com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsoft.com/o= ffice/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/package= /2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats.org/ma= rkup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/200= 4/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/re= lationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" xm= lns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types" xml= ns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messages" x= mlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" x= mlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Publis= hedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"" x= mlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"> <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> <style> <!-- /* Font Definitions */ @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @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;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:"\@SimSun"; panose-1:2 1 6 0 3 1 1 1 1 1;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:SimSun;} 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:SimSun;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:SimSun;} tt {mso-style-priority:99; font-family:SimSun;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:Consolas;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only;} @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'>One more: how you implement the ring-link between PE1 and PE= 2, PWE emulated, and can be used by non-user-related data also or not? Or it i= s an independent link only for ring usage?<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> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Regards,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Peng<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> </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"'> song.xiaojuan@zte.com.cn [mailto:song.xiaojuan@zte.com.cn] <br> <b>Sent:</b> Friday, March 13, 2009 5:03 AM<br> <b>To:</b> Peng He<br> <b>Cc:</b> l2vpn@ietf.org; shao.hong@zte.com.cn; wu.shaoyong@zte.com.cn<br> <b>Subject:</b> </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=B4=F0= =B8=B4</span><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>: Questions ab= out I.D. 'VPLS protection switching with ring access'<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> hel= lo,peng</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; thank for your attention to my draft.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><tt>1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS CE'?</tt> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > answer</span><span lang=3DZH-CN style=3D'font-s= ize: 10.0pt;color:red'>=A3=BA</span><span style=3D'font-size:10.0pt;font-family:= "Arial","sans-serif"; color:red'> yes, you are right</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><tt>2. page 4, middle, by 'PE-CE-CE-PE forms a non-clos= e ring', you mean 'PE1-CE1-CE2-PE2' forms a non-close ring as a close ring sh= ould be ''PE1-CE1-CE2-PE2-PE1'?</tt> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; <span style=3D'color:red'> answer</span></span><span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style= =3D'font-size: 10.0pt;font-family:"Arial","sans-serif";color:red'> yes too.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <tt> 3. Both CE and PE can be a master node (there is o= nly one at a time)?</tt> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > answer:</span><tt><span style=3D'color:blue'> <= /span><span style=3D'color:red'> </span></tt><span style=3D'font-size:10.0pt;font-= family: "Arial","sans-serif";color:red'>a ring only can has one master node at the = same time .</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><tt> 4. What happens if a node, e.g., CE or PE, fails? W= hat happens if a link/node is recovered from a failure?</tt> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; <span style=3D'color:red'> answer</span></span><span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style= =3D'font-size: 10.0pt;font-family:"Arial","sans-serif";color:red'> i am sorry that n= ode failure and failur recovery is my little concern in this version0.thank you for your comment.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > but i think if you want the answer now ,i can explain briefly now .</span> <br> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > in scenario 1 ,if NODE CE i= s down ,the flow will be halted without doubt</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ; if NODE PE1 is down, CE can detect the faillure,= so do the same action as the PE-CE link down.</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ; if NODE PE2 is down ,the same way as that PE1 is down</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > in scenario 2, CE1 is a master,so if NODE CE1 is down ,the flow from CE1 will halt with no doubt.but there is no </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; change for the flow from CE2</spa= n> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; if NODE PE1 is down,CE can detect the faillure,so do th= e same action as the PE-CE</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; link down.</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; if NODE CE2 is down,CE can detect the faillure,the flow from CE2 will hault with </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; no doubt. but there is no change for the flow from CE1.</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > </span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; IF NODE PE2 is down,CE2 will detect it and sent message= to master node CE1,open </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= >  = ;  = ; the CE1-CE2link. </span><br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'= > as regards failure recovery,  = ;if failure is detected disappear, master will block one link connected it agai= n.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; <span style=3D'color:red'> so later i will add th= ese detail to my draft.thank you .</span></span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> i = will attend 74th IETF meeting</span><span lang=3DZH-CN style=3D'font-size:10.0pt= '>=A3=AC</span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>if you still ha= ve some intereste ,we can discuss there. </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span> <br> <br> <br> <o:p></o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td width=3D"26%" valign=3Dtop style=3D'width:26.0%;padding:.75pt .75pt .= 75pt .75pt'> <p class=3DMsoNormal><b><span style=3D'font-size:7.5pt;font-family:"Arial= ","sans-serif"'>Peng He <phe@soapstonenetworks.com></span></b><span style=3D'font-size:7= .5pt; font-family:"Arial","sans-serif"'> </span><o:p></o:p></p> <p><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>2009-= 03-11 09:49</span> <o:p></o:p></p> </td> <td width=3D"73%" valign=3Dtop style=3D'width:73.0%;padding:.75pt .75pt .= 75pt .75pt'> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=CA=D5=BC=FE=C8=CB</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=B3=AD=CB=CD</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn>, "shao.hong@zte.com.cn" <shao.hong@zte.com.cn>, "l2vpn@ietf.org" <l2vpn@ietf.org></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=D6=F7=CC=E2</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>Questions about I.D. 'VPLS protection switching with ring access'</span><o:p></o:= p></p> </td> </tr> </table> <p class=3DMsoNormal><o:p> </o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td> </tr> </table> </td> </tr> </table> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <br> <br> <tt>Hello Xiaojun,</tt><br> <br> <tt>I have a few questions about your ID of 'VPLS protection switching with ring access', which sounds like an interesting approach.</tt><br> <br> <tt>1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS = CE'?</tt><br> <br> <tt>2. page 4, middle, by 'PE-CE-CE-PE forms a non-close ring', you mean 'PE1-CE1-CE2-PE2' forms a non-close ring as a close ring should be ''PE1-CE1-CE2-PE2-PE1'?</tt><br> <br> <tt>3. Both CE and PE can be a master node (there is only one at a time)?</= tt><br> <br> <tt>4. What happens if a node, e.g., CE or PE, fails? What happens if a lin= k/node is recovered from a failure?</tt><br> <br> <tt>Seems to me that although there are many Ethernet ring protocols, but m= ost of the deployed ones are vendor-specified, expect G.8032, which does not support overlapping rings yet. So it might be a little bit difficult for a = VPLS device vendor (L2.5/L3) to implement/emulate a L2 vendor's specific ring protocol, unless everybody supports G.8032. </tt><br> <br> <br> <tt>Regards,</tt><br> <tt>Peng</tt> <o:p></o:p></p> <pre><o:p> </o:p></pre><pre>------------------------------------------= --------------<o:p></o:p></pre><pre>ZTE Information Security = ;Notice: The information contained in this ma= il is solely property of the sender's or= ganization. This mail communication is confidentia= l. Recipients named above are obligated to&nb= sp;maintain secrecy and are not permitted to&= nbsp;disclose the contents of this communication&n= bsp;to others.<o:p></o:p></pre><pre>This email and any&= nbsp;files transmitted with it are confidential&nb= sp;and intended solely for the use of th= e individual or entity to whom they are&= nbsp;addressed. If you have received this ema= il in error please notify the originator = ;of the message. Any views expressed in = this message are those of the individual = ;sender.<o:p></o:p></pre><pre>This message has been sca= nned for viruses and Spam by ZTE Anti-Sp= am system.<o:p></o:p></pre></div> </div> </body> </html> --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDD0corpe2k7mbx01_-- From rfc-editor@rfc-editor.org Mon Mar 16 17:01:26 2009 Return-Path: <rfc-editor@rfc-editor.org> 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 F102A28C1EE; Mon, 16 Mar 2009 17:01:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.254 X-Spam-Level: X-Spam-Status: No, score=-17.254 tagged_above=-999 required=5 tests=[AWL=0.345, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] 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 N69hKFJDOPiU; Mon, 16 Mar 2009 17:01:26 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 4332928C188; Mon, 16 Mar 2009 17:01:26 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id F2BA2257713; Mon, 16 Mar 2009 16:59:47 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5501 on Requirements for Multicast Support in Virtual Private LAN Services From: rfc-editor@rfc-editor.org Message-Id: <20090316235947.F2BA2257713@bosco.isi.edu> Date: Mon, 16 Mar 2009 16:59:47 -0700 (PDT) Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 17 Mar 2009 00:01:27 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5501 Title: Requirements for Multicast Support in Virtual Private LAN Services Author: Y. Kamite, Ed., Y. Wada, Y. Serbest, T. Morin, L. Fang Status: Informational Date: March 2009 Mailbox: y.kamite@ntt.com, wada.yuichiro@lab.ntt.co.jp, yetik_serbest@labs.att.com, thomas.morin@francetelecom.com, lufang@cisco.com Pages: 31 Characters: 71507 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2vpn-vpls-mcast-reqts-07.txt URL: http://www.rfc-editor.org/rfc/rfc5501.txt This document provides functional requirements for network solutions that support multicast over Virtual Private LAN Service (VPLS). It specifies requirements both from the end user and service provider standpoints. It is intended that potential solutions will use these requirements as guidelines. This memo provides information for the Internet community. This document is a product of the Layer 2 Virtual Private Networks Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From shane@castlepoint.net Mon Mar 16 19:10:40 2009 Return-Path: <shane@castlepoint.net> 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 A9AA63A697D for <l2vpn@core3.amsl.com>; Mon, 16 Mar 2009 19:10:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.745 X-Spam-Level: X-Spam-Status: No, score=-0.745 tagged_above=-999 required=5 tests=[AWL=0.372, 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 iH1-PTuOw0lH for <l2vpn@core3.amsl.com>; Mon, 16 Mar 2009 19:10:39 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 574F83A68AC for <l2vpn@ietf.org>; Mon, 16 Mar 2009 19:10:39 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id BD1182684EA; Mon, 16 Mar 2009 20:11:21 -0600 (MDT) Received: from mbp.castlepoint.net (71-215-95-189.hlrn.qwest.net [71.215.95.189]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Mon, 16 Mar 2009 20:11:21 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.95.189; client-port=3899; syn-fingerprint=65535:55:1:64:M1452,N,W3,N,N,T,S; data-bytes=0 Message-Id: <EA7D6F68-85FF-4FA8-9697-E605EF852986@castlepoint.net> From: Shane Amante <shane@castlepoint.net> To: l2vpn@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: IETF 74: Draft Agenda Posted Date: Mon, 16 Mar 2009 20:11:06 -0600 X-Mailer: Apple Mail (2.930.3) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 17 Mar 2009 02:10:40 -0000 Hi Everyone, The draft agenda for IETF 74 has been posted here: http://www.ietf.org/proceedings/09mar/agenda/l2vpn.txt Please let the chairs know if there are any changes. -shane & Vach From phe@soapstonenetworks.com Tue Mar 17 05:24:46 2009 Return-Path: <phe@soapstonenetworks.com> 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 341313A6A43 for <l2vpn@core3.amsl.com>; Tue, 17 Mar 2009 05:24:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.375 X-Spam-Level: X-Spam-Status: No, score=0.375 tagged_above=-999 required=5 tests=[AWL=-1.430, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6, J_CHICKENPOX_42=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_82=0.6, J_CHICKENPOX_83=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 jbaign4eOp0H for <l2vpn@core3.amsl.com>; Tue, 17 Mar 2009 05:24:44 -0700 (PDT) Received: from p01c12o147.mxlogic.net (p01c12o147.mxlogic.net [208.65.145.70]) by core3.amsl.com (Postfix) with ESMTP id C486C3A6841 for <l2vpn@ietf.org>; Tue, 17 Mar 2009 05:24:40 -0700 (PDT) Received: from unknown [12.230.177.130] (EHLO p01c12o147.mxlogic.net) by p01c12o147.mxlogic.net (mxl_mta-6.1.1-1) with ESMTP id 3b69fb94.2719755152.31306.00-500.p01c12o147.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 17 Mar 2009 06:25:24 -0600 (MDT) Received: from unknown [12.230.177.130] (EHLO smtp.soapstonenetworks.com) by p01c12o147.mxlogic.net (mxl_mta-6.1.1-1) over TLS secured channel with ESMTP id 3a69fb94.3770452880.31280.00-028.p01c12o147.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 17 Mar 2009 06:25:11 -0600 (MDT) Received: from corp-e2k7-mbx01.Soapstone.local ([172.24.2.72]) by cratos.Soapstone.local ([172.24.2.65]) with mapi; Tue, 17 Mar 2009 08:25:06 -0400 From: Peng He <phe@soapstonenetworks.com> To: "song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn> Date: Tue, 17 Mar 2009 08:25:06 -0400 Subject: RE: RE: Questions about I.D. 'VPLS protection switching with ring access' Thread-Topic: RE: Questions about I.D. 'VPLS protection switching with ring access' Thread-Index: Acmm15PzCuOchDeVSc2CYR0T7NPswAAI8FTg Message-ID: <E6D5CAC0ACC932498E6AC1A692E0CBA12297B7F046@corp-e2k7-mbx01.Soapstone.local> References: <E6D5CAC0ACC932498E6AC1A692E0CBA12297B7EDD0@corp-e2k7-mbx01.Soapstone.local> <OF131DA090.75E3B11A-ON4825757C.002C4C78-4825757C.002BD875@zte.com.cn> In-Reply-To: <OF131DA090.75E3B11A-ON4825757C.002C4C78-4825757C.002BD875@zte.com.cn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7F046corpe2k7mbx01_" MIME-Version: 1.0 X-Spam: [F=0.2000000000; S=0.200(2009020301)] X-MAIL-FROM: <phe@soapstonenetworks.com> X-SOURCE-IP: [12.230.177.130] Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn> 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 17 Mar 2009 12:24:46 -0000 --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7F046corpe2k7mbx01_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 VGhhbmtzLiBMb29raW5nIGZvcndhcmQgdG8gc2VlaW5nIHRoZSBuZXh0IHZlcnNpb24gb2YgeW91 ciBkcmFmdC4NCg0KDQpSZWdhcmRzLA0KUGVuZw0KDQpGcm9tOiBzb25nLnhpYW9qdWFuQHp0ZS5j b20uY24gW21haWx0bzpzb25nLnhpYW9qdWFuQHp0ZS5jb20uY25dDQpTZW50OiBUdWVzZGF5LCBN YXJjaCAxNywgMjAwOSA0OjA0IEFNDQpUbzogUGVuZyBIZQ0KQ2M6IGwydnBuQGlldGYub3JnOyBz aGFvLmhvbmdAenRlLmNvbS5jbjsgd3Uuc2hhb3lvbmdAenRlLmNvbS5jbg0KU3ViamVjdDogtPC4 tDogUkU6IFF1ZXN0aW9ucyBhYm91dCBJLkQuICdWUExTIHByb3RlY3Rpb24gc3dpdGNoaW5nIHdp dGggcmluZyBhY2Nlc3MnDQoNCg0KIE9uZSBtb3JlOiBob3cgeW91IGltcGxlbWVudCB0aGUgcmlu Zy1saW5rIGJldHdlZW4gUEUxIGFuZCBQRTIsIFBXRSBlbXVsYXRlZCwgYW5kIGNhbiBiZSB1c2Vk IGJ5IG5vbi11c2VyLXJlbGF0ZWQgZGF0YSBhbHNvIG9yIG5vdD8gT3IgaXQgaXMgYW4gaW5kZXBl bmRlbnQgbGluayBvbmx5IGZvciByaW5nIHVzYWdlPw0KDQogICBhbnN3ZXI6IHdlIGFyZSBwcmVw YXJpbmcgYWRkaW5nICB0aGVzZSBwYXJ0IHRvIG15IGRyYWZ0ICAuDQoNCiAgICAgICAgICB0aGVy ZSBpcyBhIFBXIGxpbmsgYmV0d2VlbiBQRTEgYW5kIFBFMiwgYW5kIHRoZSBsaW5rICBjYW4gY29u bmVjdCB3aXRoIHRoZSBhY2Nlc3MgcmluZyAgdG8gZm9ybSBhIGNsb3NlIHJpbmcgLg0KDQogICAg ICAgICAgdGhpcyAgUFcgbGluayAgaXMgbW9zdGx5IHVzZWQgdG8gdHJhbnNtaXQgbGluayAiZG93 biIgbWVzc2FnZSB0byBtYXN0ZXIgbm9kZSBpbiB0aGlzIHNpdHVhdGlvbi4NCg0KDQoqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqDQrT0M/f0dC+v9S6IENFJlBUTiDEz76pyO28/rb+sr8N CrXnu7CjujgwMzc4DQpFTUFJTDpzb25nLnhpYW9qdWFuQHp0ZS5jb20uY24NCioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioNCg0KUGVuZyBIZSA8cGhlQHNvYXBzdG9uZW5ldHdvcmtzLmNv bT4NCg0KMjAwOS0wMy0xMyAyMzozMw0KDQrK1bz+yMsNCg0KInNvbmcueGlhb2p1YW5AenRlLmNv bS5jbiIgPHNvbmcueGlhb2p1YW5AenRlLmNvbS5jbj4NCg0Ks63LzQ0KDQoibDJ2cG5AaWV0Zi5v cmciIDxsMnZwbkBpZXRmLm9yZz4sICJzaGFvLmhvbmdAenRlLmNvbS5jbiIgPHNoYW8uaG9uZ0B6 dGUuY29tLmNuPiwgInd1LnNoYW95b25nQHp0ZS5jb20uY24iIDx3dS5zaGFveW9uZ0B6dGUuY29t LmNuPg0KDQrW98ziDQoNClJFOiBRdWVzdGlvbnMgYWJvdXQgSS5ELiAnVlBMUyBwcm90ZWN0aW9u IHN3aXRjaGluZyB3aXRoIHJpbmcgYWNjZXNzJw0KDQoNCg0KDQoNCg0KDQpPbmUgbW9yZTogaG93 IHlvdSBpbXBsZW1lbnQgdGhlIHJpbmctbGluayBiZXR3ZWVuIFBFMSBhbmQgUEUyLCBQV0UgZW11 bGF0ZWQsIGFuZCBjYW4gYmUgdXNlZCBieSBub24tdXNlci1yZWxhdGVkIGRhdGEgYWxzbyBvciBu b3Q/IE9yIGl0IGlzIGFuIGluZGVwZW5kZW50IGxpbmsgb25seSBmb3IgcmluZyB1c2FnZT8NCg0K DQpSZWdhcmRzLA0KUGVuZw0KDQpGcm9tOiBzb25nLnhpYW9qdWFuQHp0ZS5jb20uY24gW21haWx0 bzpzb25nLnhpYW9qdWFuQHp0ZS5jb20uY25dDQpTZW50OiBGcmlkYXksIE1hcmNoIDEzLCAyMDA5 IDU6MDMgQU0NClRvOiBQZW5nIEhlDQpDYzogbDJ2cG5AaWV0Zi5vcmc7IHNoYW8uaG9uZ0B6dGUu Y29tLmNuOyB3dS5zaGFveW9uZ0B6dGUuY29tLmNuDQpTdWJqZWN0OiC08Li0OiBRdWVzdGlvbnMg YWJvdXQgSS5ELiAnVlBMUyBwcm90ZWN0aW9uIHN3aXRjaGluZyB3aXRoIHJpbmcgYWNjZXNzJw0K DQoNCmhlbGxvLHBlbmcNCg0KICAgICAgdGhhbmsgZm9yIHlvdXIgYXR0ZW50aW9uIHRvIG15IGRy YWZ0Lg0KDQoNCiAgICAgIDEuIHBhZ2UgMywgYm90dG9tLCB5b3UgdXNlIHRoZSB0ZXJtICdWUExT IENFJyB0byBkaXN0aW5ndWlzaCAnbm9uLVZQTFMgQ0UnPw0KDQogICAgICAgICBhbnN3ZXKjuiAg eWVzLCB5b3UgYXJlIHJpZ2h0DQoNCiAgICAgIDIuIHBhZ2UgNCwgbWlkZGxlLCBieSAnUEUtQ0Ut Q0UtUEUgZm9ybXMgYSBub24tY2xvc2UgcmluZycsIHlvdSBtZWFuICdQRTEtQ0UxLUNFMi1QRTIn IGZvcm1zIGEgbm9uLWNsb3NlIHJpbmcgYXMgYSBjbG9zZSByaW5nIHNob3VsZCBiZSAnJ1BFMS1D RTEtQ0UyLVBFMi1QRTEnPw0KICAgICAgICBhbnN3ZXKjuiB5ZXMgdG9vLg0KDQoNCiAgICAgMy4g Qm90aCBDRSBhbmQgUEUgY2FuIGJlIGEgbWFzdGVyIG5vZGUgKHRoZXJlIGlzIG9ubHkgb25lIGF0 IGEgdGltZSk/DQogICAgICAgICBhbnN3ZXI6ICBhIHJpbmcgb25seSBjYW4gaGFzIG9uZSBtYXN0 ZXIgbm9kZSBhdCB0aGUgc2FtZSB0aW1lIC4NCg0KICAgICAgNC4gV2hhdCBoYXBwZW5zIGlmIGEg bm9kZSwgZS5nLiwgQ0Ugb3IgUEUsIGZhaWxzPyBXaGF0IGhhcHBlbnMgaWYgYSBsaW5rL25vZGUg aXMgcmVjb3ZlcmVkIGZyb20gYSBmYWlsdXJlPw0KICAgICAgICAgYW5zd2Vyo7ogaSBhbSBzb3Jy eSB0aGF0ICBub2RlIGZhaWx1cmUgIGFuZCBmYWlsdXIgcmVjb3ZlcnkgIGlzIG15IGxpdHRsZSBj b25jZXJuIGluIHRoaXMgdmVyc2lvbjAudGhhbmsgeW91IGZvciB5b3VyIGNvbW1lbnQuDQoNCiAg ICAgICAgIGJ1dCBpIHRoaW5rIGlmIHlvdSB3YW50IHRoZSBhbnN3ZXIgbm93ICxpIGNhbiBleHBs YWluIGJyaWVmbHkgbm93IC4NCg0KDQogICAgICAgICAgICAgIGluIHNjZW5hcmlvIDEgLGlmIE5P REUgQ0UgaXMgZG93biAsdGhlIGZsb3cgd2lsbCBiZSBoYWx0ZWQgd2l0aG91dCBkb3VidA0KICAg ICAgICAgICAgICAgICAgICAgICAgICAgICBpZiBOT0RFIFBFMSBpcyAgZG93biwgQ0UgY2FuIGRl dGVjdCB0aGUgZmFpbGx1cmUsc28gZG8gIHRoZSBzYW1lIGFjdGlvbiBhcyB0aGUgUEUtQ0UgbGlu ayBkb3duLg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICBpZiBOT0RFIFBFMiBpcyAgZG93 biAsdGhlIHNhbWUgd2F5IGFzIHRoYXQgUEUxIGlzIGRvd24NCiAgICAgICAgICAgICBpbiAgc2Nl bmFyaW8gMiwgQ0UxIGlzIGEgbWFzdGVyLHNvICBpZiBOT0RFIENFMSBpcyBkb3duICx0aGUgZmxv dyBmcm9tIENFMSB3aWxsIGhhbHQgd2l0aCBubyBkb3VidC5idXQgdGhlcmUgaXMgbm8NCiAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGNoYW5n ZSBmb3IgdGhlIGZsb3cgZnJvbSBDRTINCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICBpZiBOT0RFIFBFMSBpcyBkb3duLENFIGNhbiBkZXRlY3QgdGhlIGZh aWxsdXJlLHNvIGRvICB0aGUgc2FtZSBhY3Rpb24gYXMgdGhlIFBFLUNFDQogICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBsaW5rIGRvd24uDQog ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGlmIE5PREUg Q0UyIGlzIGRvd24sQ0UgY2FuIGRldGVjdCB0aGUgZmFpbGx1cmUsdGhlIGZsb3cgZnJvbSBDRTIg d2lsbCBoYXVsdCB3aXRoDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgbm8gZG91YnQuIGJ1dCB0aGVyZSBpcyBubyBjaGFuZ2UgZm9yIHRo ZSBmbG93IGZyb20gQ0UxLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIElGIE5PREUgUEUyIGlzIGRvd24sQ0UyIHdpbGwgZGV0ZWN0IGl0IGFuZCBz ZW50IG1lc3NhZ2UgdG8gbWFzdGVyIG5vZGUgQ0UxLG9wZW4NCiAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHRoZSBDRTEtQ0UybGluay4NCg0KICAg ICAgICAgIGFzIHJlZ2FyZHMgICBmYWlsdXJlIHJlY292ZXJ5LCAgaWYgZmFpbHVyZSBpcyBkZXRl Y3RlZCBkaXNhcHBlYXIsIG1hc3RlciB3aWxsIGJsb2NrIG9uZSBsaW5rIGNvbm5lY3RlZCBpdCBh Z2Fpbi4NCg0KICAgICAgICAgIHNvIGxhdGVyIGkgd2lsbCBhZGQgdGhlc2UgZGV0YWlsIHRvIG15 IGRyYWZ0LnRoYW5rIHlvdSAuDQoNCiBpIHdpbGwgYXR0ZW5kIDc0dGggSUVURiBtZWV0aW5no6xp ZiB5b3Ugc3RpbGwgaGF2ZSBzb21lIGludGVyZXN0ZSAsd2UgY2FuIGRpc2N1c3MgdGhlcmUuDQoN ClBlbmcgSGUgPHBoZUBzb2Fwc3RvbmVuZXR3b3Jrcy5jb20+DQoNCjIwMDktMDMtMTEgMDk6NDkN Cg0KDQrK1bz+yMsNCg0KInNvbmcueGlhb2p1YW5AenRlLmNvbS5jbiIgPHNvbmcueGlhb2p1YW5A enRlLmNvbS5jbj4NCg0Ks63LzQ0KDQoid3Uuc2hhb3lvbmdAenRlLmNvbS5jbiIgPHd1LnNoYW95 b25nQHp0ZS5jb20uY24+LCAic2hhby5ob25nQHp0ZS5jb20uY24iIDxzaGFvLmhvbmdAenRlLmNv bS5jbj4sICJsMnZwbkBpZXRmLm9yZyIgPGwydnBuQGlldGYub3JnPg0KDQrW98ziDQoNClF1ZXN0 aW9ucyBhYm91dCBJLkQuICdWUExTIHByb3RlY3Rpb24gc3dpdGNoaW5nIHdpdGggcmluZyBhY2Nl c3MnDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KSGVsbG8gWGlhb2p1biwNCg0KSSBoYXZlIGEgZmV3 IHF1ZXN0aW9ucyBhYm91dCB5b3VyIElEIG9mICdWUExTIHByb3RlY3Rpb24gc3dpdGNoaW5nIHdp dGggcmluZyBhY2Nlc3MnLCB3aGljaCBzb3VuZHMgbGlrZSBhbiBpbnRlcmVzdGluZyBhcHByb2Fj aC4NCg0KMS4gcGFnZSAzLCBib3R0b20sIHlvdSB1c2UgdGhlIHRlcm0gJ1ZQTFMgQ0UnIHRvIGRp c3Rpbmd1aXNoICdub24tVlBMUyBDRSc/DQoNCjIuIHBhZ2UgNCwgbWlkZGxlLCBieSAnUEUtQ0Ut Q0UtUEUgZm9ybXMgYSBub24tY2xvc2UgcmluZycsIHlvdSBtZWFuICdQRTEtQ0UxLUNFMi1QRTIn IGZvcm1zIGEgbm9uLWNsb3NlIHJpbmcgYXMgYSBjbG9zZSByaW5nIHNob3VsZCBiZSAnJ1BFMS1D RTEtQ0UyLVBFMi1QRTEnPw0KDQozLiBCb3RoIENFIGFuZCBQRSBjYW4gYmUgYSBtYXN0ZXIgbm9k ZSAodGhlcmUgaXMgb25seSBvbmUgYXQgYSB0aW1lKT8NCg0KNC4gV2hhdCBoYXBwZW5zIGlmIGEg bm9kZSwgZS5nLiwgQ0Ugb3IgUEUsIGZhaWxzPyBXaGF0IGhhcHBlbnMgaWYgYSBsaW5rL25vZGUg aXMgcmVjb3ZlcmVkIGZyb20gYSBmYWlsdXJlPw0KDQpTZWVtcyB0byBtZSB0aGF0IGFsdGhvdWdo IHRoZXJlIGFyZSBtYW55IEV0aGVybmV0IHJpbmcgcHJvdG9jb2xzLCBidXQgbW9zdCBvZiB0aGUg ZGVwbG95ZWQgb25lcyBhcmUgdmVuZG9yLXNwZWNpZmllZCwgZXhwZWN0IEcuODAzMiwgd2hpY2gg ZG9lcyBub3Qgc3VwcG9ydCBvdmVybGFwcGluZyByaW5ncyB5ZXQuIFNvIGl0IG1pZ2h0IGJlIGEg bGl0dGxlIGJpdCBkaWZmaWN1bHQgZm9yIGEgVlBMUyBkZXZpY2UgdmVuZG9yIChMMi41L0wzKSB0 byBpbXBsZW1lbnQvZW11bGF0ZSBhIEwyIHZlbmRvcidzIHNwZWNpZmljIHJpbmcgcHJvdG9jb2ws IHVubGVzcyBldmVyeWJvZHkgc3VwcG9ydHMgRy44MDMyLg0KDQoNClJlZ2FyZHMsDQpQZW5nDQoN Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t DQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkgTm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFp bmVkIGluIHRoaXMgbWFpbCBpcyBzb2xlbHkgcHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2Fu aXphdGlvbi4gVGhpcyBtYWlsIGNvbW11bmljYXRpb24gaXMgY29uZmlkZW50aWFsLiBSZWNpcGll bnRzIG5hbWVkIGFib3ZlIGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgYXJl IG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNh dGlvbiB0byBvdGhlcnMuDQpUaGlzIGVtYWlsIGFuZCBhbnkgZmlsZXMgdHJhbnNtaXR0ZWQgd2l0 aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2Yg dGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdob20gdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5 b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yIHBsZWFzZSBub3RpZnkgdGhlIG9y aWdpbmF0b3Igb2YgdGhlIG1lc3NhZ2UuIEFueSB2aWV3cyBleHByZXNzZWQgaW4gdGhpcyBtZXNz YWdlIGFyZSB0aG9zZSBvZiB0aGUgaW5kaXZpZHVhbCBzZW5kZXIuDQpUaGlzIG1lc3NhZ2UgaGFz IGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBhbmQgU3BhbSBieSBaVEUgQW50aS1TcGFtIHN5c3Rl bS4NCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tDQoNClpURSBJbmZvcm1hdGlvbiBTZWN1cml0eSBOb3RpY2U6IFRoZSBpbmZvcm1h dGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWlsIGlzIHNvbGVseSBwcm9wZXJ0eSBvZiB0aGUgc2Vu ZGVyJ3Mgb3JnYW5pemF0aW9uLiBUaGlzIG1haWwgY29tbXVuaWNhdGlvbiBpcyBjb25maWRlbnRp YWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZCB0byBtYWludGFpbiBzZWNy ZWN5IGFuZCBhcmUgbm90IHBlcm1pdHRlZCB0byBkaXNjbG9zZSB0aGUgY29udGVudHMgb2YgdGhp cyBjb21tdW5pY2F0aW9uIHRvIG90aGVycy4NCg0KVGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRy YW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlhbCBhbmQgaW50ZW5kZWQgc29sZWx5IGZv ciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFk ZHJlc3NlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ug bm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBtZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2Vk IGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2YgdGhlIGluZGl2aWR1YWwgc2VuZGVyLg0KDQpU aGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBhbmQgU3BhbSBieSBaVEUg QW50aS1TcGFtIHN5c3RlbS4NCg== --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7F046corpe2k7mbx01_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m= icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office= :access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"= uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof= t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co= m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee= t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns= :odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro= soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln= s:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D= "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"http://sc= hemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schemas.micro= soft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2000/09/= xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" xmlns:u= dc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www.w3.org= /2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/= 2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"= http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.micro= soft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-in= stance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xmlns:udc= xf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http:/= /schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.micr= osoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.microsoft= .com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsoft.com/o= ffice/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/package= /2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats.org/ma= rkup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/200= 4/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/re= lationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" xm= lns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types" xml= ns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messages" x= mlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" x= mlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Publis= hedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"" x= mlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"> <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> <style> <!-- /* Font Definitions */ @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1;} @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;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:"\@SimSun"; panose-1:2 1 6 0 3 1 1 1 1 1;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:SimSun;} 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:SimSun;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:SimSun;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:Consolas;} span.EmailStyle20 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only;} @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'>Thanks. Looking forward to seeing the next version of your draft.<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> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Regards,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Peng<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> </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"'> song.xiaojuan@zte.com.cn [mailto:song.xiaojuan@zte.com.cn] <br> <b>Sent:</b> Tuesday, March 17, 2009 4:04 AM<br> <b>To:</b> Peng He<br> <b>Cc:</b> l2vpn@ietf.org; shao.hong@zte.com.cn; wu.shaoyong@zte.com.cn<br> <b>Subject:</b> </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=B4=F0= =B8=B4</span><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>: RE: Question= s about I.D. 'VPLS protection switching with ring access'<o:p></o:p></span></= p> </div> </div> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> <sp= an style=3D'color:#1F497D'>One more: how you implement the ring-link between P= E1 and PE2, PWE emulated, and can be used by non-user-related data also or not? Or= it is an independent link only for ring usage?</span></span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> answer: we are preparing adding these part to my draft .<= /span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; there is a PW link between PE1 and PE2, and the link can connect with the access ring to form a close ring .</span> = <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; this PW link is mostly used to transmit li= nk "down" message to master node in this situation.</span> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> &n= bsp; </span><br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>*********= **********************<br> </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=D3=D0=CF=DF=D1=D0=BE= =BF=D4=BA</span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> CE&PTN </s= pan><span lang=3DZH-CN style=3D'font-size:10.0pt'>=C4=CF=BE=A9=C8=ED=BC=FE=B6=FE=B2= =BF</span><span style=3D'font-size:10.0pt; font-family:"Arial","sans-serif"'><br> </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=B5=E7=BB=B0=A3=BA</sp= an><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>80378<br> EMAIL:song.xiaojuan@zte.com.cn<br> *******************************</span> <br> <br> <o:p></o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td width=3D"26%" valign=3Dtop style=3D'width:26.0%;padding:.75pt .75pt .= 75pt .75pt'> <p class=3DMsoNormal><b><span style=3D'font-size:7.5pt;font-family:"Arial= ","sans-serif"'>Peng He <phe@soapstonenetworks.com></span></b><span style=3D'font-size:7= .5pt; font-family:"Arial","sans-serif"'> </span><o:p></o:p></p> <p><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>2009-= 03-13 23:33</span> <o:p></o:p></p> </td> <td width=3D"73%" valign=3Dtop style=3D'width:73.0%;padding:.75pt .75pt .= 75pt .75pt'> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=CA=D5=BC=FE=C8=CB</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=B3=AD=CB=CD</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"l2vpn@ietf.org" <l2vpn@ietf.org>, "shao.hong@zte.com.cn" <shao.hong@zte.com.cn>, "wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn></span> <o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=D6=F7=CC=E2</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>RE: Questions about I.D. 'VPLS protection switching with ring access'</span= ><o:p></o:p></p> </td> </tr> </table> <p class=3DMsoNormal><o:p> </o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></td> </tr> </table> </td> </tr> </table> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br> <br> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F4= 97D'>One more: how you implement the ring-link between PE1 and PE2, PWE emulated, an= d can be used by non-user-related data also or not? Or it is an independent l= ink only for ring usage?</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F4= 97D'> </span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F4= 97D'> </span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F4= 97D'>Regards,</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F4= 97D'>Peng</span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F4= 97D'> </span> <br> <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"'> song.xiaojuan@zte.com.cn [mailto:song.xiaojuan@zte.com.cn] <b><br> Sent:</b> Friday, March 13, 2009 5:03 AM<b><br> To:</b> Peng He<b><br> Cc:</b> l2vpn@ietf.org; shao.hong@zte.com.cn; wu.shaoyong@zte.com.cn<b><br> Subject:</b> </span><span lang=3DZH-CN style=3D'font-size:10.0pt'>=B4=F0=B8= =B4</span><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>: Questions ab= out I.D. 'VPLS protection switching with ring access'</span> <br> <span style=3D'font-family:"Arial","sans-serif"'> </span> <br> <span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><br> hello,peng</span><span style=3D'font-family:"Arial","sans-serif"'> </span><= span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><br> <br> thank for your attention to my draft.</span><span style=3D'font-family:"Arial","sans-serif"'> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b= r> <br> </span><span style=3D'font-family:"Arial","sans-serif"= '>1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS CE'? <b= r> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:red'><br> answer</span><span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style=3D'font-size:= 10.0pt; font-family:"Arial","sans-serif";color:red'> yes, you are right</span= ><span style=3D'font-family:"Arial","sans-serif"'> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b= r> </span><span style=3D'font-family:"Arial","sans-serif"= '>2. page 4, middle, by 'PE-CE-CE-PE forms a non-close ring', you mean 'PE1-CE1-CE2-PE2' forms a non-close ring as a close ring should be ''PE1-CE1-CE2-PE2-PE1'? </span><span style=3D'font-size:10.0pt;font-family:= "Arial","sans-serif"'><br> <span style=3D'color:red'> answer</span></span><= span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style= =3D'font-size: 10.0pt;font-family:"Arial","sans-serif";color:red'> yes too.</span><span style=3D'font-family:"Arial","sans-serif"'> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b= r> </span><span style=3D'font-family:"Arial","sans-serif"'= ><br> 3. Both CE and PE can be a master node (there is only o= ne at a time)? </span><span style=3D'font-size:10.0pt;font-family:"Arial","san= s-serif"; color:red'><br> answer:</span><span style=3D'font-family:= "Arial","sans-serif"; color:blue'> </span><span style=3D'font-family:"Arial","sans-serif";color:r= ed'> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'>a rin= g only can has one master node at the same time .</span><span style=3D'font-family= :"Arial","sans-serif"'> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b= r> </span><span style=3D'font-family:"Arial","sans-serif"'= > 4. What happens if a node, e.g., CE or PE, fails? What happens if a link/node = is recovered from a failure? </span><span style=3D'font-size:10.0pt;font-famil= y: "Arial","sans-serif"'><br> <span style=3D'color:red'> answer</span></= span><span lang=3DZH-CN style=3D'font-size:10.0pt;color:red'>=A3=BA</span><span style= =3D'font-size: 10.0pt;font-family:"Arial","sans-serif";color:red'> i am sorry that n= ode failure and failur recovery is my little concern in this version0.thank= you for your comment.</span><span style=3D'font-family:"Arial","sans-serif"'> <= br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:red'><br> but i think if you want the answer now ,i= can explain briefly now .</span><span style=3D'font-family:"Arial","sans-serif"= '> <br> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:red'><br> in scenario 1 ,if NODE CE = is down ,the flow will be halted without doubt</span><span style=3D'font-famil= y: "Arial","sans-serif"'> </span><span style=3D'font-size:10.0pt;font-family:"= Arial","sans-serif"; color:red'><br>  = ; if NODE PE1 is down, CE can detect the faillure,so do the same action as the PE-CE link down.</span><span style=3D'font-family:"Arial","sans-serif"'> </span><span style=3D'font-size= :10.0pt; font-family:"Arial","sans-serif";color:red'><br>  = ; if NODE PE2 is down ,the same way as that = PE1 is down</span><span style=3D'font-family:"Arial","sans-serif"'> </span><spa= n style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:red'><br> in scenario 2, CE1 is= a master,so if NODE CE1 is down ,the flow from CE1 will halt with no doubt.but there is no <br>  = ;  = ; change for the flow from CE= 2</span><span style=3D'font-family:"Arial","sans-serif"'> </span><span style=3D'font-size= :10.0pt; font-family:"Arial","sans-serif";color:red'><br>  = ;  = ; if NODE PE1 is down,CE can detect the faillure,so do the same action as the PE-CE</span><span style=3D'font-family:"Arial"= ,"sans-serif"'> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:red'><br>  = ;  = ; link down.</span><span style=3D'font-family:"Arial","sans-serif"'> </span><span style=3D'font-size= :10.0pt; font-family:"Arial","sans-serif";color:red'><br>  = ;  = ; if NODE CE2 is down,CE can detect the faillure,the flo= w from CE2 will hault with <br>  = ;  = ; no doubt. but there is no change for the flow from CE1.</span><span style=3D'font-family:"Arial","san= s-serif"'> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:red'><br> </span><span style=3D'font= -family: "Arial","sans-serif"'> </span><span style=3D'font-size:10.0pt;font-fam= ily: "Arial","sans-serif";color:red'><br>  = ;  = ; IF NODE PE2 is down,CE2 will detect it and sent messag= e to master node CE1,open <br>  = ;  = ; the CE1-CE2link. </span><span style=3D'font-family:"Arial","sans-serif"'><br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:red'><br> as regards failure recovery, &nbs= p;if failure is detected disappear, master will block one link connected it agai= n.</span><span style=3D'font-family:"Arial","sans-serif"'> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b= r> <span style=3D'color:red'> so later i wil= l add these detail to my draft.thank you .</span></span><span style=3D'font-famil= y: "Arial","sans-serif"'> <br> </span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b= r> i will attend 74th IETF meeting</span><span lang=3DZH-CN style=3D'fon= t-size: 10.0pt'>=A3=AC</span><span style=3D'font-size:10.0pt;font-family:"Arial","s= ans-serif"'>if you still have some intereste ,we can discuss there. <= br> </span><span style=3D'font-family:"Arial","sans= -serif"'> </span><o:p></o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td width=3D"24%" valign=3Dtop style=3D'width:24.0%;padding:.75pt .75pt .= 75pt .75pt'> <p class=3DMsoNormal><b><span style=3D'font-size:7.5pt;font-family:"Arial= ","sans-serif"'>Peng He <phe@soapstonenetworks.com></span></b><span style=3D'font-size:7= .5pt; font-family:"Arial","sans-serif"'> </span><o:p></o:p></p> <p><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>2009-= 03-11 09:49</span><span style=3D'font-family:"Arial","sans-serif"'> </span><o:p= ></o:p></p> </td> <td width=3D"75%" valign=3Dtop style=3D'width:75.0%;padding:.75pt .75pt .= 75pt .75pt'> <p class=3DMsoNormal><o:p> </o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td width=3D"4%" valign=3Dtop style=3D'width:4.0%;padding:.75pt .75pt .= 75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=CA=D5=BC=FE=C8=CB</span><o:p></o:p></p> </td> <td width=3D"95%" valign=3Dtop style=3D'width:95.0%;padding:.75pt .75pt= .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"song.xiaojuan@zte.com.cn" <song.xiaojuan@zte.com.cn></span><span style=3D'font-family:"Aria= l","sans-serif"'> </span><o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=B3=AD=CB=CD</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>"wu.shaoyong@zte.com.cn" <wu.shaoyong@zte.com.cn>, "shao.hong@zte.com.cn" <shao.hong@zte.com.cn>, "l2vpn@ietf.org" <l2vpn@ietf.org></span><span style=3D'font-family:"Arial","sans-s= erif"'> </span><o:p></o:p></p> </td> </tr> <tr> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><span lan= g=3DZH-CN style=3D'font-size:7.5pt'>=D6=F7=CC=E2</span><o:p></o:p></p> </td> <td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'> <p class=3DMsoNormal><span style=3D'font-size:7.5pt;font-family:"Arial"= ,"sans-serif"'>Questions about I.D. 'VPLS protection switching with ring access'</span><o:p></o:= p></p> </td> </tr> </table> <p class=3DMsoNormal><br> <span style=3D'font-family:"Arial","sans-serif"'> </span> <o:p></o:p= ></p> <p><o:p> </o:p></p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'> <tr> <td width=3D"50%" valign=3Dtop style=3D'width:50.0%;padding:.75pt .75pt= .75pt .75pt'></td> <td width=3D"50%" valign=3Dtop style=3D'width:50.0%;padding:.75pt .75pt= .75pt .75pt'></td> </tr> </table> </td> </tr> </table> <p style=3D'margin-bottom:12.0pt'><br> <span style=3D'font-family:"Arial","sans-serif"'><br> <br> <br> Hello Xiaojun,<br> <br> I have a few questions about your ID of 'VPLS protection switching with rin= g access', which sounds like an interesting approach.<br> <br> 1. page 3, bottom, you use the term 'VPLS CE' to distinguish 'non-VPLS CE'?= <br> <br> 2. page 4, middle, by 'PE-CE-CE-PE forms a non-close ring', you mean 'PE1-CE1-CE2-PE2' forms a non-close ring as a close ring should be ''PE1-CE1-CE2-PE2-PE1'?<br> <br> 3. Both CE and PE can be a master node (there is only one at a time)?<br> <br> 4. What happens if a node, e.g., CE or PE, fails? What happens if a link/no= de is recovered from a failure?<br> <br> Seems to me that although there are many Ethernet ring protocols, but most = of the deployed ones are vendor-specified, expect G.8032, which does not suppo= rt overlapping rings yet. So it might be a little bit difficult for a VPLS dev= ice vendor (L2.5/L3) to implement/emulate a L2 vendor's specific ring protocol, unless everybody supports G.8032. <br> <br> <br> Regards,<br> Peng </span><br> <span style=3D'font-family:"Arial","sans-serif"'> </span> <br> <span style=3D'font-family:"Arial","sans-serif"'>--------------------------= ------------------------------</span> <br> <span style=3D'font-family:"Arial","sans-serif"'>ZTE Information Security N= otice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named abo= ve are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.</span> <br> <span style=3D'font-family:"Arial","sans-serif"'>This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expre= ssed in this message are those of the individual sender.</span> <br> <span style=3D'font-family:"Arial","sans-serif"'>This message has been scan= ned for viruses and Spam by ZTE Anti-Spam system.</span> <o:p></o:p></p> <pre><o:p> </o:p></pre><pre>------------------------------------------= --------------<o:p></o:p></pre><pre>ZTE Information Security = ;Notice: The information contained in this ma= il is solely property of the sender's or= ganization. This mail communication is confidentia= l. Recipients named above are obligated to&nb= sp;maintain secrecy and are not permitted to&= nbsp;disclose the contents of this communication&n= bsp;to others.<o:p></o:p></pre><pre>This email and any&= nbsp;files transmitted with it are confidential&nb= sp;and intended solely for the use of th= e individual or entity to whom they are&= nbsp;addressed. If you have received this ema= il in error please notify the originator = ;of the message. Any views expressed in = this message are those of the individual = ;sender.<o:p></o:p></pre><pre>This message has been sca= nned for viruses and Spam by ZTE Anti-Sp= am system.<o:p></o:p></pre></div> </div> </body> </html> --_000_E6D5CAC0ACC932498E6AC1A692E0CBA12297B7F046corpe2k7mbx01_-- From loa@pi.nu Tue Mar 17 07:34:46 2009 Return-Path: <loa@pi.nu> 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 3B2F93A6A06; Tue, 17 Mar 2009 07:34:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.226 X-Spam-Level: X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, HELO_EQ_SE=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 BUajItSiKYWN; Tue, 17 Mar 2009 07:34:45 -0700 (PDT) Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 74EAB3A67E3; Tue, 17 Mar 2009 07:34:45 -0700 (PDT) Received: from [192.36.158.51] (wdhcp-158-51.verkstad.net [192.36.158.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 5BCBB2D84B1; Tue, 17 Mar 2009 15:35:27 +0100 (CET) Message-ID: <49BFB52E.5000903@pi.nu> Date: Tue, 17 Mar 2009 15:35:26 +0100 From: Loa Andersson <loa@pi.nu> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: l2vpn@ietf.org, ccamp@ops.ietf.org, pwe3@ietf.org Subject: poll on making the draft-beller-mpls-tp-gach-dcn 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 17 Mar 2009 14:34:46 -0000 All, the authors/editors of draft-beller-mpls-tp-gach-dcn has asked us to accept the document as an MPLS Working group document. This is a one week poll to see if there are support for making it a working group document, please respond to the mpls-tp mailing list before Wednesday March 25. /Loa -- Loa Andersson Sr Strategy and Standards Manager Ericsson /// phone: +46 8 632 77 14 email: loa.andersson@ericsson.com loa.andersson@redback.com loa@pi.nu From loa@pi.nu Wed Mar 18 07:50:01 2009 Return-Path: <loa@pi.nu> 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 54C7A28C205; Wed, 18 Mar 2009 07:50:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.233 X-Spam-Level: X-Spam-Status: No, score=-2.233 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, HELO_EQ_SE=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 nFGTLnhs6ePJ; Wed, 18 Mar 2009 07:50:00 -0700 (PDT) Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 8B51C28C20D; Wed, 18 Mar 2009 07:50:00 -0700 (PDT) Received: from [192.36.158.51] (wdhcp-158-51.verkstad.net [192.36.158.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id C48392D84B1; Wed, 18 Mar 2009 15:50:43 +0100 (CET) Message-ID: <49C10A42.5070509@pi.nu> Date: Wed, 18 Mar 2009 15:50:42 +0100 From: Loa Andersson <loa@pi.nu> User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: ccamp@ops.ietf.org, l2vpn@ietf.org, pwe3@ietf.org Subject: working groupm last call on draft-ietf-mpls-tp-gach-gal-02 has ended 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 18 Mar 2009 14:50:01 -0000 All, the working group last call on draft-ietf-mpls-tp-gach-gal-02 has ended. 1. we have received the information from ITU-T ad hoc team on mpls-tp that the comments they have is aligned with the last call comments received under point 5. below in the MPLS wg last call. 2. We have received one comment that says that the associated channel should not be used for OAM. Since this is the entire purpose of the of the associated channel the authors/editors are instructed not consider this comment. 3. We have received comments that would require us to revisit the results of the JWT investigtaion. We will not do so, since this is not within our charter. 4. We have received one comment that we are allocating too many experimental code points, the editors/authors are instructed to solve this together with the current and future RTG AD and the MEAD team chair. 5. We have received a set of comments, that should be considered as "friendly amendments" and that should be responded to by the authors-editors. Could the authors lease update the draft and republish. /Loa -- Loa Andersson Sr Strategy and Standards Manager phone: +46 10 717 52 13 Ericsson /// +46 767 72 92 13 email: loa.andersson@ericsson.com loa.andersson@redback.com loa@pi.nu From wwwrun@core3.amsl.com Wed Mar 18 14:39:40 2009 Return-Path: <wwwrun@core3.amsl.com> X-Original-To: l2vpn@ietf.org Delivered-To: l2vpn@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id E000A28C0E1; Wed, 18 Mar 2009 14:39:40 -0700 (PDT) To: yakov@juniper.net, rahul@juniper.net, y.kamite@ntt.com, ipr@ietf.org, lufang@cisco.com From: IETF Secretariat <ietf-ipr@ietf.org> Subject: Posting of IPR Disclosure related to Juniper's Statement of IPR related to draft-ietf-l2vpn-vpls-mcast-04 Message-Id: <20090318213940.E000A28C0E1@core3.amsl.com> Date: Wed, 18 Mar 2009 14:39:40 -0700 (PDT) X-Mailman-Approved-At: Wed, 18 Mar 2009 15:55:17 -0700 Cc: l2vpn@ietf.org, , Shane.Amante@Level3.com, "vach.kompella@alcatel-lucent.comipr-announce"@ietf.org, rdroms@cisco.com, townsley@cisco.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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 18 Mar 2009 21:39:41 -0000 Dear Yakov Rekhter, Rahul Aggarwal, Yuji Kamite, Intellectual Property, Luyuan Fang: An IPR disclosure that pertains to your Internet-Draft entitled "Multicast in VPLS" (draft-ietf-l2vpn-vpls-mcast) was submitted to the IETF Secretariat on 2009-03-17 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1117/). The title of the IPR disclosure is "Juniper's Statement of IPR related to draft-ietf-l2vpn-vpls-mcast-04." The IETF Secretariat From loa@pi.nu Thu Mar 19 05:47:27 2009 Return-Path: <loa@pi.nu> 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 495B83A6A30; Thu, 19 Mar 2009 05:47:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=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 JmiEgI6FhzHj; Thu, 19 Mar 2009 05:47:26 -0700 (PDT) Received: from ns.elverljung.se (ns.elverljung.se [194.68.48.116]) by core3.amsl.com (Postfix) with ESMTP id 3E9B13A6A0B; Thu, 19 Mar 2009 05:47:26 -0700 (PDT) Received: from [10.4.169.87] (bgp-ext.core.365-24.net [217.151.192.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa) by ns.elverljung.se (Postfix) with ESMTPSA id 15BB02D84B8; Thu, 19 Mar 2009 13:48:08 +0100 (CET) Message-ID: <49C23F04.1040804@pi.nu> Date: Thu, 19 Mar 2009 13:48:04 +0100 From: Loa Andersson <loa@pi.nu> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: ccamp@ops.ietf.org, l2vpn@ietf.org, pwe3@ietf.org Subject: poll to make draft-busi-mpls-tp-oam-framework an mpls working group document 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Thu, 19 Mar 2009 12:47:27 -0000 Working Group, the authors of draft-busi-mpls-tp-oam-framework-02-02-1.txt has requested the document shall be accepted as a working group document. This is a one week poll to see if there are support for making it a working group document, please respond to the mpls-tp mailing list before Wednesday March 26. The document will be found at: http://www.tla-group.com/~loa/draft-busi-mpls-tp-oam-framework-02-02-1.txt Disclaimer: I've decided to start this poll even though the draft is not available from the IETF repository. /Loa -- Loa Andersson Sr Strategy and Standards Manager phone: +46 10 717 52 13 Ericsson /// +46 767 72 92 13 email: loa.andersson@ericsson.com loa.andersson@redback.com loa@pi.nu From Martin.Vigoureux@alcatel-lucent.com Fri Mar 20 05:29:50 2009 Return-Path: <Martin.Vigoureux@alcatel-lucent.com> 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 E255A3A6C6A; Fri, 20 Mar 2009 05:29:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 EbmKQ9YMoI7c; Fri, 20 Mar 2009 05:29:50 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id B6E383A6C6D; Fri, 20 Mar 2009 05:29:49 -0700 (PDT) Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2KCUBdV001884; Fri, 20 Mar 2009 13:30:33 +0100 Received: from [135.244.23.217] ([135.244.23.217]) by FRVELSBHS02.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Mar 2009 13:30:31 +0100 Message-ID: <49C38C62.8090609@alcatel-lucent.com> Date: Fri, 20 Mar 2009 13:30:26 +0100 From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Organization: Alcatel-Lucent User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: mpls@ietf.org Subject: slides for joint mpls-tp session Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Mar 2009 12:30:32.0313 (UTC) FILETIME=[A9396690:01C9A957] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Cc: ccamp@ops.ietf.org, l2vpn@ietf.org, pwe3@ietf.org, mpls-tp@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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Fri, 20 Mar 2009 12:29:51 -0000 all, could you please start sending the slides you will use for your presentation(s). Thanks. The joint wg session on mpls-tp is on Wednesday, 9:00-11:30 am http://www.ietf.org/proceedings/09mar/agenda/mpls.txt martin From shane@castlepoint.net Sun Mar 22 18:37:45 2009 Return-Path: <shane@castlepoint.net> 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 B14233A688C for <l2vpn@core3.amsl.com>; Sun, 22 Mar 2009 18:37:45 -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 p+ZG+WCDVals for <l2vpn@core3.amsl.com>; Sun, 22 Mar 2009 18:37:45 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id B3F4E3A67A4 for <l2vpn@ietf.org>; Sun, 22 Mar 2009 18:37:44 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id 13DE32684EA; Sun, 22 Mar 2009 19:38:34 -0600 (MDT) Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 22 Mar 2009 19:38:33 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=54761; data-bytes=0 Message-Id: <23AF11CD-1BB9-413A-9F34-B6C052723F2D@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 v930.3) Subject: IETF 74: Presentations Needed Date: Sun, 22 Mar 2009 19:38:31 -0600 X-Mailer: Apple Mail (2.930.3) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 23 Mar 2009 01:37:45 -0000 Hi Everyone, Thus far, we've received one presentation for the L2VPN WG meeting on Tuesday morning. For the rest of you holding a slot on Tuesday morning, can you please send your presentations to the chairs ASAP so they may be posted to the IETF Web site prior to the meeting? The agenda for the meeting can be found here: http://www.ietf.org/proceedings/09mar/agenda/l2vpn.txt Thanks! -shane & Vach From hshah@ciena.com Sun Mar 22 18:44:54 2009 Return-Path: <hshah@ciena.com> 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 2D0613A69E2 for <l2vpn@core3.amsl.com>; Sun, 22 Mar 2009 18:44:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.734 X-Spam-Level: X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[AWL=-0.550, BAYES_40=-0.185, 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 48jdhI6HV2bl for <l2vpn@core3.amsl.com>; Sun, 22 Mar 2009 18:44:53 -0700 (PDT) Received: from ripley.ciena.com (ripley.ciena.com [63.118.34.24]) by core3.amsl.com (Postfix) with ESMTP id 5E2EC3A6873 for <l2vpn@ietf.org>; Sun, 22 Mar 2009 18:44:53 -0700 (PDT) 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_01C9AB59.13639F82" Subject: clarification on draft-pkwok-l2vpn-vpls-macflush-ld-00.txt Date: Sun, 22 Mar 2009 21:45:42 -0400 Message-ID: <6535C9CED6F87446B41D20EF170F23623161D8@mamxm01.ciena.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: clarification on draft-pkwok-l2vpn-vpls-macflush-ld-00.txt Thread-Index: AcmrWRNCa8TcdLNCTfKxV7oG2m+MlQ== From: "Shah, Himanshu" <hshah@ciena.com> To: <l2vpn@ietf.org> X-OriginalArrivalTime: 23 Mar 2009 01:45:43.0086 (UTC) FILETIME=[13E31CE0:01C9AB59] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 23 Mar 2009 01:44:54 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9AB59.13639F82 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Paul/Pranjal, I read through this draft and would appreciate if you could clarify following things - 1) It wasn't exactly clear how the MAC flush loop would occur. It would help if you could give an example with the misconfiguration that you refer in the draft. 2) In the event of such a misconfiguration was to exist, do you believe that it is possible that a broadcast loop could also occur at data plane. If true, how do you resolve that? 3) Is it possible to detect such mis-wired/misconfigured PW with a built-in control plane mechanism, rather than after the fact, through looped mac-flush messages? thanks, himanshu ------_=_NextPart_001_01C9AB59.13639F82 Content-Type: text/html; charset="iso-8859-1" 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=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7654.12"> <TITLE>clarification on = draft-pkwok-l2vpn-vpls-macflush-ld-00.txt</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT SIZE=3D2>Hi Paul/Pranjal,<BR> <BR> I read through this draft and would appreciate if you<BR> could clarify following things -<BR> <BR> 1) It wasn't exactly clear how the MAC flush loop would<BR> occur. It would help if you could give an example with<BR> the misconfiguration that you refer in the draft.<BR> <BR> 2) In the event of such a misconfiguration was to exist,<BR> do you believe that it is possible that a broadcast<BR> loop could also occur at data plane. If true, how do = you<BR> resolve that?<BR> <BR> 3) Is it possible to detect such mis-wired/misconfigured PW<BR> with a built-in control plane mechanism, rather than = after<BR> the fact, through looped mac-flush messages?<BR> <BR> thanks,<BR> himanshu<BR> </FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C9AB59.13639F82-- From pdutta@alcatel-lucent.com Sun Mar 22 23:09:14 2009 Return-Path: <pdutta@alcatel-lucent.com> 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 B361C3A685D for <l2vpn@core3.amsl.com>; Sun, 22 Mar 2009 23:09:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.248 X-Spam-Level: X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 prWdo0Oglsrs for <l2vpn@core3.amsl.com>; Sun, 22 Mar 2009 23:09:13 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 42CDC3A67C1 for <l2vpn@ietf.org>; Sun, 22 Mar 2009 23:09:13 -0700 (PDT) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2N69xol001868 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 23 Mar 2009 07:09:59 +0100 Received: from INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 23 Mar 2009 07:09:58 +0100 Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Mon, 23 Mar 2009 11:37:37 +0530 From: "Dutta, Pranjal K (Pranjal)" <pdutta@alcatel-lucent.com> To: "Shah, Himanshu" <hshah@ciena.com>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 23 Mar 2009 11:35:53 +0530 Subject: RE: clarification on draft-pkwok-l2vpn-vpls-macflush-ld-00.txt Thread-Topic: clarification on draft-pkwok-l2vpn-vpls-macflush-ld-00.txt Thread-Index: AcmrWRNCa8TcdLNCTfKxV7oG2m+MlQAHXgkQ Message-ID: <C584046466ED224CA92C1BC3313B963E0358DE54EF@INBANSXCHMBSA3.in.alcatel-lucent.com> References: <6535C9CED6F87446B41D20EF170F23623161D8@mamxm01.ciena.com> In-Reply-To: <6535C9CED6F87446B41D20EF170F23623161D8@mamxm01.ciena.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C584046466ED224CA92C1BC3313B963E0358DE54EFINBANSXCHMBSA_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Cc: "Kwok, Paul \(Paul\)" <paul.kwok@alcatel-lucent.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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 23 Mar 2009 06:09:14 -0000 --_000_C584046466ED224CA92C1BC3313B963E0358DE54EFINBANSXCHMBSA_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Himanshu, Thanks for detailed review of the draft. Please refe= r more inline. Thanks, Pranjal ________________________________ From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hah, Himanshu Sent: Sunday, March 22, 2009 6:46 PM To: l2vpn@ietf.org Subject: clarification on draft-pkwok-l2vpn-vpls-macflush-ld-00.txt Hi Paul/Pranjal, I read through this draft and would appreciate if you could clarify following things - 1) It wasn't exactly clear how the MAC flush loop would occur. It would help if you could give an example with the misconfiguration that you refer in the draft. In general misconfiguration in the draft refers to break of VPLS split hori= zon rule among VPLS PEs in the core full mesh or loop resolution mechanism in dual-homing configuration in H-VP= LS. The specific methods to ensure split horizon or loop free connectivity in H-VPLS redundancy is kept out of= scope of the draft . Such methods could be either manual configuration or automated mechanisms/protocols used= to create loop free path in redundant topology. 2) In the event of such a misconfiguration was to exist, do you believe that it is possible that a broadcast loop could also occur at data plane. If true, how do you resolve that? That's correct. Such misconfiguration may cause loops/broadcast storms in d= atapath as well. However in this draft we are not proposing any solution for datapath loops and assumption is that= implementations may have loop detection methodologies based on the native service forwarding. Pls. note that loop d= etection in forwarding would take place only if there is data traffic flowing across. Mac flush messages are not really= "forwarded" by VPLS PEs , rather "propagated" by the PE's control plane, so we require a loop detection mechanism based o= n the characteristics of the control plane messaging. 3) Is it possible to detect such mis-wired/misconfigured PW with a built-in control plane mechanism, rather than after the fact, through looped mac-flush messages? To have such built-in control mechanism a reference for "good config" is ne= eded, which may not be possible locally in a VPLS PE device. What has been administratively provisioned (or misconf= igured) in a VPLS PE device is itself the starting point of reference. thanks, himanshu --_000_C584046466ED224CA92C1BC3313B963E0358DE54EFINBANSXCHMBSA_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>clarification on draft-pkwok-l2vpn-vpls-macflush-ld-00.t= xt</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD> <BODY> <DIV dir=3Dltr align=3Dleft><SPAN class=3D015391605-23032009><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>Hi Himanshu,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D015391605-23032009><FONT face=3DA= rial=20 color=3D#0000ff=20 size=3D2> = =20 Thanks for detailed review of the draft. Please refer=20 more inline.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D015391605-23032009><FONT face=3DA= rial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D015391605-23032009><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D015391605-23032009><FONT face=3DA= rial=20 color=3D#0000ff size=3D2>Pranjal</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>Shah,=20 Himanshu<BR><B>Sent:</B> Sunday, March 22, 2009 6:46 PM<BR><B>To:</B>=20 l2vpn@ietf.org<BR><B>Subject:</B> clarification on=20 draft-pkwok-l2vpn-vpls-macflush-ld-00.txt<BR></FONT><BR></DIV> <DIV></DIV><!-- Converted from text/plain format --> <P><FONT size=3D2>Hi Paul/Pranjal,<BR><BR>I read through this draft and wou= ld=20 appreciate if you<BR>could clarify following things -<BR><BR>1) It wasn't=20 exactly clear how the MAC flush loop would<BR> occur. It would = help=20 if you could give an example with<BR> the misconfiguration that= you=20 refer in the draft.<SPAN class=3D015391605-23032009><FONT face=3DArial=20 color=3D#0000ff> </FONT></SPAN></FONT></P> <P><FONT size=3D2><SPAN class=3D015391605-23032009><FONT face=3DArial color= =3D#0000ff>In=20 general misconfiguration in the draft refers to b</FONT></SPAN></FONT>= <SPAN=20 class=3D015391605-23032009><FONT face=3DArial color=3D#0000ff size=3D2>reak= of=20 </FONT></SPAN><SPAN class=3D015391605-23032009><FONT face=3DArial color=3D#= 0000ff=20 size=3D2>VPLS split horizon rule among VPLS PEs in the core <BR>full mesh o= r loop=20 resolution mechanism in dual-homing </FONT></SPAN><SPAN=20 class=3D015391605-23032009><FONT face=3DArial color=3D#0000ff size=3D2>conf= iguration in=20 </FONT></SPAN><FONT size=3D2><SPAN class=3D015391605-23032009><FONT face=3D= Arial=20 color=3D#0000ff>H-VPLS. The specific methods to ensure <BR>split horizon or= loop=20 free connectivity in H-VPLS redundancy is kept out of scope of the=20 draft . Such methods</FONT></SPAN></FONT><FONT size=3D2><SPAN=20 class=3D015391605-23032009><FONT face=3DArial color=3D#0000ff> <BR>cou= ld be=20 either manual configuration or automated mechanisms/protocols used&nbs= p;to=20 create loop free path in redundant <BR></FONT></SPAN><SPAN=20 class=3D015391605-23032009><FONT face=3DArial=20 color=3D#0000ff>topology. </FONT> </SPAN><BR><BR>2) In the event = of such=20 a misconfiguration was to exist,<BR> do you believe that it is= =20 possible that a broadcast<BR> loop could also occur at data pla= ne.=20 If true, how do you<BR> resolve that?</P></FONT><FONT size=3D2>= <SPAN=20 class=3D015391605-23032009></SPAN></FONT> <P><FONT size=3D2><SPAN class=3D015391605-23032009><FONT face=3DArial=20 color=3D#0000ff>That's correct. Such misconfiguration may cause=20 loops/broadcast storms in datapath as well. However in this draft<BR>w= e are=20 not proposing any solution for datapath loops and assumption is that=20 implementations may have loop detection <BR>methodologies based=20 </FONT></SPAN></FONT><FONT size=3D2><SPAN class=3D015391605-23032009><FONT= =20 face=3DArial color=3D#0000ff>on the native service forwarding. Pls. note th= at loop=20 detection in forwarding would take place only <BR>if there i= s=20 data traffic flowing across. Mac flush messages are not really=20 "forwarded" by VPLS PEs , rather "propagated" <BR>by the PE's con= trol=20 plane, so we require a loop detection mechanism based on the=20 characteristics of the control plane <BR>messaging.</FONT></SPAN></FONT><FO= NT=20 size=3D2><SPAN class=3D015391605-23032009> </SPAN></FONT></P> <P><FONT size=3D2><SPAN class=3D015391605-23032009> </SPAN><BR>3) Is i= t=20 possible to detect such mis-wired/misconfigured PW<BR> with a=20 built-in control plane mechanism, rather than after<BR> the fac= t,=20 through looped mac-flush messages?<SPAN class=3D015391605-23032009><FONT=20 face=3DArial color=3D#0000ff> </FONT></SPAN></FONT></P> <P><FONT size=3D2><SPAN class=3D015391605-23032009><FONT face=3DArial color= =3D#0000ff>To=20 have such built-in control mechanism a reference for "good config" is= =20 needed, which may not be possible locally<BR>in a VPLS PE device.=20 W</FONT></SPAN></FONT><FONT size=3D2><SPAN class=3D015391605-23032009><FONT= =20 face=3DArial color=3D#0000ff>hat has been administratively provisioned (or= =20 misconfigured) in a VPLS PE device</FONT></SPAN></FONT><FONT size=3D2><SPAN= =20 class=3D015391605-23032009><FONT face=3DArial color=3D#0000ff> is=20 itself <BR>the starting point of reference. </FONT></SPAN></FONT></P> <P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20 class=3D015391605-23032009></SPAN></FONT><FONT size=3D2><SPAN=20 class=3D015391605-23032009><FONT face=3DArial=20 color=3D#0000ff></FONT></SPAN><BR>thanks,<BR>himanshu<BR></P></FONT></BODY>= </HTML> --_000_C584046466ED224CA92C1BC3313B963E0358DE54EFINBANSXCHMBSA_-- From nitinb@juniper.net Sun Mar 22 23:58:41 2009 Return-Path: <nitinb@juniper.net> 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 4680D3A67B5; Sun, 22 Mar 2009 23:58: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=[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 pV2fkSfLI2I9; Sun, 22 Mar 2009 23:58:40 -0700 (PDT) Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id 4F0863A67A8; Sun, 22 Mar 2009 23:58:38 -0700 (PDT) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKScczT19BBW4hsi92haH9u9b4sm7O8lhS@postini.com; Sun, 22 Mar 2009 23:59:30 PDT Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Sun, 22 Mar 2009 23:58:33 -0700 Received: from emailcorp3.jnpr.net ([66.129.254.13]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sun, 22 Mar 2009 23:58:33 -0700 Received: from 172.23.5.253 ([172.23.5.253]) by emailcorp3.jnpr.net ([66.129.254.13]) with Microsoft Exchange Server HTTP-DAV ; Mon, 23 Mar 2009 06:58:32 +0000 User-Agent: Microsoft-Entourage/12.10.0.080409 Date: Mon, 23 Mar 2009 00:00:13 -0700 Subject: Re: [PWE3] poll to make draft-busi-mpls-tp-oam-framework an mpls working group document From: Nitin Bahadur <nitinb@juniper.net> To: Loa Andersson <loa@pi.nu>, <ccamp@ietf.org>, <l2vpn@ietf.org>, <pwe3@ietf.org> Message-ID: <C5EC818D.483E3%nitinb@juniper.net> Thread-Topic: [PWE3] poll to make draft-busi-mpls-tp-oam-framework an mpls working group document Thread-Index: AcmrhQM7cTK48B2SREKVJgZZK3zzMg== In-Reply-To: <49C23F04.1040804@pi.nu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Mar 2009 06:58:33.0376 (UTC) FILETIME=[C7DA1200:01C9AB84] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 23 Mar 2009 06:58:41 -0000 Support. On 3/19/09 5:48 AM, "Loa Andersson" <loa@pi.nu> wrote: > Working Group, > > > the authors of draft-busi-mpls-tp-oam-framework-02-02-1.txt has > requested the document shall be accepted as a working group document. > > This is a one week poll to see if there are support for making it a > working group document, please respond to the mpls-tp mailing list > before Wednesday March 26. > > The document will be found at: > > http://www.tla-group.com/~loa/draft-busi-mpls-tp-oam-framework-02-02-1.txt > > Disclaimer: I've decided to start this poll even though the draft is not > available from the IETF repository. > > > /Loa From mngpl@singnet.com.sg Mon Mar 23 01:42:26 2009 Return-Path: <mngpl@singnet.com.sg> 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 74CA63A6A0B for <l2vpn@core3.amsl.com>; Mon, 23 Mar 2009 01:42:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, 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 pA3jAChamDz9 for <l2vpn@core3.amsl.com>; Mon, 23 Mar 2009 01:42:25 -0700 (PDT) Received: from comsmtp1.singnet.com.sg (comsmtp1.singnet.com.sg [165.21.101.74]) by core3.amsl.com (Postfix) with ESMTP id 5EB703A69C3 for <l2vpn@ietf.org>; Mon, 23 Mar 2009 01:42:25 -0700 (PDT) Received: from pike.singnet.com.sg (pike.singnet.com.sg [165.21.101.112]) by comsmtp1.singnet.com.sg (8.14.1/8.13.6) with ESMTP id n2N8h1iY004080; Mon, 23 Mar 2009 16:43:01 +0800 Received: from pike.singnet.com.sg (localhost.localdomain [127.0.0.1]) by pike.singnet.com.sg (8.14.3/8.14.2) with ESMTP id n2N8gsTc011713; Mon, 23 Mar 2009 16:43:04 +0800 Received: (from cooluser@localhost) by pike.singnet.com.sg (8.14.3/8.14.2/Submit) id n2N8gsP3011712; Mon, 23 Mar 2009 16:42:54 +0800 X-Authentication-Warning: pike.singnet.com.sg: cooluser set sender to mngpl@singnet.com.sg using -f To: pdutta@alcatel-lucent.com Subject: Comments to LDP Extensions for Optimized MAC Address Withdrawal in H-VPLS Message-ID: <1237797774.49c74b8e4dfb3@discus.singnet.com.sg> Date: Mon, 23 Mar 2009 16:42:54 +0800 (SGT) From: mngpl@singnet.com.sg References: <6535C9CED6F87446B41D20EF170F23623161D8@mamxm01.ciena.com> In-Reply-To: <6535C9CED6F87446B41D20EF170F23623161D8@mamxm01.ciena.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: SingNet WebMail X-Mailman-Approved-At: Mon, 23 Mar 2009 07:26:30 -0700 Cc: l2vpn@ietf.org X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: mngpl@singnet.com.sg List-Id: <l2vpn.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 23 Mar 2009 08:42:26 -0000 Hi Pranjal, Just want to highlight a deployment scenario that I forsee will have interop issues. Although you stated in your paper regarding General Applicability of PE-ID TLV, however there could be a case in the field when provisioning PE-ID across the same VPLS VSI but spanning multiple PEs/mtu-s, the PE-ID is different per site. This could be due to misconfigurations or because of interop limitation between vendors. On the same figure 1 on your paper, if the same VPLS VSI is provisioned with same PE-ID between PE-4 and PE-2, but a different PE-ID between PE-2 and mtu-s. I forsee potential issue when Mtu-s switchover to PE-2, trigger a PE-ID but this is different between PE-2 and PE-4, which PE-2 will relay the PE-ID TLV. So I suggest that either every PE will have to do a lookup to match the corresponding PE-ID before forwarding or you be specific in the paper that PE-ID of the same VPLS VSI is the same throughout the whole domain. Generally, the draft has gone through 4 versions and has cover most scenarios. But just this above scenario that I've seen getting configured in the field that gets me worry. regards, Max From Rohit.Mediratta@alcatel-lucent.com Tue Mar 24 11:23:38 2009 Return-Path: <Rohit.Mediratta@alcatel-lucent.com> 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 1163F28C335 for <l2vpn@core3.amsl.com>; Tue, 24 Mar 2009 11:23:38 -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 HeiMi58QCBZT for <l2vpn@core3.amsl.com>; Tue, 24 Mar 2009 11:23:22 -0700 (PDT) Received: from audl951.usa.alcatel.com (audl951.usa.alcatel.com [143.209.238.161]) by core3.amsl.com (Postfix) with ESMTP id A2BA528C182 for <l2vpn@ietf.org>; Tue, 24 Mar 2009 11:23:21 -0700 (PDT) Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl951.usa.alcatel.com (ALCANET) with ESMTP id n2OIOCfv024143 for <l2vpn@ietf.org>; Tue, 24 Mar 2009 12:24:12 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 24 Mar 2009 13:24:12 -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_01C9ACAD.BAAE72A9" Subject: RE: Vpls-MIB response to comments at IETF 73 Date: Tue, 24 Mar 2009 13:24:11 -0500 Message-ID: <67FBA6A55FF15B46B8B572062529D26A03626541@USDALSMBS03.ad3.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Vpls-MIB response to comments at IETF 73 Thread-Index: AclVgif/lwlXCZVOQIimZWpJXn9WJgALsCvQACKpobAACCHqMAAAmJtgAAftLhAAANWWkADEnMGQFJHaEMAANIjJQA== From: "MEDIRATTA Rohit" <Rohit.Mediratta@alcatel-lucent.com> To: <l2vpn@ietf.org> X-OriginalArrivalTime: 24 Mar 2009 18:24:12.0346 (UTC) FILETIME=[BB0079A0:01C9ACAD] X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34 X-Mailman-Approved-At: Tue, 24 Mar 2009 12:12:31 -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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 24 Mar 2009 18:23:38 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9ACAD.BAAE72A9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Norival, Please find my answers inline to your questions inline. =20 thanks, Rohit=20 ________________________________ From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Norival Figueira Sent: Friday, December 05, 2008 2:26 PM To: l2vpn@ietf.org Subject: RE: Vpls-MIB response to comments at IETF 73 Hi Rohit, Thank you for addressing below the questions I asked at the 73rd IETF's L2VPN WG meeting. I would like to take this opportunity to further clarify those questions and answer your questions below. > ???: I have a few questions for clarification. When I read the MIB, there's a few things that I couldn't find: > + VPLS Instance ID in the Configuration Table; > + A way to define the desired Class of Service to be used by the VPLS instance to be used for tunnel selection; > > RM: Could we get some more information on the above two and why its a > good idea to add them to the next revision. VPLS Instance ID (VC ID): In the context of LDP signaling for VPLS defined in RFC4762, LDP is used for signaling a full mesh of pseudowires interconnecting VPLS instances. LDP pseudowire id (PWid) Forwarding Equivalence Class (FEC) element 128 was originally used to carry pseudowire parameters. This is still used and supported by most of the existing RFC4762 implementations in the market. Please note that although RFC4762 defines the use of the Generalized PWid FEC 129, it also describes the use of FEC 128 in Appendix A ("VPLS Signaling using the PWid FEC Element"), which states that "this section is being retained because live deployments use this version of the signaling for VPLS". Therefore, in order to support these existing implementations, one also needs to define a VPLS Instance Id (or VC Id). In this case, in each PE containing a VPLS instance for a given customer, the VPLS instance is configured with a same VPLS Instance ID, which has global significance across all PEs involved in the same VPLS instance. The VPLS instance ID is then used as the VC ID in the FEC element 128. PEs then correlate pseudowires with corresponding VPLS instances using the VC ID value contained in the FEC element 128. [rm] VC-ID is a per PW configuration, there is no requirement for this to be globally unique. VC-ID per PW is captured in the PW MIB. Bgp-Autodiscovery has a globally unique Vpls-Id which is captured in this MIB. The above reasoning also justifies Sanjay's question in your original message. VPLS Class of Service (CoS): Some service providers use a specific CoS for particular VPLS instances. In that case, the PE needs to choose an appropriate LSP such as an L-LSP that best satisfies the desired VPLS CoS. A VPLS CoS could be defined as a 3-bit value. How would a PE select appropriate LSPs in regards to CoS for each VPLS instance without an explicit definition in the VPLS MIB? [rm] Choosing a tunnel is a PW function. Still not convinced this belong in Vpls-MIB.=20 > + There are pointers to the Bridge-MIB, but if would be useful if there was > a place in MIB to define the maximum # of MAC addresses that should be > learned by a specific VPLS instance. > > RM: There was an object vplsPwBindMacAddressLimit in an earlier revision. > http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt > <http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt> > This was removed after suggestion from the group in Montreal-IETF, refer > to discussion in Montreal VPLS Maximum Number of MAC addresses: My understanding from the Montreal discussions is that the group was concerned with the definition in the VPLS MIB of features that are implementation specific. I also agree that implementation specific definitions should not be part of a standard VPLS MIB. However, defining the maximum number of MAC addressed for a VPLS instance is not an implementation specific issue. A VPLS maximum number of MAC addresses is needed to support service provider's L2VPN business models. Without this feature, service providers will not able to properly deploy large scale VPLS services. Service providers deploying VPLS as an L2VPN service usually define L2VPN business models with different service levels. For example (completely hypothetical), a service provider may define a customer VPLS service starting at a maximum of 40 MAC addresses and charge for additional increments of 40 MAC addresses. This business model allows the service provider to optimize MAC address table resources and to plan the capacity of its network in terms of the number of VPLS instances that can be supported by each PE (i.e., it allows the service provider to define admission control policies that take PEs' MAC address tables' capabilities into consideration). Defining a maximum number of MAC addresses per VPLS instance is also necessary to protect the network against customer (unintended or intended) MAC address storm attacks. Without a per VPLS (i.e., customer) limit, a single VPLS could consume the whole MAC address table available in a PE. This would cause service disruption to other VPLS customers. Please note that the maximum number of MAC addresses discussed here is a VPLS instance property. The MAC address limits defined earlier in vplsLdpPwBindMacAddressLimit (which was later removed) and in vplsPwBindMacAddressLimit (which is still defined in the current VPLS MIB draft), represent something else and are not appropriate to provide an overall VPLS MAC address limit. An overall VPLS MAC address limit does not care for how many MAC addresses were learned by specific PWs or endpoint interfaces. An overall VPLS MAC address limit is what service providers care about to implement their L2VPN business models and to allow for the proper management and protection of individual VPLS services. Please note that with the advent of PBB-VPLS integration, customer MAC addresses will no longer be learned by VPLS instances. This could be used by someone as an argument against the inclusion of a VPLS MAC limit in the VPLS MIB. However, the VPLS MIB must be applicable to existing deployments where PBB-VPLS integration is not used. Please note that customer MAC addresses will be learned by PEs that also provide PBB Backbone Edge Bridge (BEB)functionality, but this is a subject for a separate discussion on a PBB-VPLS thread. [rm] Point well taken, we will certainly deliberate over this in the next revision. It will be good to understand what is the level of interest for this. > + It would be useful if there was a way to allow someone to clear the MAC > addresses in a VPLS instance. > > RM: Should this exist in the Vpls-MIB ? Why ? VPLS Clear MAC Addresses: The group has been discussing different ways to flush the learned MAC address of a VPLS instance to support dual homing. In simple terms, with dual homing a CPE (customer premises equipment) could be physically attached to two PEs supporting a VPLS service for the customer. Only one PE would initially forward the customer traffic. In the event that the active PE lost connectivity to the CPE or the PE itself failed, the other PE would take over the responsibility of forwarding the customer traffic. Without further actions, this could create a "black hole" effect where other PE's in the network would continue to send traffic to the original PE until learned MAC entries aged out or were re-learned to point to the new PE as the proper destination. To solve this problem, one can use explicit MAC withdraw (or flush) messages or implicit mechanisms to determined that a MAC flush is required. In both cases, a MAC flush is only issued when there is a VPLS service switchover from on PE to another PE in a dual homing scenario. The case exists for allowing one to manually (administratively) flush the learned MAC addresses of a VPLS instances (for dual homing and non-dual homing scenarios). This is useful for debugging purposes (e.g., the service provider wants to re-start MAC learning for a particular VPLS instance) and also for allowing the manual switchover of service from one PE to another (e.g., in a non-dual homing scenario). [rm] Do we have further interest in this being added to Vpls-MIB ?=20 > + You point to Bridge-MIB, but I don't see a clear identification of the > interfaces that are bound to a VPLS instance. I see that for the PW > side, but I don't see that for the interfaces. > > RM: This is the issue where AC is a PW. We've raised this a few times > and have not really > been able to solicit a clear approach to tackling this. VSIs are interconnected by a full mesh of network pseudowires. To provide services to customers a VSI must also support port mode and tagged mode (VLAN) attachments (or endpoints). My question regards these two types. Analogous to the PW bind table defined in the VPLS MIB, one could have an explicit attachment bind table (possibly indexed by vplsConfigIndex and ifindex of endpoint). There seems to be a lean towards SNMP Context Mapping MIB to represent the endpoints. However, this seems to only apply in the context of SNMP v3. For SNMPv2c and SNMPv1, each context will need to be mapped to a community string, which will need to be configured on the management station. This seems impractical, since any number of VPLS instances are possible, with each one having its own unique endpoint attachments. Regards, Norival Figueira ---------------------------------------------------------------------- Date: Tue, 2 Dec 2008 17:38:32 -0600 From: "MEDIRATTA Rohit" <Rohit.Mediratta@alcatel-lucent.com> Subject: Vpls-MIB response to comments at IETF 73 To: <l2vpn@ietf.org> Cc: Agrahara S Kiran Koushik <kkoushik@cisco.com> Message-ID: =20 <67FBA6A55FF15B46B8B572062529D26A03038B77@USDALSMBS03.ad3.ad.alcatel.com > =20 Content-Type: text/plain; charset=3D"us-ascii" Hi All, Please find the response to the questions raised w.r.t to VPLS-MIB at IETF-73. The response to the questions are preprended with RM: Regards, Rohit, Kiran & Tom. ----------------------------- Questions: - Kireeti Kompella: You say that VplsBgpRteTargetEntry allows H-VPLS representation, but that seems pretty orthogonal. Can you explain that? RM: RT's can be used to filter which "l2vpn route" should be accepted by each Node. Consider the following setup A-----B------C------D | | | | E F Assuming Vpls/Bgp on A is setup to import RT from B only, export RT-A. Vpls/Bgp on B is setup to import RT from A,C and E, export RT-B Vpls/Bgp on C is setup to import RT from B,D and F, export RT-C Vpls/Bgp on D is setup to import RT from C only, export RT-D. Vpls/Bgp on E is setup to import RT from B only, export RT-E. Vpls/Bgp on F is setup to import RT from C only, export RT-F. This will lead to the following PW Setup. A----B=3D=3D=3D=3D=3DC----D | | | | E F This gives Providers the flexibility to engineer the Auto-discovered PW's. To provide the ability to import/export multiple RT's per Vpls we needed to break RT into a separate table. - ???: I have a few questions for clarification. When I read the MIB, there's a few things that I couldn't find: + VPLS Instance ID in the Configuration Table; + A way to define the desired Class of Service to be used by the VPLS instance to be used for tunnel selection; RM: Could we get some more information on the above two and why its a good idea to add them to the next revision. + There are pointers to the Bridge-MIB, but if would be useful if there was a place in MIB to define the maximum # of MAC addresses that should be learned by a specific VPLS instance. RM: There was an object vplsPwBindMacAddressLimit in an earlier revision. http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt <http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt> This was removed after suggestion from the group in Montreal-IETF, refer to discussion in Montreal + It would be useful if there was a way to allow someone to clear the MAC addresses in a VPLS instance. RM: Should this exist in the Vpls-MIB ? Why ? + You point to Bridge-MIB, but I don't see a clear identification of the interfaces that are bound to a VPLS instance. I see that for the PW side, but I don't see that for the interfaces. RM: This is the issue where AC is a PW. We've raised this a few times and have not really been able to solicit a clear approach to tackling this. - Sanjay (?): MIB you're using for configuration doesn't support old FEC Type using VC ID. There are a lot of existing installations today that are using FEC 128 and all of them depend on the VC ID for the identifier of the VPLS instance. Would like you to consider in the VPLS instance, if you can add the VC ID as a field so that older installations can also be included. RM: Vpls MIB is FEC Type agnostic. FEC 128 and FEC 129 are in the PW-MIB. Also, VC Id is only an identifier for a PW. Not the Vpls. ------------------------------ _______________________________________________ L2vpn mailing list L2vpn@ietf.org https://www.ietf.org/mailman/listinfo/l2vpn End of L2vpn Digest, Vol 55, Issue 2 ************************************ ------_=_NextPart_001_01C9ACAD.BAAE72A9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>RE: Vpls-MIB response to comments at IETF 73</TITLE> <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=3D178402000-09122008><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D939372218-24032009>Hi Norival,</SPAN></FONT></FONT></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D939372218-24032009> Please find my answers inline to = your=20 questions inline.</SPAN></FONT></FONT></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D939372218-24032009></SPAN></FONT></FONT></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D939372218-24032009>thanks,</SPAN></FONT></FONT></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT = color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D939372218-24032009>Rohit </SPAN></FONT></FONT></FONT><BR></D= IV> <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>Norival=20 Figueira<BR><B>Sent:</B> Friday, December 05, 2008 2:26 PM<BR><B>To:</B> = l2vpn@ietf.org<BR><B>Subject:</B> RE: Vpls-MIB response to comments at = IETF=20 73<BR></FONT><BR></DIV> <DIV></DIV><!-- Converted from text/rtf format --> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>Hi = Rohit,</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Thank you for=20 addressing below the questions I asked at the 73rd IETF's L2VPN WG = meeting. I=20 would like to take this opportunity to further clarify those questions = and=20 answer your questions below.</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = ???: I have a=20 few questions for clarification. When I read the MIB,=20 there</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" = size=3D2>’</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2>s</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> a few things=20 that I couldn't find:</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>> + VPLS=20 Instance ID in the Configuration Table;</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>> + A way=20 to define the desired Class of Service to be used by the VPLS instance = to be=20 used for tunnel selection;</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = RM: Could we=20 get some more information on the above two and why its = a</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = good idea to=20 add them to the next revision.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>VPLS = Instance ID (VC=20 ID):</FONT></SPAN></P> <P dir=3Dltr><FONT size=3D2><SPAN lang=3Den-us><FONT face=3D"Courier = New">In the context=20 of LDP signaling for VPLS defined in RFC4762, LDP is used for signaling = a full=20 mesh of pseudowires interconnecting VPLS instances. LDP pseudowire id = (PWid)=20 Forwarding Equivalence Class (FEC) element 128 was originally used to = carry=20 pseudowire parameters. This is still used and supported by most of the = existing=20 RFC4762 implementations in the market. Please note that although RFC4762 = defines=20 the use of the Generalized PWid FEC 129, it also describes the use of = FEC 128 in=20 Appendix A ("VPLS Signaling using the PWid FEC Element"), which states = that=20 "</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us><FONT face=3D"Courier New">t</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></FONT><SPAN lang=3Den-us><FONT face=3D"Courier = New"><FONT=20 size=3D2>his section is being retained because live deployments use this = version=20 of the signaling for VPLS". Therefore, in order to support these = existing=20 implementations, one also needs to define a VPLS Instance Id (or VC Id). = In this=20 case, in each PE containing a VPLS instance for a given customer, the = VPLS=20 instance is configured with a same VPLS Instance ID, which has global=20 significance across all PEs involved in the same VPLS instance. The VPLS = instance ID is then used as the VC ID in the FEC element 128. PEs then = correlate=20 pseudowires with corresponding VPLS instances using the VC ID value = contained in=20 the FEC element 128.<BR><SPAN class=3D178402000-09122008><FONT = face=3DArial=20 color=3D#0000ff>[rm] VC-ID is a per PW configuration, there is no = requirement=20 for this to be globally unique. VC-ID per PW is captured = in the=20 PW MIB. Bgp-Autodiscovery has a globally unique Vpls-Id which is = captured in=20 this MIB.</FONT></SPAN></FONT></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>The = above reasoning=20 also justifies Sanjay's question</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>in your=20 original message</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>VPLS = Class of=20 Service (CoS):</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>S</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2>ome</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>service=20 providers</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>use a specific CoS for = particular=20 VPLS</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2> = instances</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2>. In that case, the PE needs to=20 choose</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>an</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> appropriate LSP such as = a</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2>n</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> L-LSP=20 that</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>best</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>satisfies the</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>desired</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>VPLS</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>CoS</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2>.</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>A VPLS CoS=20 could be defined as a 3-bit value.</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>H</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>ow would a PE select = appropriate LSPs=20 in regard</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>s</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> to CoS</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>for each=20 VPLS instance</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New"><FONT size=3D2>without an = explicit definition=20 in the VPLS MIB?<BR><SPAN class=3D178402000-09122008><FONT face=3DArial=20 color=3D#0000ff>[rm] Choosing a tunnel is a PW function. Still not = convinced=20 this belong in = Vpls-MIB. </FONT></SPAN></FONT></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = + There are=20 pointers to the Bridge-MIB, but if would be useful if there=20 was</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = a place in MIB=20 to define the maximum # of MAC addresses that should = be</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = learned by a=20 specific VPLS instance.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = RM: There was=20 an object vplsPwBindMacAddressLimit in an earlier = revision.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = <A=20 href=3D"http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt">http= ://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt</A></FONT></SPAN>= </P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = <<A=20 href=3D"http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt">http= ://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt</A>></FONT></S= PAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = This was=20 removed after suggestion from the group in Montreal-IETF,=20 refer</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = to discussion=20 in Montreal</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>VPLS = Maximum Number=20 of MAC addresses:</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>My = understanding=20 from the Montreal discussions is that the group was concerned with the=20 definition in the VPLS MIB of features that are implementation specific. = I also=20 agree that implementation specific definitions should not be part of a = standard=20 VPLS MIB. However, defining the maximum number of MAC addressed for a = VPLS=20 instance is not an implementation specific issue. A VPLS maximum number = of MAC=20 addresses is needed to support service provider's L2VPN business models. = Without=20 this feature, service providers will not able to properly deploy large = scale=20 VPLS services.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Service providers=20 deploying VPLS as an L2VPN service usually define L2VPN business models = with=20 different service levels. For example (completely hypothetical), a = service=20 provider may define a customer VPLS service starting at a maximum of 40 = MAC=20 addresses and charge for additional increments of 40 MAC addresses. This = business model allows the service provider to optimize MAC address table = resources and to plan the capacity of its network in terms of the number = of VPLS=20 instances that can be supported by each PE (i.e., it allows the service = provider=20 to define admission control policies that take PEs' MAC address tables'=20 capabilities into consideration). Defining a maximum number of MAC = addresses per=20 VPLS instance is also necessary to protect the network against customer=20 (unintended or intended) MAC address storm attacks. Without a per VPLS = (i.e.,=20 customer) limit, a single VPLS could consume the whole MAC address table = available in a PE. This would cause service disruption to other VPLS=20 customers.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Please note that the=20 maximum number of MAC addresses discussed here is a VPLS instance = property. The=20 MAC address limits defined earlier in vplsLdpPwBindMacAddressLimit = (which was=20 later removed) and in vplsPwBindMacAddressLimit (which is still defined = in the=20 current VPLS MIB draft), represent something else and are not = appropriate to=20 provide an overall VPLS</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>MAC</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>address limit. An = overall VPLS MAC=20 address limit does not care for how many MAC addresses were learned by = specific=20 PWs or endpoint interfaces. An overall VPLS MAC address limit is what = service=20 providers care about to implement their L2VPN business models and to = allow for=20 the proper management and protection of individual VPLS=20 services.</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Please note that=20 with the advent of PBB</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>-VPLS=20 integration, customer MAC addresses</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>will</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2> no = longer</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>be</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>learn</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>ed</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2></FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>by</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2> VPLS instances. This = could be=20 used</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>by = someone</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>as an argument against = the</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> inclusion of a VPLS MAC limit in the VPLS = MIB.=20 However, the VPLS MIB must be applicable to existing deployments where = PBB-VPLS=20 integration is not used.</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2></FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>Please</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> note that customer MAC addresses will be = learned by=20 PEs that also provide PBB Backbone Edge Bridge (BEB)functionality, but=20 th</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>is</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> is a subject for</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>a</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2></FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>separate</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>discussion</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>on=20 a</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us>=20 <FONT face=3D"Courier New" size=3D2>PBB-VPLS</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2></FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"><FONT = size=3D2>thread.<BR><SPAN class=3D178402000-09122008><FONT face=3DArial=20 color=3D#0000ff>[rm] Point well taken, we will certainly deliberate = over this=20 in the next revision. It will be good to understand what is the level of = interest for this.</FONT></SPAN></FONT></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = + It would be=20 useful if there was a way to allow someone to clear the = MAC</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>> addresses=20 in a VPLS instance.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = RM: Should this=20 exist in the Vpls-MIB ? Why ?</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>VPLS = Clear MAC=20 Addresses:</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>The = group has been=20 discussing different ways to flush the learned MAC address of a VPLS = instance to=20 support dual homing. In simple terms, with dual homing a CPE (customer=20 premises</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>equipment</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New"><FONT size=3D2>) could be physically attached to = two PEs=20 supporting a VPLS service for the customer. Only one PE would initially = forward=20 the customer traffic. In the event that the active PE lost connectivity = to the=20 CPE or the PE itself failed, the other PE would take over the = responsibility of=20 forwarding the customer traffic. Without further actions, this could = create a=20 "black hole" effect where other PE's in the network would continue to = send=20 traffic to the original PE until learned MAC entries aged out or were = re-learned=20 to point to the new PE as the proper destination. To solve this problem, = one can=20 use explicit MAC withdraw (or flush) messages or implicit mechanisms to=20 determined that a MAC flush is required. In both cases, a MAC flush is = only=20 issued when there is a VPLS service switchover from on PE to another PE = in a=20 dual homing scenario. The case exists for allowing one to manually=20 (administratively) flush the learned MAC addresses of a VPLS instances = (for dual=20 homing and non-dual homing scenarios). This is useful for debugging = purposes=20 (e.g., the service provider wants to re-start MAC learning for a = particular VPLS=20 instance) and also for allowing the manual switchover of service from = one PE to=20 another (e.g., in a non-dual homing scenario).<BR><SPAN=20 class=3D178402000-09122008><FONT face=3DArial = color=3D#0000ff>[rm] Do we=20 have further interest in this being added to Vpls-MIB=20 ? </FONT></SPAN></FONT></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = + You point to=20 Bridge-MIB, but I don't see a clear identification of = the</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>> =20 interfaces that are bound to a VPLS instance. I see that for the=20 PW</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = side, but I=20 don't see that for the interfaces.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = RM: This is the=20 issue where AC is a PW. We've raised this a few times</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = and have not=20 really</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>> = been able to=20 solicit a clear approach to tackling this.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>VSIs are interconnected = by a full=20 mesh of network pseudowires. To provide services to customers a VSI must = also=20 support port mode and tagged mode (VLAN) attachments (or endpoints). My = question=20 regards these two types. Analogous to the PW bind table defined in the = VPLS MIB,=20 one could have an explicit attachment bind table (possibly indexed by=20 vplsConfigIndex and ifindex of endpoint).</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>There seems to be a = lean towards SNMP=20 Context Mapping MIB to represent the endpoints.</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2></FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New" = size=3D2>However,=20 this seems to only apply in the context of SNMP v3. For SNMPv2c and = SNMPv1, each=20 context will need to be mapped to</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>a</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>community string, = which will need to=20 be configured on the management station. This</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT=20 face=3D"Courier New" size=3D2>seems</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>=20 impractical</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>,</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> since</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>any</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2> number of VPLS = instances are=20 possible</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>, = with</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2> each</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3D"Courier New"=20 size=3D2>one</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us> <FONT face=3D"Courier New" size=3D2>having its own unique = endpoint=20 attachment</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us><FONT face=3D"Courier New" size=3D2>s</FONT></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT=20 face=3D"Courier New" size=3D2>.</FONT></SPAN><SPAN = lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us></SPAN><SPAN=20 lang=3Den-us></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>Regards,</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Norival=20 Figueira</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>----------------------------------------------------------------= ------</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Date: Tue, 2 Dec=20 2008 17:38:32 -0600</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>From: "MEDIRATTA=20 Rohit" <Rohit.Mediratta@alcatel-lucent.com></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Subject: Vpls-MIB=20 response to comments at IETF 73</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>To:=20 <l2vpn@ietf.org></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>Cc: = Agrahara S Kiran=20 Koushik <kkoushik@cisco.com></FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>Message-ID:</FONT></SPAN></P> <P dir=3Dltr><SPAN = lang=3Den-us> <FONT=20 face=3D"Courier New"=20 size=3D2><67FBA6A55FF15B46B8B572062529D26A03038B77@USDALSMBS03.ad3.ad.= alcatel.com></FONT></SPAN></P> <P dir=3Dltr><SPAN = lang=3Den-us> =20 </SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Content-Type:=20 text/plain; =20 charset=3D"us-ascii"</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>Hi=20 All,</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> Please=20 find the response to the questions raised w.r.t to VPLS-MIB = at</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>IETF-73.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>The = response to the=20 questions are preprended with RM:</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>Regards,</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Rohit, Kiran &=20 Tom.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>-----------------------------</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> Questions:</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>- = Kireeti Kompella:=20 You say that VplsBgpRteTargetEntry allows H-VPLS</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>representation, but=20 that seems pretty orthogonal. Can you explain = that?</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>RM: = RT's can be used=20 to filter which "l2vpn route" should be accepted by</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>each = Node.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Consider the=20 following setup</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>A-----B------C------D</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> | =20 |</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> | =20 |</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> E =20 F</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>Assuming</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Vpls/Bgp on A is=20 setup to import RT from B only, export RT-A.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Vpls/Bgp on B is=20 setup to import RT from A,C and E, export RT-B</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Vpls/Bgp on C is=20 setup to import RT from B,D and F, export RT-C</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Vpls/Bgp on D is=20 setup to import RT from C only, export RT-D.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Vpls/Bgp on E is=20 setup to import RT from B only, export RT-E.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>Vpls/Bgp on F is=20 setup to import RT from C only, export RT-F.</FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>This = will lead to=20 the following PW Setup.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>A----B=3D=3D=3D=3D=3DC----D</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> | = |</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> | = |</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2> E = F</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>This = gives Providers=20 the flexibility to engineer the Auto-discovered</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>PW's.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>To = provide the=20 ability to import/export multiple RT's per Vpls we = needed</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>to = break RT into a=20 separate table.</FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>- = ???: I have a few=20 questions for clarification. When I read the = MIB,</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>there's</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>a = few things that I=20 couldn't find:</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> + VPLS=20 Instance ID in the Configuration Table;</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> + A way to=20 define the desired Class of Service to be used by the = VPLS</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> instance to=20 be used for tunnel selection;</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>RM: = Could we get=20 some more information on the above two and why its a</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>good = idea to add=20 them to the next revision.</FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>+ = There are pointers=20 to the Bridge-MIB, but if would be useful if there</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>was</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> a place in=20 MIB to define the maximum # of MAC addresses that should = be</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> learned by a=20 specific VPLS instance.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>RM: = There was an=20 object vplsPwBindMacAddressLimit in an earlier</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>revision.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2><A=20 href=3D"http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt">http= ://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt</A></FONT></SPAN>= </P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2><<A=20 href=3D"http://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt">http= ://tools.ietf.org/id/draft-nadeau-l2vpn-vpls-mib-00.txt</A>></FONT></S= PAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>This = was removed=20 after suggestion from the group in Montreal-IETF, = refer</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>to = discussion in=20 Montreal</FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>+ It = would be useful=20 if there was a way to allow someone to clear the</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>MAC</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> addresses in=20 a VPLS instance.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>RM: = Should this=20 exist in the Vpls-MIB ? Why ?</FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>+ = You point to=20 Bridge-MIB, but I don't see a clear identification of = the</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> interfaces=20 that are bound to a VPLS instance. I see that for the = PW</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>side,</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> but I don't=20 see that for the interfaces.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>RM: = This is the=20 issue where AC is a PW. We've raised this a few times</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>and = have not=20 really</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>been = able to solicit=20 a clear approach to tackling this.</FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>- = Sanjay (?): MIB=20 you're using for configuration doesn't support old FEC</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>Type</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>using VC ID. =20 There are a lot of existing installations today that = are</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>using</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>FEC = 128 and all of=20 them depend on the VC ID for the identifier of the</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>VPLS</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>instance. =20 Would like you to consider in the VPLS instance, if you = can</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>add=20 the</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>VC = ID as a field so=20 that older installations can also be included.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>RM: = Vpls MIB is FEC=20 Type agnostic. FEC 128 and FEC 129 are in the</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>PW-MIB.</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2> =20 Also, VC Id is only an identifier for a PW. Not the=20 Vpls.</FONT></SPAN></P><BR><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>------------------------------</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>_______________________________________________</FONT></SPAN></P= > <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" = size=3D2>L2vpn mailing=20 list</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>L2vpn@ietf.org</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2><A=20 href=3D"https://www.ietf.org/mailman/listinfo/l2vpn">https://www.ietf.org= /mailman/listinfo/l2vpn</A></FONT></SPAN></P><BR> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New" size=3D2>End = of L2vpn Digest,=20 Vol 55, Issue 2</FONT></SPAN></P> <P dir=3Dltr><SPAN lang=3Den-us><FONT face=3D"Courier New"=20 size=3D2>************************************</FONT></SPAN></P></BODY></H= TML> ------_=_NextPart_001_01C9ACAD.BAAE72A9-- From pdutta@alcatel-lucent.com Tue Mar 24 20:05:23 2009 Return-Path: <pdutta@alcatel-lucent.com> 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 0B9B43A6945 for <l2vpn@core3.amsl.com>; Tue, 24 Mar 2009 20:05:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 3kZrEhzfARwZ for <l2vpn@core3.amsl.com>; Tue, 24 Mar 2009 20:05:22 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id E3D893A6881 for <l2vpn@ietf.org>; Tue, 24 Mar 2009 20:05:21 -0700 (PDT) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2P36B2U007055 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 25 Mar 2009 04:06:11 +0100 Received: from INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 25 Mar 2009 04:06:11 +0100 Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Wed, 25 Mar 2009 08:36:09 +0530 From: "Dutta, Pranjal K (Pranjal)" <pdutta@alcatel-lucent.com> To: "mngpl@singnet.com.sg" <mngpl@singnet.com.sg> Date: Wed, 25 Mar 2009 08:35:41 +0530 Subject: RE: Comments to LDP Extensions for Optimized MAC Address Withdrawal in H-VPLS Thread-Topic: Comments to LDP Extensions for Optimized MAC Address Withdrawal in H-VPLS Thread-Index: Acmrk2+XZeN7xtMmRIWMtZdi5YOaLgBXh53g Message-ID: <C584046466ED224CA92C1BC3313B963E0358DE5A1D@INBANSXCHMBSA3.in.alcatel-lucent.com> References: <6535C9CED6F87446B41D20EF170F23623161D8@mamxm01.ciena.com> <1237797774.49c74b8e4dfb3@discus.singnet.com.sg> In-Reply-To: <1237797774.49c74b8e4dfb3@discus.singnet.com.sg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Cc: "l2vpn@ietf.org" <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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 25 Mar 2009 03:05:23 -0000 Hi Max, =20 Please refer inline.=20 Thanks, Pranjal -----Original Message----- From: mngpl@singnet.com.sg [mailto:mngpl@singnet.com.sg]=20 Sent: Monday, March 23, 2009 1:43 AM To: Dutta, Pranjal K (Pranjal) Cc: l2vpn@ietf.org Subject: Comments to LDP Extensions for Optimized MAC Address Withdrawal in= H-VPLS=20 Hi Pranjal, Just want to highlight a deployment scenario that I forsee will have intero= p issues. Although you stated in your paper regarding General Applicability= of PE-ID TLV, however there could be a case in the field when provisioning= PE-ID across the same VPLS VSI but spanning multiple PEs/mtu-s, the PE-ID = is different per site. This could be due to misconfigurations or because of= interop limitation between vendors. <=20 The PE-ID is not provisioned and is derived from the VSI-ID of a VPLS ins= tance in the n-PE that hosts the dual homes u-PEs. This would be=20 always unique across a VPLS instance. > On the same figure 1 on your paper, if the same VPLS VSI is provisioned wit= h same PE-ID between PE-4 and PE-2, but a different PE-ID between PE-2 and = mtu-s. I forsee potential issue when Mtu-s switchover to PE-2, trigger a PE= -ID but this is different between PE-2 and PE-4, which PE-2 will relay the = PE-ID TLV. < Didn't get exactly. Did you mean that PE-4 and PE-2 are configured with s= ame VSI-ID in the vpls instance. Let's say in FEC128 case, the PE-ID is (vc-id + 4 byte ldp lsr-id) on PE. Did you mean miscon= figuration of LDP with same lsr-id in PE4 and PE-2? In FEC129 case, PE-ID is (AGI + AII) on PE. Did you mean misconfiguration= that would cause PE-4 and PE-2 to have same AII? In Figure 1, if MTU-s switches over to PE-2 from PE-1, then MTU-s would i= nitiate flush with PE-ID to indicate=20 the VSI in PE-1. PE-2 would relay the mac flush to all n-Pes in mesh with= same PE-ID (of PE-1). > So I suggest that either every PE will have to do a lookup to match the cor= responding PE-ID before forwarding or you be specific in the paper that PE-= ID of the same VPLS VSI is the same throughout the whole domain. < Yes, PE-ID of the same VPLS VSI is same throughout the whole domain, since= PE-ID is derived from VSI-ID in a VPLS and VSI-ID has to be=20 unique across all participating PE devices in a VPLS instance (unless misc= onfigured). If it's not explicit in the draft, definitely we=20 would address it in detail. > Generally, the draft has gone through 4 versions and has cover most scenari= os. But just this above scenario that I've seen getting configured in the f= ield that gets me worry. regards, Max From shane@castlepoint.net Sun Mar 29 19:01:23 2009 Return-Path: <shane@castlepoint.net> 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 386593A6C2B for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:01:23 -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 T00cOPPiVBCn for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:01:23 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 1B6E33A6B99 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 19:01:23 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id 861512684EA; Sun, 29 Mar 2009 20:02:20 -0600 (MDT) Received: from mbpw.castlepoint.net (71-215-84-148.hlrn.qwest.net [71.215.84.148]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 29 Mar 2009 20:02:20 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.84.148; client-port=3367; syn-fingerprint=65535:55:1:64:M1452,N,W3,N,N,T,S; data-bytes=0 Message-Id: <E19DDA8E-4BA7-4E22-B5E6-402B08F27C88@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 v930.3) Subject: IETF 74: DRAFT l2vpn WG Meeting Minute Date: Sun, 29 Mar 2009 20:02:05 -0600 X-Mailer: Apple Mail (2.930.3) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 02:01:23 -0000 Hi All, The WG meeting minutes have been posted to the IETF Web Site: http://www.ietf.org/proceedings/09mar/minutes/l2vpn.txt Please review them and if you have any comments or corrections, please e-mail the chairs. The deadline for corrections is Friday, April 17. Finally, we would like to thank Laurent Ciavaglia for taking the minutes. -shane & Vach From shane@castlepoint.net Sun Mar 29 19:39:12 2009 Return-Path: <shane@castlepoint.net> 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 CBE663A68AF for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:39:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.869 X-Spam-Level: X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[AWL=0.248, 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 ohijulm2vu1x for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:39:12 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 233F93A68E6 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 19:39:12 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id ADBBB2684EA; Sun, 29 Mar 2009 20:40:09 -0600 (MDT) Received: from mbpw.castlepoint.net (71-215-84-148.hlrn.qwest.net [71.215.84.148]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 29 Mar 2009 20:40:09 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.84.148; client-port=3459; syn-fingerprint=65535:55:1:64:M1452,N,W3,N,N,T,S; data-bytes=0 Message-Id: <4E65056A-207D-4350-A5AC-25F0D8D389AC@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 v930.3) Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Date: Sun, 29 Mar 2009 20:39:53 -0600 X-Mailer: Apple Mail (2.930.3) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 02:39:12 -0000 Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft: http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From shane@castlepoint.net Sun Mar 29 19:42:07 2009 Return-Path: <shane@castlepoint.net> 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 8BCDE3A69D2 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:42:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.931 X-Spam-Level: X-Spam-Status: No, score=-0.931 tagged_above=-999 required=5 tests=[AWL=0.186, 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 JWiDI4r7EoSw for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:42:06 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id DB3403A69D0 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 19:42:06 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id 86BED2684EA; Sun, 29 Mar 2009 20:43:04 -0600 (MDT) Received: from mbpw.castlepoint.net (71-215-84-148.hlrn.qwest.net [71.215.84.148]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 29 Mar 2009 20:43:04 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.84.148; client-port=4232; syn-fingerprint=65535:55:1:64:M1452,N,W3,N,N,T,S; data-bytes=0 Message-Id: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@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 v930.3) Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Sun, 29 Mar 2009 20:42:49 -0600 X-Mailer: Apple Mail (2.930.3) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 02:42:07 -0000 Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From shane@castlepoint.net Sun Mar 29 19:48:57 2009 Return-Path: <shane@castlepoint.net> 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 A58A33A698F for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:48:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.968 X-Spam-Level: X-Spam-Status: No, score=-0.968 tagged_above=-999 required=5 tests=[AWL=0.149, 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 4uCFJ-by8Pma for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 19:48:57 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 056DF3A68AF for <l2vpn@ietf.org>; Sun, 29 Mar 2009 19:48:57 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id A90602684EA; Sun, 29 Mar 2009 20:49:54 -0600 (MDT) Received: from mbpw.castlepoint.net (71-215-84-148.hlrn.qwest.net [71.215.84.148]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 29 Mar 2009 20:49:54 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.84.148; client-port=3503; syn-fingerprint=65535:55:1:64:M1452,N,W3,N,N,T,S; data-bytes=0 Message-Id: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@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 v930.3) Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Sun, 29 Mar 2009 20:49:39 -0600 X-Mailer: Apple Mail (2.930.3) 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 02:48:57 -0000 Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. Finally, please note that there is IPR filed against a previous version of this draft (-03). Please follow the procedures outlined in RFC 3979 and consult your own legal counsel in your decision-making process. -shane From Florin.Balus@alcatel-lucent.com Sun Mar 29 21:07:58 2009 Return-Path: <Florin.Balus@alcatel-lucent.com> 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 9D44D3A6D02 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:07:58 -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 t4-OfoGRg13p for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:07:57 -0700 (PDT) Received: from audl952.usa.alcatel.com (audl952.usa.alcatel.com [143.209.238.159]) by core3.amsl.com (Postfix) with ESMTP id C61A23A6D01 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 21:07:57 -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 n2U48oWm016806; Sun, 29 Mar 2009 22:08:50 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Sun, 29 Mar 2009 23:08:49 -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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Sun, 29 Mar 2009 23:08:39 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B054326D7@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jceyU3U0x8ORkqF9wXRghmfRQACtkuw References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 04:08:49.0910 (UTC) FILETIME=[3AECB960:01C9B0ED] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 04:07:58 -0000 Support. > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:50 PM > To: l2vpn@ietf.org > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft:http://tools.ietf.org/html/draft- > sajassi-l2vpn-vpls-pbb-interop-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > Finally, please note that there is IPR filed against a previous > version of this draft (-03). Please follow the procedures outlined in > RFC 3979 and consult your own legal counsel in your decision-making > process. >=20 > -shane From Florin.Balus@alcatel-lucent.com Sun Mar 29 21:08:11 2009 Return-Path: <Florin.Balus@alcatel-lucent.com> 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 C33463A6BF8 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:08:11 -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 oOQ7zKCa51aB for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:08:11 -0700 (PDT) Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com [143.209.238.162]) by core3.amsl.com (Postfix) with ESMTP id D5E893A69F7 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 21:08:10 -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 n2U493nA015361; Sun, 29 Mar 2009 22:09:03 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 29 Mar 2009 23:09:03 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Sun, 29 Mar 2009 23:08:52 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B054326D8@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4ULcWYPy+gEqQEarN+2CK132wQAC/SAA References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 04:09:03.0221 (UTC) FILETIME=[42DBD250:01C9B0ED] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 04:08:11 -0000 Support. > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > -shane From Florin.Balus@alcatel-lucent.com Sun Mar 29 21:28:19 2009 Return-Path: <Florin.Balus@alcatel-lucent.com> 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 24C343A6A95 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:28:19 -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 aI5qn0O0TYBh for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:28:18 -0700 (PDT) Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id 5A7413A6833 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 21:28:17 -0700 (PDT) Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id n2U4T9kc027306; Sun, 29 Mar 2009 22:29:09 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 29 Mar 2009 23:29:09 -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: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Date: Sun, 29 Mar 2009 23:28:58 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B054326DA@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4QEPWHKU85YzQsaA0Y79EV5BoQADwVTA References: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 04:29:09.0565 (UTC) FILETIME=[11E54ED0:01C9B0F0] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 04:28:19 -0000 Support. > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:40 PM > To: l2vpn@ietf.org > Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to > the list if you do or don't support making this draft a WG document. > The following is a URL for this draft: > http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > -shane From wim.henderickx@alcatel-lucent.be Sun Mar 29 21:52:23 2009 Return-Path: <wim.henderickx@alcatel-lucent.be> 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 234753A6C46 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:52:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 4e7v76wq8ntq for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:52:21 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 0A7853A6A4C for <l2vpn@ietf.org>; Sun, 29 Mar 2009 21:52:20 -0700 (PDT) Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U4qv71008104; Mon, 30 Mar 2009 06:52:57 +0200 Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 06:52:57 +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: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Date: Mon, 30 Mar 2009 06:52:56 +0200 Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D7049D8DA6@FRVELSMBS22.ad2.ad.alcatel.com> In-Reply-To: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4N5KZGqK1bk5RkWLY+i8vn5FWgAEoL2g References: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 04:52:57.0995 (UTC) FILETIME=[654E6DB0:01C9B0F3] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 04:52:23 -0000 support -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: maandag 30 maart 2009 4:40 To: l2vpn@ietf.org Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to =20 the list if you do or don't support making this draft a WG document. =20 The following is a URL for this draft: http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. -shane From wim.henderickx@alcatel-lucent.be Sun Mar 29 21:52:30 2009 Return-Path: <wim.henderickx@alcatel-lucent.be> 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 9E1E13A6CFF for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:52:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 j3kUoAeGVeuu for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:52:29 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 04EA33A6CFC for <l2vpn@ietf.org>; Sun, 29 Mar 2009 21:52:28 -0700 (PDT) Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U4r5hI008180; Mon, 30 Mar 2009 06:53:05 +0200 Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 06:53:05 +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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Mon, 30 Mar 2009 06:53:05 +0200 Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D7049D8DA7@FRVELSMBS22.ad2.ad.alcatel.com> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UUKGG+WseYmRg6sjyes5+vvegAEiF4A References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 04:53:05.0989 (UTC) FILETIME=[6A123750:01C9B0F3] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 04:52:31 -0000 support -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: maandag 30 maart 2009 4:43 To: l2vpn@ietf.org Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. -shane From wim.henderickx@alcatel-lucent.be Sun Mar 29 21:52:40 2009 Return-Path: <wim.henderickx@alcatel-lucent.be> 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 DE4633A6A4C for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:52:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 MmaFAqPdSNri for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 21:52:38 -0700 (PDT) Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5]) by core3.amsl.com (Postfix) with ESMTP id BA0483A6CFF for <l2vpn@ietf.org>; Sun, 29 Mar 2009 21:52:37 -0700 (PDT) Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U4rErF011965; Mon, 30 Mar 2009 06:53:14 +0200 Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 06:53:14 +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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 06:53:13 +0200 Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D7049D8DA8@FRVELSMBS22.ad2.ad.alcatel.com> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jmLZT39eid1RFGkVuYAWLvPPwAETIfQ References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 04:53:14.0402 (UTC) FILETIME=[6F15F020:01C9B0F3] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 04:52:40 -0000 support -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: maandag 30 maart 2009 4:50 To: l2vpn@ietf.org Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. Finally, please note that there is IPR filed against a previous =20 version of this draft (-03). Please follow the procedures outlined in =20 RFC 3979 and consult your own legal counsel in your decision-making =20 process. -shane From nurit.sprecher@nsn.com Sun Mar 29 22:20:47 2009 Return-Path: <nurit.sprecher@nsn.com> 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 D68403A6856 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:20:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.224 X-Spam-Level: X-Spam-Status: No, score=-5.224 tagged_above=-999 required=5 tests=[AWL=1.375, 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 PpilSCsyIyX8 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:20:47 -0700 (PDT) Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id BF4263A6807 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 22:20:46 -0700 (PDT) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n2U5La6n009857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 30 Mar 2009 07:21:36 +0200 Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n2U5LZNn030681; Mon, 30 Mar 2009 07:21:36 +0200 Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 07:21: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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 07:21:29 +0200 Message-ID: <077E41CFFD002C4CAB7DFA4386A53264798D90@DEMUEXC014.nsn-intra.net> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jlf7x1l22CjRA29h2XMSd4YhwAFJprA References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> To: "ext Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 05:21:35.0808 (UTC) FILETIME=[6533E400:01C9B0F7] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 05:20:47 -0000 Hi, I'll go over the draft again. In the meantime I'll appreciate if the authors can clarify and help me resolve my confusion about this draft.=20 Apparently I thought the intention of the draft is to enhance scalability, and to avoid the learning of all customers' MAC addresses. In the last meeting there was a comment indicating that all I-SIDs are handled in the E-NNI and that scalability is not really solved in this case. It looks as the intention is to make more efficient replication at the E-NNI.=20 Would the authors be so kind and clarify this to me. Best regards, Nurit -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of ext Shane Amante Sent: Monday, March 30, 2009 04:50 To: l2vpn@ietf.org Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. Finally, please note that there is IPR filed against a previous =20 version of this draft (-03). Please follow the procedures outlined in =20 RFC 3979 and consult your own legal counsel in your decision-making =20 process. -shane From pdutta@alcatel-lucent.com Sun Mar 29 22:53:42 2009 Return-Path: <pdutta@alcatel-lucent.com> 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 86A5D3A693B for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:53:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 eU4skKctqK6W for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:53:41 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 88D133A6B18 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 22:53:40 -0700 (PDT) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U5sGNj000545 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 07:54:17 +0200 Received: from INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 30 Mar 2009 07:54:17 +0200 Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Mon, 30 Mar 2009 11:23:32 +0530 From: "Dutta, Pranjal K (Pranjal)" <pdutta@alcatel-lucent.com> To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 11:23:29 +0530 Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4US4MPksorHfTP+CV9nGUzRyBwAGmWmA Message-ID: <C584046466ED224CA92C1BC3313B963E0358E73A28@INBANSXCHMBSA3.in.alcatel-lucent.com> References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 05:53:42 -0000 Support. Thanks, Pranjal -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hane Amante Sent: Sunday, March 29, 2009 7:43 PM To: l2vpn@ietf.org Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. -shane From pdutta@alcatel-lucent.com Sun Mar 29 22:55:06 2009 Return-Path: <pdutta@alcatel-lucent.com> 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 612D03A67E6 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:55:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 W9Oe0+PmILRW for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:55:05 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 466863A693B for <l2vpn@ietf.org>; Sun, 29 Mar 2009 22:55:05 -0700 (PDT) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U5tfPu001063 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 07:55:41 +0200 Received: from INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 30 Mar 2009 07:55:41 +0200 Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Mon, 30 Mar 2009 11:24:45 +0530 From: "Dutta, Pranjal K (Pranjal)" <pdutta@alcatel-lucent.com> To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 11:24:43 +0530 Subject: RE: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4N0EvYICmjgrSHqNIrkdSbzmLAAGxTwg Message-ID: <C584046466ED224CA92C1BC3313B963E0358E73A2C@INBANSXCHMBSA3.in.alcatel-lucent.com> References: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> In-Reply-To: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 05:55:06 -0000 Support. Thanks, Pranjal -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hane Amante Sent: Sunday, March 29, 2009 7:40 PM To: l2vpn@ietf.org Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to =20 the list if you do or don't support making this draft a WG document. =20 The following is a URL for this draft: http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. -shane From pdutta@alcatel-lucent.com Sun Mar 29 22:55:54 2009 Return-Path: <pdutta@alcatel-lucent.com> 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 5C3D13A6CC5 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:55:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 6hdN2KRu3t8Z for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 22:55:53 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 52CD73A6CB4 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 22:55:53 -0700 (PDT) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U5uTQm025701 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 07:56:29 +0200 Received: from INBANSXCHHUB01.in.alcatel-lucent.com (135.250.12.32) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (135.120.45.64) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 30 Mar 2009 07:56:29 +0200 Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Mon, 30 Mar 2009 11:24:02 +0530 From: "Dutta, Pranjal K (Pranjal)" <pdutta@alcatel-lucent.com> To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 11:24:00 +0530 Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4joM2s+5AwdGQHOkomgEHJr4mAAGau+Q Message-ID: <C584046466ED224CA92C1BC3313B963E0358E73A2A@INBANSXCHMBSA3.in.alcatel-lucent.com> References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 05:55:54 -0000 Support. Thanks, Pranjal -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hane Amante Sent: Sunday, March 29, 2009 7:50 PM To: l2vpn@ietf.org Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft:http://tools.ietf.org/html/draft-sajassi-= l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. Finally, please note that there is IPR filed against a previous =20 version of this draft (-03). Please follow the procedures outlined in =20 RFC 3979 and consult your own legal counsel in your decision-making =20 process. -shane From pdutta@alcatel-lucent.com Sun Mar 29 23:11:19 2009 Return-Path: <pdutta@alcatel-lucent.com> 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 452953A6C95 for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 23:11:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 lkePIV7oVDjJ for <l2vpn@core3.amsl.com>; Sun, 29 Mar 2009 23:11:18 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 332453A67E6 for <l2vpn@ietf.org>; Sun, 29 Mar 2009 23:11:17 -0700 (PDT) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U6Bsx5007970 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 08:11:54 +0200 Received: from INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (135.120.45.61) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 30 Mar 2009 08:11:54 +0200 Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Mon, 30 Mar 2009 11:41:03 +0530 From: "Dutta, Pranjal K (Pranjal)" <pdutta@alcatel-lucent.com> To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 11:41:01 +0530 Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4joM2s+5AwdGQHOkomgEHJr4mAAHAm5w Message-ID: <C584046466ED224CA92C1BC3313B963E0358E73A4B@INBANSXCHMBSA3.in.alcatel-lucent.com> References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 06:11:19 -0000 Support. Thanks, Pranjal -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hane Amante Sent: Sunday, March 29, 2009 7:50 PM To: l2vpn@ietf.org Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft:http://tools.ietf.org/html/draft-sajassi-= l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. Finally, please note that there is IPR filed against a previous =20 version of this draft (-03). Please follow the procedures outlined in =20 RFC 3979 and consult your own legal counsel in your decision-making =20 process. -shane From llevrau@alcatel-lucent.com Mon Mar 30 00:42:57 2009 Return-Path: <llevrau@alcatel-lucent.com> 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 F2A8D3A6923 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 00:42:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.099 X-Spam-Level: X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 J7gTVqCGqqQl for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 00:42:56 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id E84EF3A67D2 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 00:42:55 -0700 (PDT) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U7hTWq003015 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 09:43:29 +0200 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Mon, 30 Mar 2009 09:43:29 +0200 From: "LEVRAU, LIEVEN (LIEVEN)" <llevrau@alcatel-lucent.com> To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 09:43:26 +0200 Subject: RE: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4QEPWHKU85YzQsaA0Y79EV5BoQADwVTAAAbJrWA= Message-ID: <4D3F2B2A3FE4B54DBF449418B192A1FE75E74034@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> References: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> <4A5028372622294A99B8FFF6BD06EB7B054326DA@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B054326DA@USDALSMBS03.ad3.ad.alcatel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 07:42:57 -0000 Support. ./ Lieven > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:40 PM > To: l2vpn@ietf.org > Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to > the list if you do or don't support making this draft a WG document. > The following is a URL for this draft: > http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > -shane From llevrau@alcatel-lucent.com Mon Mar 30 00:43:18 2009 Return-Path: <llevrau@alcatel-lucent.com> 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 6244A3A6C3D for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 00:43:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.149 X-Spam-Level: X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 dNB9MKGIK-uY for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 00:43:17 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 4A32D3A67D2 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 00:43:17 -0700 (PDT) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U7hsQT030991 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 09:43:54 +0200 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 30 Mar 2009 09:43:54 +0200 From: "LEVRAU, LIEVEN (LIEVEN)" <llevrau@alcatel-lucent.com> To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 09:43:50 +0200 Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4ULcWYPy+gEqQEarN+2CK132wQAC/SAAAAeAZqA= Message-ID: <4D3F2B2A3FE4B54DBF449418B192A1FE75E74035@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> <4A5028372622294A99B8FFF6BD06EB7B054326D8@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B054326D8@USDALSMBS03.ad3.ad.alcatel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 07:43:18 -0000 Support. ./ Lieven > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > -shane From llevrau@alcatel-lucent.com Mon Mar 30 00:43:51 2009 Return-Path: <llevrau@alcatel-lucent.com> 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 6E84F3A6D06 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 00:43:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.174 X-Spam-Level: X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 psKpWlO0pE11 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 00:43:50 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 5E4183A6C3D for <l2vpn@ietf.org>; Mon, 30 Mar 2009 00:43:50 -0700 (PDT) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2U7iMHf003809 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Mar 2009 09:44:26 +0200 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Mon, 30 Mar 2009 09:44:25 +0200 From: "LEVRAU, LIEVEN (LIEVEN)" <llevrau@alcatel-lucent.com> To: "Balus, Florin Stelian (Florin)" <florin.balus@alcatel-lucent.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Mon, 30 Mar 2009 09:44:22 +0200 Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jceyU3U0x8ORkqF9wXRghmfRQACtkuwAAeOJRA= Message-ID: <4D3F2B2A3FE4B54DBF449418B192A1FE75E74036@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> <4A5028372622294A99B8FFF6BD06EB7B054326D7@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B054326D7@USDALSMBS03.ad3.ad.alcatel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 07:43:51 -0000 Support. ./ Lieven > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:50 PM > To: l2vpn@ietf.org > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft:http://tools.ietf.org/html/draft- > sajassi-l2vpn-vpls-pbb-interop-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > Finally, please note that there is IPR filed against a previous > version of this draft (-03). Please follow the procedures outlined in > RFC 3979 and consult your own legal counsel in your decision-making > process. >=20 > -shane From geraldine.calvignac@orange-ftgroup.com Mon Mar 30 01:14:53 2009 Return-Path: <geraldine.calvignac@orange-ftgroup.com> 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 957BF3A6A2C for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 01:14:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[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 HIxsAi1++L0Q for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 01:14:53 -0700 (PDT) Received: from R-MAIL2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 73E8C3A67D2 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 01:14:51 -0700 (PDT) Received: from ftrdmel3.rd.francetelecom.fr ([10.192.128.42]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 10:15:48 +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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 10:15:29 +0200 Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE085F4FFD@ftrdmel3> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4lthaLi5lp9QSx2c0ttLq3HC/gALNBMg References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: <geraldine.calvignac@orange-ftgroup.com> To: <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 08:15:48.0467 (UTC) FILETIME=[BB791430:01C9B10F] X-Mailman-Approved-At: Mon, 30 Mar 2009 07:03:18 -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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 08:14:53 -0000 Support.=20 -----Message d'origine----- De : l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] De la part = de Shane Amante Envoy=E9 : lundi 30 mars 2009 04:50 =C0 : l2vpn@ietf.org Objet : draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request = by the authors to make this a WG draft. Please indicate to the list if = you do or don't support making this draft a WG document. The following = is a URL for this = draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence = will not be counted as acceptance. Finally, please note that there is IPR filed against a previous version = of this draft (-03). Please follow the procedures outlined in RFC 3979 = and consult your own legal counsel in your decision-making process. -shane From geraldine.calvignac@orange-ftgroup.com Mon Mar 30 01:14:53 2009 Return-Path: <geraldine.calvignac@orange-ftgroup.com> 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 B67963A67D2 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 01:14:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[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 x-anGcWfPDBK for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 01:14:53 -0700 (PDT) Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 73F1C3A699A for <l2vpn@ietf.org>; Mon, 30 Mar 2009 01:14:51 -0700 (PDT) Received: from ftrdmel3.rd.francetelecom.fr ([10.192.128.42]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 10:15:48 +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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Mon, 30 Mar 2009 10:15:25 +0200 Message-ID: <2AF8FF7D89242541B12E7A47F6ECB4BE085F4FFC@ftrdmel3> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4VYxQLtwwD75TTOxx4vM6p4IfwALfGfQ References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: <geraldine.calvignac@orange-ftgroup.com> To: <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 08:15:48.0905 (UTC) FILETIME=[BBBBE990:01C9B10F] X-Mailman-Approved-At: Mon, 30 Mar 2009 07:03:18 -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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 08:14:53 -0000 Support.=20 -----Message d'origine----- De : l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] De la part = de Shane Amante Envoy=E9 : lundi 30 mars 2009 04:43 =C0 : l2vpn@ietf.org Objet : draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request = by the authors to make this a WG draft. Please indicate to the list if = you do or don't support making this draft a WG document. The following = is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence = will not be counted as acceptance. -shane From Mustapha.Aissaoui@alcatel-lucent.com Mon Mar 30 10:28:34 2009 Return-Path: <Mustapha.Aissaoui@alcatel-lucent.com> 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 8A92F3A6C7E for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:28:34 -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 LMgf+lwnJmjW for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:28:33 -0700 (PDT) Received: from audl951.usa.alcatel.com (audl951.usa.alcatel.com [143.209.238.161]) by core3.amsl.com (Postfix) with ESMTP id A6D0E3A6B42 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 10:28:33 -0700 (PDT) Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl951.usa.alcatel.com (ALCANET) with ESMTP id n2UHTQI2026234; Mon, 30 Mar 2009 11:29:26 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 12:29:26 -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: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Date: Mon, 30 Mar 2009 12:29:24 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B05432805@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4QEPWHKU85YzQsaA0Y79EV5BoQAfA2Og References: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 17:29:26.0063 (UTC) FILETIME=[12B3FBF0:01C9B15D] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 17:28:34 -0000 Support. Mustapha.=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Shane Amante > Sent: Sunday, March 29, 2009 10:40 PM > To: l2vpn@ietf.org > Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there=20 > was a request by the authors to make this a WG draft. Please=20 > indicate to =20 > the list if you do or don't support making this draft a WG=20 > document. =20 > The following is a URL for this draft: > http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. =20 > Silence will not be counted as acceptance. >=20 > -shane >=20 From Mustapha.Aissaoui@alcatel-lucent.com Mon Mar 30 10:31:57 2009 Return-Path: <Mustapha.Aissaoui@alcatel-lucent.com> 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 676663A6B03 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:31:57 -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 QDbbXS0r6Ozr for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:31:56 -0700 (PDT) Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id A9FD23A6C7E for <l2vpn@ietf.org>; Mon, 30 Mar 2009 10:31:56 -0700 (PDT) Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id n2UHWoer025667; Mon, 30 Mar 2009 11:32:50 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 12:32: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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Mon, 30 Mar 2009 12:32:40 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B05432808@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4ULcWYPy+gEqQEarN+2CK132wQAfEA6g References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 17:32:41.0298 (UTC) FILETIME=[87127B20:01C9B15D] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 17:31:57 -0000 Support. Mustapha.=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Shane Amante > Sent: Sunday, March 29, 2009 10:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there=20 > was a request by the authors to make this a WG draft. Please=20 > indicate to the list if you do or don't support making this=20 > draft a WG document. The following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. =20 > Silence will not be counted as acceptance. >=20 > -shane >=20 From Rohit.Mediratta@alcatel-lucent.com Mon Mar 30 10:36:36 2009 Return-Path: <Rohit.Mediratta@alcatel-lucent.com> 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 76BE93A6C7E for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:36:36 -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.001, 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 aUNsTSJ1veMV for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:36:35 -0700 (PDT) Received: from audl951.usa.alcatel.com (audl951.usa.alcatel.com [143.209.238.161]) by core3.amsl.com (Postfix) with ESMTP id 91A973A6A71 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 10:36:35 -0700 (PDT) Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl951.usa.alcatel.com (ALCANET) with ESMTP id n2UHbOPv028212 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 11:37:33 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 30 Mar 2009 12:37:27 -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: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Date: Mon, 30 Mar 2009 12:37:26 -0500 Message-ID: <67FBA6A55FF15B46B8B572062529D26A0367A390@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4Nn2v6ZCXvHWTReY5gdFSdEoSgAfVNYA From: "MEDIRATTA Rohit" <Rohit.Mediratta@alcatel-lucent.com> To: <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 17:37:27.0589 (UTC) FILETIME=[31B70550:01C9B15E] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 17:36:36 -0000 Support. -Rohit =20 -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: Sunday, March 29, 2009 6:40 PM To: l2vpn@ietf.org Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to =20 the list if you do or don't support making this draft a WG document. =20 The following is a URL for this draft: http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From Rohit.Mediratta@alcatel-lucent.com Mon Mar 30 10:37:01 2009 Return-Path: <Rohit.Mediratta@alcatel-lucent.com> 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 9ACE23A6D1A for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:37:01 -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 HD1RpebFvZPl for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:37:00 -0700 (PDT) Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com [143.209.238.162]) by core3.amsl.com (Postfix) with ESMTP id 16B453A6D48 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 10:36: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 n2UHbsi5013763 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 11:37:56 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 30 Mar 2009 12:37:51 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Mon, 30 Mar 2009 12:37:50 -0500 Message-ID: <67FBA6A55FF15B46B8B572062529D26A0367A391@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UHajpPUut3JSIWOB0+5vxfpSgAfPcnw From: "MEDIRATTA Rohit" <Rohit.Mediratta@alcatel-lucent.com> To: <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 17:37:51.0610 (UTC) FILETIME=[400855A0:01C9B15E] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 17:37:01 -0000 Support, -Rohit -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: Sunday, March 29, 2009 6:43 PM To: l2vpn@ietf.org Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From Mustapha.Aissaoui@alcatel-lucent.com Mon Mar 30 10:39:18 2009 Return-Path: <Mustapha.Aissaoui@alcatel-lucent.com> 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 C81AD28C10A for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:39:18 -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 HqCwXMq80Owq for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 10:39:18 -0700 (PDT) Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id F278628C107 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 10:39:17 -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 n2UHdtUm026370; Mon, 30 Mar 2009 11:40:11 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 30 Mar 2009 12:39:55 -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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 12:39:55 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B0543280E@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jceyU3U0x8ORkqF9wXRghmfRQAfE5Yg References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 17:39:55.0980 (UTC) FILETIME=[8A29B0C0:01C9B15E] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 17:39:18 -0000 Support. Mustapha.=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Shane Amante > Sent: Sunday, March 29, 2009 10:50 PM > To: l2vpn@ietf.org > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there=20 > was a request by the authors to make this a WG draft. Please=20 > indicate to the list if you do or don't support making this=20 > draft a WG document. The following is a URL for this=20 > draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb- > interop-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. =20 > Silence will not be counted as acceptance. >=20 > Finally, please note that there is IPR filed against a=20 > previous version of this draft (-03). Please follow the=20 > procedures outlined in RFC 3979 and consult your own legal=20 > counsel in your decision-making process. >=20 > -shane >=20 From sajassi@cisco.com Mon Mar 30 12:12:30 2009 Return-Path: <sajassi@cisco.com> 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 180863A68BB for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:12:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.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 YeyOv0RAfYkc for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:12:22 -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 7E79428C0EF for <l2vpn@ietf.org>; Mon, 30 Mar 2009 12:12:22 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,447,1233532800"; d="scan'208";a="148498316" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 30 Mar 2009 19:13:21 +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 n2UJDKfC004648; Mon, 30 Mar 2009 12:13:20 -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 n2UJDKKt001986; Mon, 30 Mar 2009 19:13:20 GMT Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Mar 2009 12:13:20 -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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 12:13:19 -0700 Message-ID: <7F115A41909B2641A9550322C4DF9D568F8E0D@xmb-sjc-22d.amer.cisco.com> In-Reply-To: <077E41CFFD002C4CAB7DFA4386A53264798D90@DEMUEXC014.nsn-intra.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jlf7x1l22CjRA29h2XMSd4YhwAFJprAABt4cGA= References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> <077E41CFFD002C4CAB7DFA4386A53264798D90@DEMUEXC014.nsn-intra.net> From: "Ali Sajassi (sajassi)" <sajassi@cisco.com> To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "ext Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 19:13:20.0315 (UTC) FILETIME=[969B58B0:01C9B16B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2494; t=1238440400; x=1239304400; 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=20draft-sajassi-l2vpn-vpls-pbb-interop-04 =20WG=20draft? |Sender:=20; bh=LDV3wyPQya+vxtZ5KFdiaLxIpwYkgrL0vqlhtFKi238=; b=ixcvWCGqEraUnICsNicBQqEAMsAsZ35CTrTgk3eki+hxP9myZXumQdXN0n efZA36NacLjvBz5bkcHcY9euH0RpHdNx2hhh4qACIeMHGsm4dVZVs2En9P7F FB/R/qDDMj; 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 19:12:30 -0000 Hi Nurit,=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon) > Sent: Sunday, March 29, 2009 10:21 PM > To: ext Shane Amante; l2vpn@ietf.org > Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hi, > I'll go over the draft again. In the meantime I'll appreciate=20 > if the authors can clarify and help me resolve my confusion=20 > about this draft.=20 > Apparently I thought the intention of the draft is to enhance=20 > scalability, and to avoid the learning of all customers' MAC=20 > addresses. The purpose of PBB encap is two fold: a) for C-MAC scalability and b) for PW scalability =20 > In the last meeting there was a comment indicating that all=20 > I-SIDs are handled in the E-NNI and that scalability is not=20 > really solved in this case. It looks as the intention is to=20 > make more efficient replication at the E-NNI. It is not clear to me what scenario you are referring to but there is no C-MAC learning & forwarding at E-NNI between PBB network and VPLS core network. In case of loosely-coupled I-SID domains, no I-SID translation is required at E-NNI. And in case of independent I-SID domains, I-SID translation may be required at E-NNI. However, no C-MAC address lookup is required at E-NNI for both of these cases. Cheers, Ali =20 > Would the authors be so kind and clarify this to me. > Best regards, > Nurit >=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of ext Shane Amante > Sent: Monday, March 30, 2009 04:50 > To: l2vpn@ietf.org > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there=20 > was a request by the authors to make this a WG draft. Please=20 > indicate to the list if you do or don't support making this=20 > draft a WG document. The following is a URL for this > draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb- > interop-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. =20 > Silence will not be counted as acceptance. >=20 > Finally, please note that there is IPR filed against a=20 > previous version of this draft (-03). Please follow the=20 > procedures outlined in RFC 3979 and consult your own legal=20 > counsel in your decision-making process. >=20 > -shane >=20 From sajassi@cisco.com Mon Mar 30 12:12:30 2009 Return-Path: <sajassi@cisco.com> 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 8BAC33A6A36 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:12:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.266 X-Spam-Level: X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=1.333, 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 NEsoufjFKd3q for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:12:22 -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 B61A828C100 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 12:12:22 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,447,1233532800"; d="scan'208";a="148498317" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 30 Mar 2009 19:13:21 +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 n2UJDLTp023330; Mon, 30 Mar 2009 12:13:21 -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 n2UJDLB3002820; Mon, 30 Mar 2009 19:13:21 GMT Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Mar 2009 12:13:21 -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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 12:13:20 -0700 Message-ID: <7F115A41909B2641A9550322C4DF9D568F8E0F@xmb-sjc-22d.amer.cisco.com> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jeUbW31F61iS/e5sN9irKApBgAghcjA References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "Ali Sajassi (sajassi)" <sajassi@cisco.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 19:13:21.0105 (UTC) FILETIME=[9713E410:01C9B16B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1008; t=1238440401; x=1239304401; 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=20draft-sajassi-l2vpn-vpls-pbb-interop-04 =20WG=20draft? |Sender:=20; bh=b+2f5s+Ye6DIwjmZH6KMo+UnCZdUwBsWCfgyD2GXdEs=; b=PbeNNf2CUMWKvYlbt8yVTX2r2ne3nN696k86kTetgjsK/ovgYj9kPgwSCa KgDohIplsFnXagM0Tx/ijJVIdWcoPyaY3jE0Z3k/l2hid+6Ijssc1aI3m5UL 7CRdoUKMEU; Authentication-Results: sj-dkim-3; header.From=sajassi@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 19:12:30 -0000 Support=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Shane Amante > Sent: Sunday, March 29, 2009 7:50 PM > To: l2vpn@ietf.org > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there=20 > was a request by the authors to make this a WG draft. Please=20 > indicate to the list if you do or don't support making this=20 > draft a WG document. The following is a URL for this=20 > draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb- > interop-04 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. =20 > Silence will not be counted as acceptance. >=20 > Finally, please note that there is IPR filed against a=20 > previous version of this draft (-03). Please follow the=20 > procedures outlined in RFC 3979 and consult your own legal=20 > counsel in your decision-making process. >=20 > -shane >=20 From sajassi@cisco.com Mon Mar 30 12:14:31 2009 Return-Path: <sajassi@cisco.com> 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 758FD3A6AC9 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:14:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.599 X-Spam-Level: X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.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 O3a5kqFKW5im for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:14:30 -0700 (PDT) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id B020528C11F for <l2vpn@ietf.org>; Mon, 30 Mar 2009 12:14:30 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,447,1233532800"; d="scan'208";a="32666206" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 30 Mar 2009 19:13:21 +0000 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n2UJDLc5019249; Mon, 30 Mar 2009 12:13:21 -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 n2UJDKvD002817; Mon, 30 Mar 2009 19:13:20 GMT Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Mar 2009 12:13:20 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Mon, 30 Mar 2009 12:13:20 -0700 Message-ID: <7F115A41909B2641A9550322C4DF9D568F8E0E@xmb-sjc-22d.amer.cisco.com> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4ULrPvB+zCQ1Q16/q/JqE7khtAAgwBXA References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: "Ali Sajassi (sajassi)" <sajassi@cisco.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 19:13:20.0886 (UTC) FILETIME=[96F27960:01C9B16B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=759; t=1238440401; x=1239304401; c=relaxed/simple; s=sjdkim1004; 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=20draft-balus-sajassi-l2vpn-pbb-vpls-01=2 0WG=20draft? |Sender:=20; bh=b/pTkCy78xvsCBn31kbKCmA2jLLBLDf1yEtK4gtNYyg=; b=Cfs7zoh659dklG48WWJEpE8n88637wWoP0fgBe2ruUrDIQmo28yxXKEieX pFlVioNpl+L/5ay1qqYFwYJEN1ESGIREMXd0IMt4p8IudI2JLNMWSioZkFCq K/RYgGBnxmqBdBj8zHVB9eimgxN4U2tD7Iz2CHT2nF12sIW5SR9DQ=; Authentication-Results: sj-dkim-1; header.From=sajassi@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 19:14:31 -0000 Support=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Shane Amante > Sent: Sunday, March 29, 2009 7:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there=20 > was a request by the authors to make this a WG draft. Please=20 > indicate to the list if you do or don't support making this=20 > draft a WG document. The following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. =20 > Silence will not be counted as acceptance. >=20 > -shane >=20 From ssalam@cisco.com Mon Mar 30 12:27:41 2009 Return-Path: <ssalam@cisco.com> 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 2D1823A6C7E for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:27: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=[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 OqXa3N1l2SkZ for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:27:39 -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 9E1BD3A6C6F for <l2vpn@ietf.org>; Mon, 30 Mar 2009 12:27:39 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,448,1233532800"; d="scan'208";a="163894027" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 30 Mar 2009 19:28:38 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n2UJScfO022870; Mon, 30 Mar 2009 12:28:38 -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 n2UJSbFN005848; Mon, 30 Mar 2009 19:28:38 GMT Received: from xmb-sjc-233.amer.cisco.com ([128.107.191.88]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Mar 2009 12:28:37 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Mon, 30 Mar 2009 12:28:36 -0700 Message-ID: <A997DBD5DD3E0B46A6D0353CF3E32CCB072FA925@xmb-sjc-233.amer.cisco.com> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UPvX7SB9j5oRw2ngaDA2cMNNAAjGgsA References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: "Samer Salam (ssalam)" <ssalam@cisco.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 19:28:37.0928 (UTC) FILETIME=[B98BFA80:01C9B16D] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=737; t=1238441318; x=1239305318; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ssalam@cisco.com; z=From:=20=22Samer=20Salam=20(ssalam)=22=20<ssalam@cisco.com > |Subject:=20RE=3A=20draft-balus-sajassi-l2vpn-pbb-vpls-01=2 0WG=20draft? |Sender:=20; bh=VDxsacp3lc0koCAOp/io33Rue6WMUsDpvVAZ6OlfZ7M=; b=NJlR/nmBCNZD+EIjSWVvqxdFO+8TqQTeSxDCuygPCN5+Yt+Ljlkb3SYr70 EsI6OZjgYZm+R1WH3sQ7Bt2dXBTHO50KwQ8PmV2aw0tjTyYndaXBqB2Fg86x TvNt5XFqUoIuaiHfHK5yd/S/kboF/W5GsXaTl7xcK/E2gKTioDQhM=; Authentication-Results: sj-dkim-1; header.From=ssalam@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 19:27:41 -0000 Support.=20 >-----Original Message----- >From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 >On Behalf Of Shane Amante >Sent: Sunday, March 29, 2009 7:43 PM >To: l2vpn@ietf.org >Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > >Hi All, > >At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 >request by the authors to make this a WG draft. Please=20 >indicate to the =20 >list if you do or don't support making this draft a WG document. The =20 >following is a URL for this draft: >http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > >The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 >will not be counted as acceptance. > >-shane > From ssalam@cisco.com Mon Mar 30 12:28:12 2009 Return-Path: <ssalam@cisco.com> 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 9A9A53A6CB6 for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:28:12 -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 9CGFDCzjOy1x for <l2vpn@core3.amsl.com>; Mon, 30 Mar 2009 12:28:11 -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 35E3D28C100 for <l2vpn@ietf.org>; Mon, 30 Mar 2009 12:27:56 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,448,1233532800"; d="scan'208";a="148505354" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 30 Mar 2009 19:28:54 +0000 Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n2UJSsbE009153; Mon, 30 Mar 2009 12:28:54 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id n2UJSshG013743; Mon, 30 Mar 2009 19:28:54 GMT Received: from xmb-sjc-233.amer.cisco.com ([128.107.191.88]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Mar 2009 12:28:54 -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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Mon, 30 Mar 2009 12:28:52 -0700 Message-ID: <A997DBD5DD3E0B46A6D0353CF3E32CCB072FA926@xmb-sjc-233.amer.cisco.com> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jeMPLMqwFjoSn6vBWwpi10AHAAi4PIw References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "Samer Salam (ssalam)" <ssalam@cisco.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 30 Mar 2009 19:28:54.0593 (UTC) FILETIME=[C37ADB10:01C9B16D] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=986; t=1238441334; x=1239305334; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ssalam@cisco.com; z=From:=20=22Samer=20Salam=20(ssalam)=22=20<ssalam@cisco.com > |Subject:=20RE=3A=20draft-sajassi-l2vpn-vpls-pbb-interop-04 =20WG=20draft? |Sender:=20; bh=rtVpXfQTSCBrpM+8vUjb1v7c/jeWZP5rz54xSRJ9I4k=; b=OpSa/89M2cFyn9qgu9nqOLU7WJLdBbzo2ANfEfx6Gz8iq+Nn3QtAAeIF2i j8AbaTBpJFTPlEDQwjp3ZZnJAx/LnAsDgkggaASBuXU1ApxYmG5ORdhITD1D SMwCuCLhnA; Authentication-Results: sj-dkim-2; header.From=ssalam@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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Mon, 30 Mar 2009 19:28:12 -0000 Support.=20 >-----Original Message----- >From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 >On Behalf Of Shane Amante >Sent: Sunday, March 29, 2009 7:50 PM >To: l2vpn@ietf.org >Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > >Hi All, > >At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 >request by the authors to make this a WG draft. Please=20 >indicate to the =20 >list if you do or don't support making this draft a WG document. The =20 >following is a URL for this=20 >draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-i >nterop-04 > >The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 >will not be counted as acceptance. > >Finally, please note that there is IPR filed against a previous =20 >version of this draft (-03). Please follow the procedures=20 >outlined in =20 >RFC 3979 and consult your own legal counsel in your decision-making =20 >process. > >-shane > From frederic.jounay@orange-ftgroup.com Tue Mar 31 00:16:59 2009 Return-Path: <frederic.jounay@orange-ftgroup.com> 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 308753A68DB for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 00:16:59 -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=[AWL=0.000, 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 yQogf9buQStP for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 00:16:58 -0700 (PDT) Received: from R-MAIL2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 036B63A67B7 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 00:16:57 -0700 (PDT) Received: from FTRDMEL2.rd.francetelecom.fr ([10.192.128.41]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 09:17:46 +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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Tue, 31 Mar 2009 09:17:44 +0200 Message-ID: <8AA97249241F7148BE6D3D8B93D83F5A1556A848@ftrdmel2> In-Reply-To: <A997DBD5DD3E0B46A6D0353CF3E32CCB072FA926@xmb-sjc-233.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jeMPLMqwFjoSn6vBWwpi10AHAAi4PIwABiwrOA= References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> <A997DBD5DD3E0B46A6D0353CF3E32CCB072FA926@xmb-sjc-233.amer.cisco.com> From: <frederic.jounay@orange-ftgroup.com> To: <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 07:17:46.0464 (UTC) FILETIME=[CA735600:01C9B1D0] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 07:16:59 -0000 Support >-----Original Message----- >From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf=20 >Of Shane Amante >Sent: Sunday, March 29, 2009 7:50 PM >To: l2vpn@ietf.org >Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > >Hi All, > >At the L2VPN WG meeting at IETF 74 in San Francisco, there was a=20 >request by the authors to make this a WG draft. Please indicate to the=20 >list if you do or don't support making this draft a WG document. The=20 >following is a URL for this=20 >draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-i >nterop-04 > >The deadline for comments will be 3 weeks: Friday, April 17. Silence=20 >will not be counted as acceptance. > >Finally, please note that there is IPR filed against a previous version >of this draft (-03). Please follow the procedures outlined in RFC 3979 >and consult your own legal counsel in your decision-making process. > >-shane > From ostokes@extremenetworks.com Tue Mar 31 05:52:15 2009 Return-Path: <ostokes@extremenetworks.com> 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 9F48B3A6D42 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 05:52:15 -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 zQXgs4JoiNca for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 05:52:15 -0700 (PDT) Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p1.extremenetworks.com [207.179.9.62]) by core3.amsl.com (Postfix) with ESMTP id EA1FB3A68BE for <l2vpn@ietf.org>; Tue, 31 Mar 2009 05:52:14 -0700 (PDT) Received: from USEXCHANGE.corp.extremenetworks.com ([10.0.4.74]) by ussc-casht-p2.corp.extremenetworks.com ([10.255.181.88]) with mapi; Tue, 31 Mar 2009 05:53:13 -0700 From: Olen Stokes <ostokes@extremenetworks.com> To: 'Shane Amante' <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Tue, 31 Mar 2009 05:53:13 -0700 Subject: RE: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Topic: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Thread-Index: Acmw4NqinxiGtXbyQQuB6okEmu1ERABHrN1w Message-ID: <6738A78F51650A4FAEDCF6844B26C21413461536F2@USEXCHANGE.corp.extremenetworks.com> References: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> In-Reply-To: <4E65056A-207D-4350-A5AC-25F0D8D389AC@castlepoint.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 12:52:15 -0000 Support. Cheers, Olen -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hane Amante Sent: Sunday, March 29, 2009 10:40 PM To: l2vpn@ietf.org Subject: draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft: http://tools.ietf.org/html/draft-pdutta-l2vpn-vpls-ldp-mac-opt-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From ostokes@extremenetworks.com Tue Mar 31 05:53:15 2009 Return-Path: <ostokes@extremenetworks.com> 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 1385F28C118 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 05:53:15 -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 UvE8FBXsRMcl for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 05:53:14 -0700 (PDT) Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p2.extremenetworks.com [207.179.9.62]) by core3.amsl.com (Postfix) with ESMTP id 9E0A928C124 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 05:52:55 -0700 (PDT) Received: from USEXCHANGE.corp.extremenetworks.com ([10.0.4.74]) by ussc-casht-p2.corp.extremenetworks.com ([10.255.181.88]) with mapi; Tue, 31 Mar 2009 05:53:54 -0700 From: Olen Stokes <ostokes@extremenetworks.com> To: 'Shane Amante' <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Tue, 31 Mar 2009 05:53:54 -0700 Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKA Message-ID: <6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com> References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 12:53:15 -0000 Support. Cheers, Olen -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S= hane Amante Sent: Sunday, March 29, 2009 10:43 PM To: l2vpn@ietf.org Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From davarish@yahoo.com Tue Mar 31 06:34:59 2009 Return-Path: <davarish@yahoo.com> 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 ECBEA3A683A for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 06:34:59 -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 poGqgjhdlujE for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 06:34:59 -0700 (PDT) Received: from smtp101.rog.mail.re2.yahoo.com (smtp101.rog.mail.re2.yahoo.com [206.190.36.79]) by core3.amsl.com (Postfix) with SMTP id EDA1828C0EF for <l2vpn@ietf.org>; Tue, 31 Mar 2009 06:34:58 -0700 (PDT) Received: (qmail 87550 invoked from network); 31 Mar 2009 13:35:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:thread-index:Content-Language; b=T6MkkqneSAFn2hkNO1ov4rGHG26pbEbdBMx+pO/VAEAfvX2FmXKfqgGTOMUb8LJy0f5qXIA9iu52kO8OuFgnr72iQNBM2imBrziQw4Hz8QudDJRaGdKvFcb8tWfIeZlQFWewMZaQ3Lk+tQisKHpIsNACVtKO+LpM2jB9MfNV2zg= ; Received: from unknown (HELO ShahramPC) (davarish@99.238.119.231 with login) by smtp101.rog.mail.re2.yahoo.com with SMTP; 31 Mar 2009 13:35:57 -0000 X-YMail-OSG: sTeWFTkVM1lErqM3_pf3Nolfg9NBqbLICReOAUcTP_Ek5SUAceG2d271nhHuhfx_pg-- X-Yahoo-Newman-Property: ymail-3 From: "Shahram Davari" <davarish@yahoo.com> To: "'Shane Amante'" <shane@castlepoint.net>, <l2vpn@ietf.org> References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> <6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com> In-Reply-To: <6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com> Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 09:35:56 -0400 Message-ID: <042001c9b205$9fa23c40$dee6b4c0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 thread-index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCA= Content-Language: en-ca X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: davarish@yahoo.com List-Id: <l2vpn.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 13:35:00 -0000 Hi, I also support. However, text needs to be added to the Introduction to make it clear that similar to H-VPLS, the PBB over VPLS method (this draft) is another method to overcome the scalability issue of VPLS that exist due to the large number of required PWs. The PBB over VPLS reduces the number of required PWs and therefore improves VPLS scalability.. Best regards, Shahram -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: Sunday, March 29, 2009 10:43 PM To: l2vpn@ietf.org Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request by the authors to make this a WG draft. Please indicate to the list if you do or don't support making this draft a WG document. The following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence will not be counted as acceptance. -shane From Manuel.Paul@telekom.de Tue Mar 31 07:02:19 2009 Return-Path: <Manuel.Paul@telekom.de> 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 B90693A680D for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:02:19 -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_DE=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 Enf4FmZwSMZX for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:02:19 -0700 (PDT) Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id AE1943A6800 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 07:02:18 -0700 (PDT) Received: from s4de9jsaano.mgb.telekom.de (HELO S4DE9JSAANO.ost.t-com.de) ([10.125.177.105]) by tcmail81.telekom.de with ESMTP; 31 Mar 2009 16:03:15 +0200 Received: from S4DE9JSAANI.ost.t-com.de ([10.125.177.223]) by S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 16:03:14 +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: AW: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 16:02:56 +0200 Message-ID: <40FB0FFB97588246A1BEFB05759DC8A002CD834C@S4DE9JSAANI.ost.t-com.de> In-Reply-To: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? thread-index: Acmw4UYtVH0G8NM5TKGfHlxusNFo7QBD7Dhg References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> From: <Manuel.Paul@telekom.de> To: <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 14:03:14.0000 (UTC) FILETIME=[6ECABD00:01C9B209] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 14:02:19 -0000 Support.=20 Best Regards Manuel -----Urspr=FCngliche Nachricht----- Von: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] Im Auftrag = von Shane Amante Gesendet: Montag, 30. M=E4rz 2009 04:43 An: l2vpn@ietf.org Betreff: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. -shane From frederic.jounay@orange-ftgroup.com Tue Mar 31 07:31:02 2009 Return-Path: <frederic.jounay@orange-ftgroup.com> 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 88C583A6855 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:31:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.000, 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 Q+nBXjYnr5ln for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:31:01 -0700 (PDT) Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 4A5173A680D for <l2vpn@ietf.org>; Tue, 31 Mar 2009 07:31:01 -0700 (PDT) Received: from FTRDMEL2.rd.francetelecom.fr ([10.192.128.41]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 16:31:57 +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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 16:31:59 +0200 Message-ID: <8AA97249241F7148BE6D3D8B93D83F5A1556AD5F@ftrdmel2> In-Reply-To: <40FB0FFB97588246A1BEFB05759DC8A002CD834C@S4DE9JSAANI.ost.t-com.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UYtVH0G8NM5TKGfHlxusNFo7QBD7DhgAAcbwUA= References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> <40FB0FFB97588246A1BEFB05759DC8A002CD834C@S4DE9JSAANI.ost.t-com.de> From: <frederic.jounay@orange-ftgroup.com> To: <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 14:31:57.0674 (UTC) FILETIME=[722E84A0:01C9B20D] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 14:31:02 -0000 Support. -----Urspr=FCngliche Nachricht----- Von: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] Im Auftrag = von Shane Amante Gesendet: Montag, 30. M=E4rz 2009 04:43 An: l2vpn@ietf.org Betreff: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request = by the authors to make this a WG draft. Please indicate to the list if = you do or don't support making this draft a WG document. The following = is a URL for this draft: http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 The deadline for comments will be 3 weeks: Friday, April 17. Silence = will not be counted as acceptance. -shane From agmalis@gmail.com Tue Mar 31 07:43:45 2009 Return-Path: <agmalis@gmail.com> 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 ED47F3A69DA for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:43:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.266 X-Spam-Level: X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5 tests=[AWL=-0.667, 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 CcnVZOLyKtwC for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:43:45 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by core3.amsl.com (Postfix) with ESMTP id 28C223A67E4 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 07:43:45 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id d11so2296388and.4 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 07:44:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=f+GoTCZCz7ZyAK+81sxKadZkszKlXJTkvkf4rS30P98=; b=CgSRPW0wghSJwZPbjo7spcYywlVrRbdVf2C0E8NlyEZAYrYaWWFSNKkeURtWBOkTLd IWPbO60DOU7lVhQiwQKagWtDG/aSiQEQPevMqMOaNEueU2OwkUomtTvyJCliODv2YxlR fJDzc9FD7wHHiSUbYiK+/qK7QZxoGPY+HLct0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=J2mw0/kkTYpcxupJRqlvlq4le8QUrNH9xXpRS2c2V+VX/gtKrZC4q5HClEBewiGJs5 FTrqwvex+rUhZV4cwyqGMUxscH3SabS5eFQI1MUBUQwvlA6mpGAcMyXaeS+uYDYtNVa4 7Xw3q6AIUvIiAWBjWuvxnDZnClIHOgxXa5Bo0= MIME-Version: 1.0 In-Reply-To: <8AA97249241F7148BE6D3D8B93D83F5A1556A848@ftrdmel2> References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> <A997DBD5DD3E0B46A6D0353CF3E32CCB072FA926@xmb-sjc-233.amer.cisco.com> <8AA97249241F7148BE6D3D8B93D83F5A1556A848@ftrdmel2> Date: Tue, 31 Mar 2009 10:44:28 -0400 Received: by 10.100.132.4 with SMTP id f4mr4979648and.16.1238510684090; Tue, 31 Mar 2009 07:44:44 -0700 (PDT) Message-ID: <8c99930d0903310744g37041435o1a29836e14cb88ee@mail.gmail.com> Subject: Re: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? From: "Andrew G. Malis" <agmalis@gmail.com> To: frederic.jounay@orange-ftgroup.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: l2vpn@ietf.org, 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 14:43:46 -0000 Support. On Tue, Mar 31, 2009 at 3:17 AM, <frederic.jounay@orange-ftgroup.com> wrot= e: > Support > >>-----Original Message----- >>From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf >>Of Shane Amante >>Sent: Sunday, March 29, 2009 7:50 PM >>To: l2vpn@ietf.org >>Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >> >>Hi All, >> >>At the L2VPN WG meeting at IETF 74 in San Francisco, there was a >>request by the authors to make this a WG draft. Please indicate to the >>list if you do or don't support making this draft a WG document. =A0The >>following is a URL for this >>draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-i >>nterop-04 >> >>The deadline for comments will be 3 weeks: Friday, April 17. =A0Silence >>will not be counted as acceptance. >> >>Finally, please note that there is IPR filed against a previous version > >>of this draft (-03). =A0Please follow the procedures outlined in RFC 3979 > >>and consult your own legal counsel in your decision-making process. >> >>-shane >> > From agmalis@gmail.com Tue Mar 31 07:46:33 2009 Return-Path: <agmalis@gmail.com> 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 CA35828C13E for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:46: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 TNBwyDJMJ8cg for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 07:46:33 -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 00E6028C139 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 07:46:32 -0700 (PDT) Received: by yx-out-2324.google.com with SMTP id 8so3570862yxm.49 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 07:47:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vdowqIpbjG5iCEL1KtI8DOSQZ+HZxtSgr8yAdlayfB4=; b=vu/4+M+53KRcge6Lo39XIykjsMcpG43VkKv0tRlt8zRavPnGK+c84ObJWfRAtCWzhL /1VrousJyAwmrXfi4IyXwjNEgRPIHBJh7qmTruACjZWh7ZfQRTklOoPxWpZ22vySACW4 CyTq2c4+2rqBIjcLtxxbQey2a5B5KQPQLHZR4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Lw5Jy9YIFtJK/tE5H2v0s24wbaS1YslAZT3YvoxdbkX9c1cw60YZXEgXZEPzd2kfLZ 1/lsFeUiiEj4+7119iHmCQ/HhHCuoLFAojIHia68Dg27PND/5WzR0Z3WhleYSdpBF1Jw MMHiNxNtFtUc9dPd1uWMM6LB83kM0RZm792tg= MIME-Version: 1.0 In-Reply-To: <8AA97249241F7148BE6D3D8B93D83F5A1556AD5F@ftrdmel2> References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> <40FB0FFB97588246A1BEFB05759DC8A002CD834C@S4DE9JSAANI.ost.t-com.de> <8AA97249241F7148BE6D3D8B93D83F5A1556AD5F@ftrdmel2> Date: Tue, 31 Mar 2009 10:47:16 -0400 Received: by 10.100.96.9 with SMTP id t9mr4962568anb.95.1238510851602; Tue, 31 Mar 2009 07:47:31 -0700 (PDT) Message-ID: <8c99930d0903310747j67baba2asd0b91556bef5291f@mail.gmail.com> Subject: Re: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? From: "Andrew G. Malis" <agmalis@gmail.com> To: frederic.jounay@orange-ftgroup.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: l2vpn@ietf.org, 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 14:46:33 -0000 Support. On Tue, Mar 31, 2009 at 10:31 AM, <frederic.jounay@orange-ftgroup.com> wro= te: > Support. > > -----Urspr=FCngliche Nachricht----- > Von: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] Im Auftrag vo= n Shane Amante > Gesendet: Montag, 30. M=E4rz 2009 04:43 > An: l2vpn@ietf.org > Betreff: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > Hi All, > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a request = by the authors to make this a WG draft. Please indicate to the list if you = do or don't support making this draft a WG document. =A0The following is a = URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > > The deadline for comments will be 3 weeks: Friday, April 17. =A0Silence w= ill not be counted as acceptance. > > -shane > From ketan.paralkar@bell.ca Tue Mar 31 08:53:36 2009 Return-Path: <ketan.paralkar@bell.ca> 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 0D1133A6D8A for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 08:53:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.836 X-Spam-Level: X-Spam-Status: No, score=-4.836 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MISSING_SUBJECT=1.762, 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-ey6VK4ZyY7 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 08:53:35 -0700 (PDT) Received: from mail176.messagelabs.com (mail176.messagelabs.com [85.158.138.83]) by core3.amsl.com (Postfix) with ESMTP id 7B4CE3A679F for <l2vpn@ietf.org>; Tue, 31 Mar 2009 08:53:34 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: ketan.paralkar@bell.ca X-Msg-Ref: server-9.tower-176.messagelabs.com!1238514859!18827134!12 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [206.47.0.173] Received: (qmail 32381 invoked from network); 31 Mar 2009 15:54:31 -0000 Received: from bell.ca (HELO TLS.Exchange.Bell.ca) (206.47.0.173) by server-9.tower-176.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2009 15:54:31 -0000 Received: from hub02-wyn.bell.corp.bce.ca (142.182.199.50) by dm1c8f.exchange1.bell.ca (198.235.102.112) with Microsoft SMTP Server id 8.1.340.0; Tue, 31 Mar 2009 11:54:21 -0400 Received: from MBX08.bell.corp.bce.ca ([142.182.199.89]) by hub02-wyn.bell.corp.bce.ca ([142.182.199.50]) with mapi; Tue, 31 Mar 2009 11:54:19 -0400 From: <ketan.paralkar@bell.ca> To: <l2vpn@ietf.org>, <shane@castlepoint.net> Date: Tue, 31 Mar 2009 11:54:18 -0400 Subject: Thread-Index: AcmyGPDUpr1Oh8OXRliqm5wKQwEJpA== Message-ID: <EFAB6F21C0EA5D4A8AD8E43E7587C1290101F2D9C4@MBX08.bell.corp.bce.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_EFAB6F21C0EA5D4A8AD8E43E7587C1290101F2D9C4MBX08bellcorp_" MIME-Version: 1.0 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 15:53:36 -0000 --_000_EFAB6F21C0EA5D4A8AD8E43E7587C1290101F2D9C4MBX08bellcorp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Support. Ketan Paralkar MIET , CCIE 12179, JNCIS Sr. Network Architect BELL SYSTEMS & TECHNOLOGY Technology Development Bell Canada 76 Adelaide Street West, 15th Floor Toronto, Ontario M5H 1P6 Office (416)-353-3227 e-mail : ketan.paralkar@bell.ca<mailto:ketan.paralkar@bell.ca> The information contained herein is proprietary to BCE/Bell Canada and may = not be used, reproduced or disclosed to others except as specifically permi= tted in writing by the originator of the information. The recipient of thi= s information, by its retention and use, agrees to protect it from any loss= , theft or compromise. > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 7:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > Hi All, > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > > The deadline for comments will be 3 weeks: Friday, April 17. > Silence will not be counted as acceptance. > > -shane > --_000_EFAB6F21C0EA5D4A8AD8E43E7587C1290101F2D9C4MBX08bellcorp_ 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-micr= osoft-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;} @font-face {font-family:"Book Antiqua"; panose-1:2 4 6 2 5 3 5 3 3 4;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:Georgia; panose-1:2 4 5 2 5 4 5 2 3 3;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText {mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0cm; margin-bottom:.0001pt; font-size:10.5pt; font-family:Consolas;} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate {mso-style-priority:99; mso-style-link:"Balloon Text Char"; margin:0cm; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif";} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} span.BalloonTextChar {mso-style-name:"Balloon Text Char"; mso-style-priority:99; mso-style-link:"Balloon Text"; font-family:"Tahoma","sans-serif";} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-priority:99; mso-style-link:"Plain Text"; font-family:Consolas;} .MsoChpDefault {mso-style-type:export-only;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1033" /> </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-CA link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal><o:p> </o:p></p> <p class=3DMsoNormal><span lang=3DFR-CA style=3D'font-size:12.0pt;font-fami= ly:"Times New Roman","serif"'> Support.<o:p></o:p></span></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DFR-CA style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> = ;</o:p></span></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DFR-CA style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> = ;</o:p></span></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span lang=3DFR-CA style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'= >Ketan Paralkar MIET , CCIE 12179, JNCIS &= nbsp; &nbs= p; &= nbsp; &nbs= p; &= nbsp; &nbs= p; = <o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span style=3D'font= -size: 12.0pt;font-family:"Times New Roman","serif";color:blue'>Sr. Network Archit= ect<o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span style=3D'font= -size: 10.0pt;font-family:"Times New Roman","serif";color:blue'>BELL SYSTEMS & TECHNOLOGY<o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span style=3D'font= -size: 7.5pt;font-family:"Book Antiqua","serif";color:blue'>Technology Development= </span></i></b><b><i><span style=3D'font-size:8.0pt;font-family:"Arial","sans-serif";color:blue'><br> </span></i></b><b><i><span style=3D'font-size:7.5pt;font-family:"Book Antiq= ua","serif"; color:blue'>Bell</span></i></b><b><i><span style=3D'font-size:8.0pt;font-fa= mily: "Arial","sans-serif";color:blue'> </span></i></b><b><i><span style=3D'font-= size: 7.5pt;font-family:"Book Antiqua","serif";color:blue'>Canada</span></i></b><= b><i><span style=3D'font-size:8.0pt;font-family:"Arial","sans-serif";color:blue'><br> </span></i></b><b><i><span style=3D'font-size:7.5pt;font-family:"Book Antiq= ua","serif"; color:blue'>76 Adelaide Street West, 15th Floor</span></i></b><b><i><span style=3D'font-size:8.0pt;font-family:"Arial","sans-serif";color:blue'><br> </span></i></b><b><i><span style=3D'font-size:7.5pt;font-family:"Book Antiq= ua","serif"; color:blue'>Toronto</span></i></b><b><i><span style=3D'font-size:8.0pt; font-family:"Arial","sans-serif";color:blue'>, </span></i></b><b><i><span style=3D'font-size:7.5pt;font-family:"Book Antiqua","serif";color:blue'>Ont= ario</span></i></b><b><i><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'= ><o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span style=3D'font= -size: 7.5pt;font-family:"Book Antiqua","serif";color:blue'>M5H 1P6</span></i></b>= <b><i><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'= ><o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span style=3D'font= -size: 7.5pt;font-family:"Book Antiqua","serif";color:blue'>Office (416)-353-3227<br> </span></i></b><b><i><span style=3D'font-size:12.0pt;font-family:"Times New= Roman","serif"; color:blue'>e-mail : </span></i></b><b><i><span lang=3DPT-BR style=3D'font-= size: 12.0pt;font-family:"Times New Roman","serif";color:blue'><a href=3D"mailto:ketan.paralkar@bell.ca"><span lang=3DEN-CA style=3D'color:bl= ue'>ketan.paralkar@bell.ca</span></a></span></i></b><b><i><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:#3366= FF'>  = ; &n= bsp;  = ; <o:p></o:p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><b><i><span style=3D'font= -size: 12.0pt;font-family:"Times New Roman","serif";color:#3366FF'><o:p> </o:= p></span></i></b></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-size:= 12.0pt; font-family:"Times New Roman","serif"'><o:p> </o:p></span></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-size:= 12.0pt; font-family:"Times New Roman","serif"'> <b><i><span style=3D'color:#33= 66FF'><o:p></o:p></span></i></b></span></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-size:= 10.0pt; font-family:"Georgia","serif";color:navy'>The information contained herein = is proprietary to BCE/Bell Canada and may not be used, reproduced or disclosed= to others except as specifically permitted in writing by the originator of the information. The recipient of this information, by its retention and = use, agrees to protect it from any loss, theft or compromise.</span><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p= ></span></p> <p class=3DMsoNormal style=3D'margin-left:36.0pt'><span style=3D'font-size:= 12.0pt; font-family:"Times New Roman","serif"'> <o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New= Roman","serif"'><o:p> </o:p></span></p> <p class=3DMsoPlainText>> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf <o:p></o:p></p> <p class=3DMsoPlainText>> Of Shane Amante<o:p></o:p></p> <p class=3DMsoPlainText>> Sent: Sunday, March 29, 2009 7:43 PM<o:p></o:p= ></p> <p class=3DMsoPlainText>> To: l2vpn@ietf.org<o:p></o:p></p> <p class=3DMsoPlainText>> Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01= WG draft?<o:p></o:p></p> <p class=3DMsoPlainText>> <o:p></o:p></p> <p class=3DMsoPlainText>> Hi All,<o:p></o:p></p> <p class=3DMsoPlainText>> <o:p></o:p></p> <p class=3DMsoPlainText>> At the L2VPN WG meeting at IETF 74 in San Fran= cisco, there was a <o:p></o:p></p> <p class=3DMsoPlainText>> request by the authors to make this a WG draft= . Please indicate to the <o:p></o:p></p> <p class=3DMsoPlainText>> list if you do or don't support making this dr= aft a WG document. The <o:p></o:p></p> <p class=3DMsoPlainText>> following is a URL for this draft:<o:p></o:p><= /p> <p class=3DMsoPlainText>> <a href=3D"http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01">h= ttp://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01</a><o:p></o= :p></p> <p class=3DMsoPlainText>> <o:p></o:p></p> <p class=3DMsoPlainText>> The deadline for comments will be 3 weeks: Fri= day, April 17. <o:p></o:p></p> <p class=3DMsoPlainText>> Silence will not be counted as acceptance.<o:p= ></o:p></p> <p class=3DMsoPlainText>> <o:p></o:p></p> <p class=3DMsoPlainText>> -shane<o:p></o:p></p> <p class=3DMsoPlainText>> <o:p></o:p></p> <p class=3DMsoNormal><o:p> </o:p></p> </div> </body> </html> --_000_EFAB6F21C0EA5D4A8AD8E43E7587C1290101F2D9C4MBX08bellcorp_-- From Florin.Balus@alcatel-lucent.com Tue Mar 31 11:26:21 2009 Return-Path: <Florin.Balus@alcatel-lucent.com> 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 787223A6D43 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 11:26:21 -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 iHfDjMPdqnJH for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 11:26:20 -0700 (PDT) Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id 861F43A6956 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 11:26:20 -0700 (PDT) Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id n2VIRBWO023785; Tue, 31 Mar 2009 12:27:18 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.6]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 13:27:17 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 13:27:05 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <042001c9b205$9fa23c40$dee6b4c0$@com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? thread-index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCAACfzoIA== References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net><6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com> <042001c9b205$9fa23c40$dee6b4c0$@com> From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com> To: <davarish@yahoo.com>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 18:27:17.0754 (UTC) FILETIME=[5267BDA0:01C9B22E] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 18:26:21 -0000 Hi Shahram, I thought we discussed this aspect in Introduction (section 1, see 3rd paragraph starting at "A hierarchical solution for VPLS ..."). The PW scaling is achieved because in the core infrastructure one needs to maintain just one PW set for a B-component instead of M PW sets for M I-components. We did not get in the details of how PBB provides multiplexing of M I-components into one B-component as this is described in detail in the IEEE 802.1ah specification. And the L2VPN WG asked us to just reference the IEEE spec for the details to make it easier to keep synchronization between the two documents. Florin > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shahram Davari > Sent: Tuesday, March 31, 2009 6:36 AM > To: 'Shane Amante'; l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi, >=20 > I also support. However, text needs to be added to the Introduction to > make > it clear that similar to H-VPLS, the PBB over VPLS method (this draft) > is > another method to overcome the scalability issue of VPLS that exist due > to > the large number of required PWs. The PBB over VPLS reduces the number > of > required PWs and therefore improves VPLS scalability.. >=20 > Best regards, > Shahram >=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of > Shane Amante > Sent: Sunday, March 29, 2009 10:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. >=20 > -shane From phe@soapstonenetworks.com Tue Mar 31 11:49:30 2009 Return-Path: <phe@soapstonenetworks.com> 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 53CBA28C0FE for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 11:49:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.648 X-Spam-Level: X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[AWL=0.951, 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 bJhIwlopRfgm for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 11:49:29 -0700 (PDT) Received: from p01c11o143.mxlogic.net (p01c11o143.mxlogic.net [208.65.144.66]) by core3.amsl.com (Postfix) with ESMTP id 44E553A684F for <l2vpn@ietf.org>; Tue, 31 Mar 2009 11:49:29 -0700 (PDT) Received: from unknown [12.230.177.130] (EHLO p01c11o143.mxlogic.net) by p01c11o143.mxlogic.net (mxl_mta-6.1.1-2) with ESMTP id 4f562d94.2710539152.194988.00-502.p01c11o143.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 31 Mar 2009 12:50:29 -0600 (MDT) Received: from unknown [12.230.177.130] (EHLO smtp.soapstonenetworks.com) by p01c11o143.mxlogic.net (mxl_mta-6.1.1-2) over TLS secured channel with ESMTP id 3d562d94.3570707344.194922.00-001.p01c11o143.mxlogic.net (envelope-from <phe@soapstonenetworks.com>); Tue, 31 Mar 2009 12:50:15 -0600 (MDT) Received: from corp-e2k7-mbx01.Soapstone.local ([172.24.2.72]) by corp-e2k7-hub01.Soapstone.local ([172.24.2.84]) with mapi; Tue, 31 Mar 2009 14:49:54 -0400 From: Peng He <phe@soapstonenetworks.com> To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, ext Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org> Date: Tue, 31 Mar 2009 14:49:53 -0400 Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jlf7x1l22CjRA29h2XMSd4YhwAFJprAABt4cGAAMwTnUA== Message-ID: <E6D5CAC0ACC932498E6AC1A692E0CBA12297C39A3E@corp-e2k7-mbx01.Soapstone.local> References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> <077E41CFFD002C4CAB7DFA4386A53264798D90@DEMUEXC014.nsn-intra.net> <7F115A41909B2641A9550322C4DF9D568F8E0D@xmb-sjc-22d.amer.cisco.com> In-Reply-To: <7F115A41909B2641A9550322C4DF9D568F8E0D@xmb-sjc-22d.amer.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam: [F=0.2000000000; S=0.200(2009020301)] X-MAIL-FROM: <phe@soapstonenetworks.com> X-SOURCE-IP: [12.230.177.130] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 18:49:30 -0000 Hello Ali, The titles of Fig 5 and Fig. 6 might be read as " H-VPLS with Mixed PBN and= PBBN Access: xxxx" instead of " H-VPLS with Mixed PBB and PBBN Access: xxx= x". Regards, Peng > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Ali Sajassi (sajassi) > Sent: Monday, March 30, 2009 3:13 PM > To: Sprecher, Nurit (NSN - IL/Hod HaSharon); ext Shane Amante; > l2vpn@ietf.org > Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 >=20 > Hi Nurit, >=20 > > -----Original Message----- > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] > > On Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon) > > Sent: Sunday, March 29, 2009 10:21 PM > > To: ext Shane Amante; l2vpn@ietf.org > > Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > > > > Hi, > > I'll go over the draft again. In the meantime I'll appreciate > > if the authors can clarify and help me resolve my confusion > > about this draft. > > Apparently I thought the intention of the draft is to enhance > > scalability, and to avoid the learning of all customers' MAC > > addresses. >=20 > The purpose of PBB encap is two fold: a) for C-MAC scalability and b) > for PW scalability >=20 > > In the last meeting there was a comment indicating that all > > I-SIDs are handled in the E-NNI and that scalability is not > > really solved in this case. It looks as the intention is to > > make more efficient replication at the E-NNI. >=20 > It is not clear to me what scenario you are referring to but there is > no > C-MAC learning & forwarding at E-NNI between PBB network and VPLS core > network. In case of loosely-coupled I-SID domains, no I-SID translation > is required at E-NNI. And in case of independent I-SID domains, I-SID > translation may be required at E-NNI. However, no C-MAC address lookup > is required at E-NNI for both of these cases. >=20 > Cheers, > Ali >=20 > > Would the authors be so kind and clarify this to me. > > Best regards, > > Nurit > > > > -----Original Message----- > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] > > On Behalf Of ext Shane Amante > > Sent: Monday, March 30, 2009 04:50 > > To: l2vpn@ietf.org > > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > > > > Hi All, > > > > At the L2VPN WG meeting at IETF 74 in San Francisco, there > > was a request by the authors to make this a WG draft. Please > > indicate to the list if you do or don't support making this > > draft a WG document. The following is a URL for this > > draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb- > > interop-04 > > > > The deadline for comments will be 3 weeks: Friday, April 17. > > Silence will not be counted as acceptance. > > > > Finally, please note that there is IPR filed against a > > previous version of this draft (-03). Please follow the > > procedures outlined in RFC 3979 and consult your own legal > > counsel in your decision-making process. > > > > -shane > > From DALLAN@nortel.com Tue Mar 31 11:52:46 2009 Return-Path: <DALLAN@nortel.com> 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 2E97C3A6DB6 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 11:52:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.549 X-Spam-Level: X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 dQxZHKOoKFqw for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 11:52:45 -0700 (PDT) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 3CB553A6DB0 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 11:52:45 -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 n2VIrfY11153 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 18:53:41 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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 14:53:25 -0400 Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE193A82DA@zcarhxm2.corp.nortel.com> In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCAACfzoIAABKQPQ References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net><6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com><042001c9b205$9fa23c40$dee6b4c0$@com> <4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> From: "David Allan" <dallan@nortel.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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 18:52:46 -0000 I agree with the single PW mesh for B-component aspect (vs. many I-component meshes) and the mention of IEEE protocol snooping for multicast containment...but I'd like to see 802.1aq also mentioned in section 6 as a means of controlling filtering of multicast... Cheers Dave > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shane Amante > Sent: Sunday, March 29, 2009 10:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi All, >=20 > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a=20 > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The=20 > following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 >=20 > The deadline for comments will be 3 weeks: Friday, April 17. Silence=20 > will not be counted as acceptance. >=20 > -shane From davarish@yahoo.com Tue Mar 31 12:15:37 2009 Return-Path: <davarish@yahoo.com> 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 4AC783A6DCC for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:15:37 -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 mV5nmrToqnyJ for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:15:36 -0700 (PDT) Received: from smtp121.rog.mail.re2.yahoo.com (smtp121.rog.mail.re2.yahoo.com [206.190.53.26]) by core3.amsl.com (Postfix) with SMTP id 288873A6A79 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 12:15:36 -0700 (PDT) Received: (qmail 5047 invoked from network); 31 Mar 2009 19:16:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=teWiRLxpaSbyUikGRimjUBgZa3xVQQDYEXKyvybeMnP62qOxlLANpQNqVJTT4P6Okdqx4VS26xL1f3jmHXNemIIp/4z0NkSLolJaDtRjXeiHnzWr5uYGWJsD65Na0Bjc/FR+sTwOkekIHvmEJrCDd+id34+BFlluCoUE0ElkWKk= ; Received: from unknown (HELO ShahramPC) (davarish@99.238.119.231 with login) by smtp121.rog.mail.re2.yahoo.com with SMTP; 31 Mar 2009 19:16:34 -0000 X-YMail-OSG: uR36A9EVM1kvEBQxwsKtXaUtAwVKofqsFD9X.u4vx7sPwWcgVpXBoTbiPKEbG7ojRQ-- X-Yahoo-Newman-Property: ymail-3 From: "Shahram Davari" <davarish@yahoo.com> To: "'BALUS Florin'" <Florin.Balus@alcatel-lucent.com>, <l2vpn@ietf.org> References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net><6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com> <042001c9b205$9fa23c40$dee6b4c0$@com> <4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 15:16:34 -0400 Message-ID: <000301c9b235$352a8680$9f7f9380$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCAACfzoIAACEX2g Content-Language: en-ca X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: davarish@yahoo.com List-Id: <l2vpn.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 19:15:37 -0000 Hi Florin, It does to some extent. But I think it Introduction text needs to better reflect what you described below. Since it is not very clear what the objective of this draft is and how it achieves such objectives. Best regards, Shahram -----Original Message----- From: BALUS Florin [mailto:Florin.Balus@alcatel-lucent.com] Sent: March-31-09 2:27 PM To: davarish@yahoo.com; l2vpn@ietf.org Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Hi Shahram, I thought we discussed this aspect in Introduction (section 1, see 3rd paragraph starting at "A hierarchical solution for VPLS ..."). The PW scaling is achieved because in the core infrastructure one needs to maintain just one PW set for a B-component instead of M PW sets for M I-components. We did not get in the details of how PBB provides multiplexing of M I-components into one B-component as this is described in detail in the IEEE 802.1ah specification. And the L2VPN WG asked us to just reference the IEEE spec for the details to make it easier to keep synchronization between the two documents. Florin > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of Shahram Davari > Sent: Tuesday, March 31, 2009 6:36 AM > To: 'Shane Amante'; l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > Hi, > > I also support. However, text needs to be added to the Introduction to > make > it clear that similar to H-VPLS, the PBB over VPLS method (this draft) > is > another method to overcome the scalability issue of VPLS that exist due > to > the large number of required PWs. The PBB over VPLS reduces the number > of > required PWs and therefore improves VPLS scalability.. > > Best regards, > Shahram > > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of > Shane Amante > Sent: Sunday, March 29, 2009 10:43 PM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > Hi All, > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > request by the authors to make this a WG draft. Please indicate to the > list if you do or don't support making this draft a WG document. The > following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > > The deadline for comments will be 3 weeks: Friday, April 17. Silence > will not be counted as acceptance. > > -shane From sajassi@cisco.com Tue Mar 31 12:18:10 2009 Return-Path: <sajassi@cisco.com> 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 8323328C18C for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:18:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.799 X-Spam-Level: X-Spam-Status: No, score=-5.799 tagged_above=-999 required=5 tests=[AWL=0.800, 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 VtFOeOhVwj1f for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:18:09 -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 5427828C115 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 12:18:09 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.39,303,1235952000"; d="scan'208";a="149069347" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 31 Mar 2009 19:19:09 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n2VJJ8Qb005081; Tue, 31 Mar 2009 12:19:08 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n2VJJ8xL022806; Tue, 31 Mar 2009 19:19:08 GMT Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Mar 2009 12:19: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: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Tue, 31 Mar 2009 12:19:07 -0700 Message-ID: <7F115A41909B2641A9550322C4DF9D568F91F2@xmb-sjc-22d.amer.cisco.com> In-Reply-To: <E6D5CAC0ACC932498E6AC1A692E0CBA12297C39A3E@corp-e2k7-mbx01.Soapstone.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4jlf7x1l22CjRA29h2XMSd4YhwAFJprAABt4cGAAMwTnUAABF3HA References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net><077E41CFFD002C4CAB7DFA4386A53264798D90@DEMUEXC014.nsn-intra.net><7F115A41909B2641A9550322C4DF9D568F8E0D@xmb-sjc-22d.amer.cisco.com> <E6D5CAC0ACC932498E6AC1A692E0CBA12297C39A3E@corp-e2k7-mbx01.Soapstone.local> From: "Ali Sajassi (sajassi)" <sajassi@cisco.com> To: "Peng He" <phe@soapstonenetworks.com>, "Sprecher, Nurit (NSN -IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "ext Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 19:19:08.0761 (UTC) FILETIME=[90B5BC90:01C9B235] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3857; t=1238527148; x=1239391148; 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=20draft-sajassi-l2vpn-vpls-pbb-interop-04 =20WG=20draft? |Sender:=20; bh=ugi2A4oEWEShn7hta75U2mRdZNdQXlJeRPE8mJYMddk=; b=ueupTnqwpFn5dinNzJFXnkkrzt2djsaBipOjdODKthkVFzxBgxRPEVd4yt gGy7a/mB6/pq/iyoktRwxWxTdZyzNRGVtQxC062+Tz3YlhqdVjxAi6E/3N3W flSuqTAnWr; Authentication-Results: sj-dkim-3; header.From=sajassi@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 19:18:10 -0000 You're correct. It should be "PBN" in both fig 5 & 6. I will update it for the next rev. Thanks, Ali=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Peng He > Sent: Tuesday, March 31, 2009 11:50 AM > To: Ali Sajassi (sajassi); Sprecher, Nurit (NSN -IL/Hod=20 > HaSharon); ext Shane Amante; l2vpn@ietf.org > Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? >=20 > Hello Ali, >=20 > The titles of Fig 5 and Fig. 6 might be read as " H-VPLS with=20 > Mixed PBN and PBBN Access: xxxx" instead of " H-VPLS with=20 > Mixed PBB and PBBN Access: xxxx". >=20 >=20 > Regards, > Peng >=20 > > -----Original Message----- > > From: l2vpn-bounces@ietf.org=20 > [mailto:l2vpn-bounces@ietf.org] On Behalf=20 > > Of Ali Sajassi (sajassi) > > Sent: Monday, March 30, 2009 3:13 PM > > To: Sprecher, Nurit (NSN - IL/Hod HaSharon); ext Shane Amante;=20 > > l2vpn@ietf.org > > Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > >=20 > >=20 > > Hi Nurit, > >=20 > > > -----Original Message----- > > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On=20 > > > Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon) > > > Sent: Sunday, March 29, 2009 10:21 PM > > > To: ext Shane Amante; l2vpn@ietf.org > > > Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > > > > > > Hi, > > > I'll go over the draft again. In the meantime I'll=20 > appreciate if the=20 > > > authors can clarify and help me resolve my confusion about this=20 > > > draft. > > > Apparently I thought the intention of the draft is to enhance=20 > > > scalability, and to avoid the learning of all customers' MAC=20 > > > addresses. > >=20 > > The purpose of PBB encap is two fold: a) for C-MAC=20 > scalability and b)=20 > > for PW scalability > >=20 > > > In the last meeting there was a comment indicating that=20 > all I-SIDs=20 > > > are handled in the E-NNI and that scalability is not=20 > really solved=20 > > > in this case. It looks as the intention is to make more efficient=20 > > > replication at the E-NNI. > >=20 > > It is not clear to me what scenario you are referring to=20 > but there is=20 > > no C-MAC learning & forwarding at E-NNI between PBB network=20 > and VPLS=20 > > core network. In case of loosely-coupled I-SID domains, no I-SID=20 > > translation is required at E-NNI. And in case of independent I-SID=20 > > domains, I-SID translation may be required at E-NNI.=20 > However, no C-MAC=20 > > address lookup is required at E-NNI for both of these cases. > >=20 > > Cheers, > > Ali > >=20 > > > Would the authors be so kind and clarify this to me. > > > Best regards, > > > Nurit > > > > > > -----Original Message----- > > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On=20 > > > Behalf Of ext Shane Amante > > > Sent: Monday, March 30, 2009 04:50 > > > To: l2vpn@ietf.org > > > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > > > > > > Hi All, > > > > > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a=20 > > > request by the authors to make this a WG draft. Please=20 > indicate to=20 > > > the list if you do or don't support making this draft a=20 > WG document. =20 > > > The following is a URL for this > > > draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb- > > > interop-04 > > > > > > The deadline for comments will be 3 weeks: Friday, April 17. > > > Silence will not be counted as acceptance. > > > > > > Finally, please note that there is IPR filed against a previous=20 > > > version of this draft (-03). Please follow the=20 > procedures outlined=20 > > > in RFC 3979 and consult your own legal counsel in your=20 > > > decision-making process. > > > > > > -shane > > > >=20 From sajassi@cisco.com Tue Mar 31 12:31:43 2009 Return-Path: <sajassi@cisco.com> 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 69D343A6817 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:31:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.932 X-Spam-Level: X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667, 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 xfqa5YvF9KEs for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:31:42 -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 8630F28C195 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 12:31:42 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.39,303,1235952000"; d="scan'208";a="148801607" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 31 Mar 2009 19:32:42 +0000 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n2VJWgPj004700; Tue, 31 Mar 2009 12:32:42 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n2VJWg8t025459; Tue, 31 Mar 2009 19:32:42 GMT Received: from xmb-sjc-22d.amer.cisco.com ([128.107.191.68]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Mar 2009 12:32:42 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 12:32:41 -0700 Message-ID: <7F115A41909B2641A9550322C4DF9D568F9200@xmb-sjc-22d.amer.cisco.com> In-Reply-To: <000301c9b235$352a8680$9f7f9380$@com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Thread-Index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCAACfzoIAACEX2gAABx3mA= References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net><6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com><042001c9b205$9fa23c40$dee6b4c0$@com><4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> <000301c9b235$352a8680$9f7f9380$@com> From: "Ali Sajassi (sajassi)" <sajassi@cisco.com> To: <davarish@yahoo.com>, "BALUS Florin" <Florin.Balus@alcatel-lucent.com>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 19:32:42.0204 (UTC) FILETIME=[758F49C0:01C9B237] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3373; t=1238527962; x=1239391962; 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=20draft-balus-sajassi-l2vpn-pbb-vpls-01=2 0WG=20draft? |Sender:=20; bh=OY47Rxn1z6y9F99R/kppPejrngZ6IWv17YHM3pRiUoo=; b=qchyq55Aij9xAuRLm20jVdNdaR49KFJaZY1VMAZuoGx3nm2A195VGlC8ro 6OdYthZK0KSQBz0CQ/LrswFqw0Fjz3ypGSTpnGM/0wPkVBWp8HAnK0kYCy68 AqUHeK5vMT; Authentication-Results: sj-dkim-3; header.From=sajassi@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 19:31:43 -0000 Hi Shahram, The bottom of the 3rd paragraph (intro sec.) describes how we get PW scalability with PBB-VPLS versus VPLS. If the description is not clear, let us know how we can improve the text and we'll consider it in the next rev. Cheers, Ali=20 > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org]=20 > On Behalf Of Shahram Davari > Sent: Tuesday, March 31, 2009 12:17 PM > To: 'BALUS Florin'; l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi Florin, >=20 > It does to some extent. But I think it Introduction text=20 > needs to better reflect what you described below. Since it is=20 > not very clear what the objective of this draft is and how it=20 > achieves such objectives. >=20 > Best regards, > Shahram >=20 > -----Original Message----- > From: BALUS Florin [mailto:Florin.Balus@alcatel-lucent.com] > Sent: March-31-09 2:27 PM > To: davarish@yahoo.com; l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi Shahram, >=20 > I thought we discussed this aspect in Introduction (section=20 > 1, see 3rd paragraph starting at "A hierarchical solution for=20 > VPLS ..."). The PW scaling is achieved because in the core=20 > infrastructure one needs to maintain just one PW set for a=20 > B-component instead of M PW sets for M I-components. >=20 > We did not get in the details of how PBB provides=20 > multiplexing of M I-components into one B-component as this=20 > is described in detail in the IEEE 802.1ah specification. And=20 > the L2VPN WG asked us to just reference the IEEE spec for the=20 > details to make it easier to keep synchronization between the=20 > two documents. >=20 > Florin >=20 > > -----Original Message----- > > From: l2vpn-bounces@ietf.org=20 > [mailto:l2vpn-bounces@ietf.org] On Behalf=20 > > Of Shahram Davari > > Sent: Tuesday, March 31, 2009 6:36 AM > > To: 'Shane Amante'; l2vpn@ietf.org > > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > >=20 > > Hi, > >=20 > > I also support. However, text needs to be added to the=20 > Introduction to=20 > > make it clear that similar to H-VPLS, the PBB over VPLS=20 > method (this=20 > > draft) is another method to overcome the scalability issue of VPLS=20 > > that exist > due > > to > > the large number of required PWs. The PBB over VPLS reduces=20 > the number=20 > > of required PWs and therefore improves VPLS scalability.. > >=20 > > Best regards, > > Shahram > >=20 > > -----Original Message----- > > From: l2vpn-bounces@ietf.org=20 > [mailto:l2vpn-bounces@ietf.org] On Behalf=20 > > Of Shane Amante > > Sent: Sunday, March 29, 2009 10:43 PM > > To: l2vpn@ietf.org > > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > >=20 > > Hi All, > >=20 > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a=20 > > request by the authors to make this a WG draft. Please=20 > indicate to the=20 > > list if you do or don't support making this draft a WG=20 > document. The=20 > > following is a URL for this draft: > > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > >=20 > > The deadline for comments will be 3 weeks: Friday, April=20 > 17. Silence=20 > > will not be counted as acceptance. > >=20 > > -shane >=20 >=20 From Florin.Balus@alcatel-lucent.com Tue Mar 31 12:40:01 2009 Return-Path: <Florin.Balus@alcatel-lucent.com> 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 9E4493A69AE for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:40:01 -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 ochOiJU7Jppf for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:40:00 -0700 (PDT) Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id 8AFAB3A6817 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 12:40:00 -0700 (PDT) Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id n2VJevfe005963; Tue, 31 Mar 2009 13:40:59 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.6]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 14:40:52 -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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 14:40:41 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B05432B60@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <000301c9b235$352a8680$9f7f9380$@com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? thread-index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCAACfzoIAACEX2gAAA+WbA= References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net><6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com> <042001c9b205$9fa23c40$dee6b4c0$@com> <4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> <000301c9b235$352a8680$9f7f9380$@com> From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com> To: <davarish@yahoo.com>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 19:40:52.0833 (UTC) FILETIME=[99FF5510:01C9B238] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 19:40:01 -0000 Hi Shahram, The paragraph I mentioned below highlights we believe the problem space: scalability of MAC table and service instances (including PW set). But we will definitely take another shot at the Introduction in the next revision of the draft to improve readability and address your comment.=20 Florin > -----Original Message----- > From: Shahram Davari [mailto:davarish@yahoo.com] > Sent: Tuesday, March 31, 2009 12:17 PM > To: BALUS Florin; l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi Florin, >=20 > It does to some extent. But I think it Introduction text needs to > better > reflect what you described below. Since it is not very clear what the > objective of this draft is and how it achieves such objectives. >=20 > Best regards, > Shahram >=20 > -----Original Message----- > From: BALUS Florin [mailto:Florin.Balus@alcatel-lucent.com] > Sent: March-31-09 2:27 PM > To: davarish@yahoo.com; l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > Hi Shahram, >=20 > I thought we discussed this aspect in Introduction (section 1, see 3rd > paragraph starting at "A hierarchical solution for VPLS ..."). The PW > scaling is achieved because in the core infrastructure one needs to > maintain just one PW set for a B-component instead of M PW sets for M > I-components. >=20 > We did not get in the details of how PBB provides multiplexing of M > I-components into one B-component as this is described in detail in the > IEEE 802.1ah specification. And the L2VPN WG asked us to just reference > the IEEE spec for the details to make it easier to keep synchronization > between the two documents. >=20 > Florin >=20 > > -----Original Message----- > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On > Behalf > > Of Shahram Davari > > Sent: Tuesday, March 31, 2009 6:36 AM > > To: 'Shane Amante'; l2vpn@ietf.org > > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > > > Hi, > > > > I also support. However, text needs to be added to the Introduction > to > > make > > it clear that similar to H-VPLS, the PBB over VPLS method (this > draft) > > is > > another method to overcome the scalability issue of VPLS that exist > due > > to > > the large number of required PWs. The PBB over VPLS reduces the > number > > of > > required PWs and therefore improves VPLS scalability.. > > > > Best regards, > > Shahram > > > > -----Original Message----- > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On > Behalf > > Of > > Shane Amante > > Sent: Sunday, March 29, 2009 10:43 PM > > To: l2vpn@ietf.org > > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > > > Hi All, > > > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > > request by the authors to make this a WG draft. Please indicate to > the > > list if you do or don't support making this draft a WG document. The > > following is a URL for this draft: > > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > > > > The deadline for comments will be 3 weeks: Friday, April 17. Silence > > will not be counted as acceptance. > > > > -shane From Florin.Balus@alcatel-lucent.com Tue Mar 31 12:45:28 2009 Return-Path: <Florin.Balus@alcatel-lucent.com> 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 8AC363A67AE for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:45:28 -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 fQ+Dcp9SQq21 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 12:45:27 -0700 (PDT) Received: from audl952.usa.alcatel.com (audl952.usa.alcatel.com [143.209.238.159]) by core3.amsl.com (Postfix) with ESMTP id 984753A67F3 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 12:45:26 -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 n2VJkPtu022623; Tue, 31 Mar 2009 13:46:25 -0600 Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.6]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 31 Mar 2009 14:46: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: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? Date: Tue, 31 Mar 2009 14:46:14 -0500 Message-ID: <4A5028372622294A99B8FFF6BD06EB7B05432B65@USDALSMBS03.ad3.ad.alcatel.com> In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE193A82DA@zcarhxm2.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? thread-index: Acmw4UKX3WFKeyIMSc+yTHe0JvOK0ABHnUKAAAFCbCAACfzoIAABKQPQAAHQSvA= References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net><6738A78F51650A4FAEDCF6844B26C21413461536F3@USEXCHANGE.corp.extremenetworks.com><042001c9b205$9fa23c40$dee6b4c0$@com><4A5028372622294A99B8FFF6BD06EB7B05432AFE@USDALSMBS03.ad3.ad.alcatel.com> <87AC5F88F03E6249AEA68D40BD3E00BE193A82DA@zcarhxm2.corp.nortel.com> From: "BALUS Florin" <Florin.Balus@alcatel-lucent.com> To: "David Allan" <dallan@nortel.com>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 19:46:25.0828 (UTC) FILETIME=[607A5640:01C9B239] 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 19:45:28 -0000 Dave, I am ok to add 802.1aq reference to section 6 in the next revision. Florin > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf > Of David Allan > Sent: Tuesday, March 31, 2009 11:53 AM > To: l2vpn@ietf.org > Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? >=20 > I agree with the single PW mesh for B-component aspect (vs. many > I-component meshes) and the mention of IEEE protocol snooping for > multicast containment...but I'd like to see 802.1aq also mentioned in > section 6 as a means of controlling filtering of multicast... >=20 > Cheers > Dave >=20 >=20 > > -----Original Message----- > > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On > Behalf >=20 > > Of Shane Amante > > Sent: Sunday, March 29, 2009 10:43 PM > > To: l2vpn@ietf.org > > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > > > Hi All, > > > > At the L2VPN WG meeting at IETF 74 in San Francisco, there was a > > request by the authors to make this a WG draft. Please indicate to > the >=20 > > list if you do or don't support making this draft a WG document. The > > following is a URL for this draft: > > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > > > > The deadline for comments will be 3 weeks: Friday, April 17. Silence > > will not be counted as acceptance. > > > > -shane From Alexander.Shafir@tellabs.com Tue Mar 31 14:21:21 2009 Return-Path: <Alexander.Shafir@tellabs.com> 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 A3F763A6AE5 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 14:21:21 -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 EzHt7WefjCJr for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 14:21:20 -0700 (PDT) Received: from mx4.tellabs.com (mx4.tellabs.com [204.154.129.57]) by core3.amsl.com (Postfix) with ESMTP id C01F63A6A4A for <l2vpn@ietf.org>; Tue, 31 Mar 2009 14:21:20 -0700 (PDT) X-SBRS: None X-IronPort-AV: E=Sophos;i="4.39,304,1235952000"; d="scan'208";a="1280297572" Received: from usnvwwms2c.hq.tellabs.com (HELO USNVEX3.tellabs-west.tellabsinc.net) ([172.23.216.105]) by mx4-priv.tellabs.com with ESMTP; 31 Mar 2009 21:22:17 +0000 Received: from USPAEX2.tellabs-west.tellabsinc.net ([172.26.6.136]) by USNVEX3.tellabs-west.tellabsinc.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 16:22:17 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Date: Tue, 31 Mar 2009 14:22:16 -0700 Message-ID: <0D2161FC73CF2F42908B475E37B76F6203724215@USPAEX2.tellabs-west.tellabsinc.net> In-Reply-To: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Thread-Index: Acmw4j5ZFmTQTJzxSnueLTbDdy5YvwBXltWw References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> From: "Shafir, Alexander" <Alexander.Shafir@tellabs.com> To: "Shane Amante" <shane@castlepoint.net>, <l2vpn@ietf.org> X-OriginalArrivalTime: 31 Mar 2009 21:22:17.0149 (UTC) FILETIME=[C48846D0:01C9B246] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Tue, 31 Mar 2009 21:21:21 -0000 Hello Ali, In my further review of the draft the following question came up: In paragraphs 4.1 and 4.2 the assumption is made that CE is directly connected to PBBN via C-Tagged interface. I might be mistaken, but is there C-Tagged interface defined for PBBN in 802.1ah?=20 Sincerely, Alex. -----Original Message----- From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of Shane Amante Sent: Sunday, March 29, 2009 7:50 PM To: l2vpn@ietf.org Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? Hi All, At the L2VPN WG meeting at IETF 74 in San Francisco, there was a =20 request by the authors to make this a WG draft. Please indicate to the =20 list if you do or don't support making this draft a WG document. The =20 following is a URL for this draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-interop-04 The deadline for comments will be 3 weeks: Friday, April 17. Silence =20 will not be counted as acceptance. Finally, please note that there is IPR filed against a previous =20 version of this draft (-03). Please follow the procedures outlined in =20 RFC 3979 and consult your own legal counsel in your decision-making =20 process. -shane =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D From y.kamite@ntt.com Tue Mar 31 19:18:36 2009 Return-Path: <y.kamite@ntt.com> 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 8E21C3A6A31 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 19:18:36 -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 bE4IhgADjpX7 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 19:18:35 -0700 (PDT) Received: from mgw4.noc.ntt.com (mgw4.noc.ntt.com [210.160.15.15]) by core3.amsl.com (Postfix) with ESMTP id A98993A69FB for <l2vpn@ietf.org>; Tue, 31 Mar 2009 19:18:35 -0700 (PDT) Received: from mop3.noc.ntt.com by mgw4.noc.ntt.com (NTT-Com MailSV) with ESMTP id n312JYpO019338 for <l2vpn@ietf.org>; Wed, 1 Apr 2009 11:19:34 +0900 (JST) Received: from mip02.noc.ntt.com (mvi2.noc.ntt.com) by mop3.noc.ntt.com (NTT-Com MailSV) with ESMTP id <0KHE0045BH4843@ntt.com> for l2vpn@ietf.org; Wed, 01 Apr 2009 11:19:34 +0900 (JST) Date: Wed, 01 Apr 2009 11:14:33 +0900 From: "Yuji KAMITE" <y.kamite@ntt.com> Subject: RE: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? In-reply-to: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@castlepoint.net> To: l2vpn@ietf.org Message-id: <015f01c9b26f$99572930$b3d80e0a@coe.ntt.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1933 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Thread-index: Acmw4UPl8VvFB/PWSBGEjZQJEDsi0wBi+LUw References: <5ABF91A0-8CCF-40A2-AB7B-25F2060B23B8@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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 01 Apr 2009 02:18:36 -0000 Suport. -Yuji > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] > On Behalf Of Shane Amante > Sent: Monday, March 30, 2009 11:43 AM > To: l2vpn@ietf.org > Subject: draft-balus-sajassi-l2vpn-pbb-vpls-01 WG draft? > > Hi All, > > At the L2VPN WG meeting at IETF 74 in San Francisco, there > was a request by the authors to make this a WG draft. Please > indicate to the list if you do or don't support making this > draft a WG document. The following is a URL for this draft: > http://tools.ietf.org/html/draft-balus-sajassi-l2vpn-pbb-vpls-01 > > The deadline for comments will be 3 weeks: Friday, April 17. > Silence will not be counted as acceptance. > > -shane From y.kamite@ntt.com Tue Mar 31 19:18:43 2009 Return-Path: <y.kamite@ntt.com> 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 433383A6AE9 for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 19:18:43 -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 APwaIliJ23MR for <l2vpn@core3.amsl.com>; Tue, 31 Mar 2009 19:18:42 -0700 (PDT) Received: from mgw3.noc.ntt.com (mgw3.noc.ntt.com [210.160.15.14]) by core3.amsl.com (Postfix) with ESMTP id 3A5F93A6AE4 for <l2vpn@ietf.org>; Tue, 31 Mar 2009 19:18:42 -0700 (PDT) Received: from mop3.noc.ntt.com by mgw3.noc.ntt.com (NTT-Com MailSV) with ESMTP id n312JeId009227 for <l2vpn@ietf.org>; Wed, 1 Apr 2009 11:19:41 +0900 (JST) Received: from mip01.noc.ntt.com (mvi3.noc.ntt.com) by mop3.noc.ntt.com (NTT-Com MailSV) with ESMTP id <0KHE004DTH4O43@ntt.com> for l2vpn@ietf.org; Wed, 01 Apr 2009 11:19:40 +0900 (JST) Date: Wed, 01 Apr 2009 11:14:33 +0900 From: "Yuji KAMITE" <y.kamite@ntt.com> Subject: RE: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? In-reply-to: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@castlepoint.net> To: l2vpn@ietf.org Message-id: <016001c9b26f$9975adb0$b3d80e0a@coe.ntt.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1933 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Thread-index: Acmw4jetjfYkUpOERx2prPCf5KmIhgBjNBXQ References: <7D1D556B-38E9-47B8-B66A-5C764AAD3419@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: <http://www.ietf.org/mail-archive/web/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> X-List-Received-Date: Wed, 01 Apr 2009 02:18:43 -0000 Support -Yuji > -----Original Message----- > From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] > On Behalf Of Shane Amante > Sent: Monday, March 30, 2009 11:50 AM > To: l2vpn@ietf.org > Subject: draft-sajassi-l2vpn-vpls-pbb-interop-04 WG draft? > > Hi All, > > At the L2VPN WG meeting at IETF 74 in San Francisco, there > was a request by the authors to make this a WG draft. Please > indicate to the list if you do or don't support making this > draft a WG document. The following is a URL for this > draft:http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb- > interop-04 > > The deadline for comments will be 3 weeks: Friday, April 17. > Silence will not be counted as acceptance. > > Finally, please note that there is IPR filed against a > previous version of this draft (-03). Please follow the > procedures outlined in RFC 3979 and consult your own legal > counsel in your decision-making process. > > -shane
- Time slots for IETF 74 L2VPN WG? Shane Amante