From l2vpn-bounces@ietf.org  Mon Jun  2 15:15:03 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF4F23A6A19;
	Mon,  2 Jun 2008 15:15:03 -0700 (PDT)
X-Original-To: l2vpn@ietf.org
Delivered-To: l2vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id A58223A69A6; Mon,  2 Jun 2008 15:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l2vpn-vpls-mcast-04.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080602221501.A58223A69A6@core3.amsl.com>
Date: Mon,  2 Jun 2008 15:15:01 -0700 (PDT)
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org


--NextPart

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


	Title           : Multicast in VPLS
	Author(s)       : R. Aggarwal, et al.
	Filename        : draft-ietf-l2vpn-vpls-mcast-04.txt
	Pages           : 42
	Date            : 2008-06-02

This document describes a solution for overcoming a subset of the
limitations of existing VPLS multicast solutions. It describes
procedures for VPLS multicast that utilize multicast trees in the
sevice provider (SP) network.  One such multicast tree can be shared
between multiple VPLS instances.  Procedures by which a single
multicast tree in the SP network can be used to carry traffic
belonging only to a specified set of one or more IP multicast streams
from one or more VPLSs are also described.

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

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

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

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

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


--NextPart--


From l2vpn-bounces@ietf.org  Wed Jun  4 07:27:32 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C71A428C188;
	Wed,  4 Jun 2008 07:27:32 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6142B28C108
	for <l2vpn@core3.amsl.com>; Wed,  4 Jun 2008 07:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.152
X-Spam-Level: 
X-Spam-Status: No, score=-2.152 tagged_above=-999 required=5 tests=[AWL=0.097, 
	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 5HTyvuh2lDLg for <l2vpn@core3.amsl.com>;
	Wed,  4 Jun 2008 07:27:27 -0700 (PDT)
Received: from fw.testbed.se (smtp.testbed.se [80.86.78.228])
	by core3.amsl.com (Postfix) with ESMTP id 3C48728C0FF
	for <l2vpn@ietf.org>; Wed,  4 Jun 2008 07:27:27 -0700 (PDT)
Received: from MailerDaemon by fw.testbed.se with local-bsmtp (Exim 4.63)
	(envelope-from <loa@pi.nu>) id 1K3tiM-0003V1-6t
	for l2vpn@ietf.org; Wed, 04 Jun 2008 16:11:46 +0200
Received: from pat.acreo.se ([217.151.195.214]:54405 helo=[10.4.144.171])
	by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
	(envelope-from <loa@pi.nu>)
	id 1K3tiK-0003Ul-Kl; Wed, 04 Jun 2008 16:11:44 +0200
Message-ID: <4846A28A.3050309@pi.nu>
Date: Wed, 04 Jun 2008 16:11:22 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: mpls@ietf.org, ccamp <ccamp@ops.ietf.org>, pwe3 <pwe3@ietf.org>, 
	L2VPN <l2vpn@ietf.org>
Subject: MPLS TP status
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

Dear all,

with this mail we would like to informally share with you
the status of the work on MPLS-Transport Profile within the
IETF MPLS Interoperability Design Team (MEAD Team).

The MEAD Team has worked to define a document structure
related to the agreement between ITU-T and IETF to add an
MPLS-Transport Profile within the IETF MPLS architecture.

A list of documents the Team thinks is a good enough start to form
the architectural foundation for the MPLS TP has been prepared and
editors appointed.

The current list of documents and editors can be found at:

http://www.tla-group.com/~loa/editor-doc-list.pdf

Please note that this document is a living document and changes if
and when the information changes.

It is also possible that the document structure will change as the
topics are better understood.

There is also a still pending action to define a document structure
for the OAM Procedures documents

As recommended by the JWT document (MPLS-TP_overview-22.ppt), it is
assumed that both IETF and ITU-T participants will participate as
contributing authors to the development of these documents.
Cross-participation is highly appreciated to early capture the
major input before we reaches the final processes for the documents.

A contributing author of the document contributes text and
participates in defining changes, extensions and modifications to
the existing text.

If you want to contribute to any of these documents you need to
get in contact with the editors of that document.

Note that it is up to the editor team to decide how the discussions
should be conducted (e.g. via working group mailing lists or via
dedicated lists).

Some of you have not earlier contributed to Internet Drafts or RFC,
please remember that this is an effort that will take place very
much unrelated to IETF meetings, and that IETF will progress
documents by decisions take based on traffic on wg mailing lists.

Best Regards

Loa and Italo


-- 
Loa Andersson

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


From l2vpn-bounces@ietf.org  Mon Jun 16 19:40:43 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E18B3A6969;
	Mon, 16 Jun 2008 19:40:43 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95A8A3A695B
	for <l2vpn@core3.amsl.com>; Mon, 16 Jun 2008 19:40:41 -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 cy1g1FjifwUo for <l2vpn@core3.amsl.com>;
	Mon, 16 Jun 2008 19:40:40 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 6AE113A6954
	for <l2vpn@ietf.org>; Mon, 16 Jun 2008 19:40:40 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id A097D26803D; Mon, 16 Jun 2008 20:41:23 -0600 (MDT)
Received: from pmac.castlepoint.net (71-215-92-213.hlrn.qwest.net
	[71.215.92.213]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	for l2vpn@ietf.org; Mon, 16 Jun 2008 20:41:23 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.92.213;
	client-port=1570; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <E53EA089-164B-435B-B95C-0D9780CC67DA@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 v924)
Subject: IETF 72: Call for slots for Dublin, Ireland
Date: Mon, 16 Jun 2008 20:41:05 -0600
X-Mailer: Apple Mail (2.924)
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

Hi,

We've been tentatively scheduled for a 2 hour slot on Monday  
afternoon, 7/28, 1520-1720 in Dublin.  Please e-mail the chairs if you  
have an item you wish to present.

Also, see here for Important Dates for IETF 72:
http://www.ietf.org/meetings/72/72-cutoff_dates.html

Thanks!

-shane & Vach


From l2vpn-bounces@ietf.org  Thu Jun 26 17:21:12 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3742D3A6A6D;
	Thu, 26 Jun 2008 17:21:12 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41BE53A6A5C;
	Thu, 26 Jun 2008 17:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.392
X-Spam-Level: 
X-Spam-Status: No, score=-3.392 tagged_above=-999 required=5
	tests=[AWL=-0.793, 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 F+liVTQZN-Xu; Thu, 26 Jun 2008 17:21:05 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [61.144.161.54])
	by core3.amsl.com (Postfix) with ESMTP id 29C323A6A4C;
	Thu, 26 Jun 2008 17:21:05 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K3100LNFTU4TC@szxga02-in.huawei.com>; Thu,
	26 Jun 2008 10:34:52 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K3100HO8TU4B0@szxga02-in.huawei.com>; Thu,
	26 Jun 2008 10:34:52 +0800 (CST)
Received: from j59929 ([10.70.77.136])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K31007C3TU4FL@szxml03-in.huawei.com>; Thu,
	26 Jun 2008 10:34:52 +0800 (CST)
Date: Thu, 26 Jun 2008 10:34:52 +0800
From: Jiang Yuan-long <yljiang@huawei.com>
Subject: Optimized MAC Address Operations in VPLS with Redundancy
To: l2vpn@ietf.org
Message-id: <009001c8d735$362c71a0$884d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: multipart/alternative;
	boundary="Boundary_(ID_UACNGQVAHHFO65Lq1S8iVA)"
X-Priority: 3
X-MSMail-priority: Normal
Cc: pwe3@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

This is a multi-part message in MIME format.

--Boundary_(ID_UACNGQVAHHFO65Lq1S8iVA)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi, all:

In VPLS with redundancy scenarios such as defined in draft-ietf-pwe3-redundancy-00.txt 
or in draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt, MAC address withdrawal mechanism 
is introduced in RFC 4762 for faster convergence. 

In progress work of draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt enhances the mechanism 
by flushing only the affected MAC addresses. This method may greatly restrict the scope
of MAC flushing under some circumstances. That's really a good job.

But in VPLS with redundancy, as the relation of the working PW and the protection PW is
determined in advance, flushing is not the best choice. So this draft provides two 
mechanisms: MAC address switching and MAC address notification. With these two 
mechanisms  MAC address flushing can be removed completely.

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


        Title : Optimized MAC Address Operations in VPLS with Redundancy 
        Author(s) : Y. Jiang, Y. Yang 
        Filename : draft-jiang-l2vpn-vpls-mac-operation-00.txt 
        Pages : 16 
        Date : 2008-6-24 
        
   The Virtual Private LAN Service (VPLS) Using Label Distribution     
   Protocol (LDP) Signaling is described in RFC 4762. That document   
   describes a mechanism called MAC Address Withdrawal to remove or     
   unlearn MAC addresses which have been dynamically learned in a VPLS   
   instance. Further work in progress defines an extension to MAC 
   Address Withdrawal procedure which can greatly restrict the scope of 
   MAC flushing. This document provides two mechanisms which completely 
   remove the need for MAC address flushing in VPLS instances. The 
   mechanisms are MAC address switching and MAC address notification.     

A URL for this Internet-Draft is: 
http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-mac-operation-00.txt

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

Please comment on the idea.

Regards,

Y.L. Jiang

--Boundary_(ID_UACNGQVAHHFO65Lq1S8iVA)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=gb2312">
<META content="MSHTML 6.00.2900.3314" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial>Hi, all:</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>In VPLS with redundancy scenarios such as defined in 
draft-ietf-pwe3-redundancy-00.txt </FONT></DIV>
<DIV><FONT face=Arial>or in draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt, MAC 
address withdrawal mechanism </FONT></DIV>
<DIV><FONT face=Arial>is introduced in RFC 4762 for faster convergence. 
</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>In progress work of 
draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt enhances the mechanism </FONT></DIV>
<DIV><FONT face=Arial>by flushing only the affected MAC addresses. This method 
may greatly restrict the scope</FONT></DIV>
<DIV><FONT face=Arial>of MAC flushing under some circumstances. 
That's&nbsp;really a good job.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>But in VPLS with redundancy,&nbsp;as the relation of the 
working PW and the protection PW is</FONT></DIV>
<DIV><FONT face=Arial>determined in advance, flushing is not the best choice. So 
this draft provides two </FONT></DIV>
<DIV><FONT face=Arial>mechanisms: MAC address switching and MAC address 
notification. With these two </FONT></DIV>
<DIV><FONT face=Arial>mechanisms&nbsp; MAC address flushing&nbsp;can be removed 
completely.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>-&gt;</FONT></DIV>
<DIV><FONT size=2><FONT face=Arial size=3>A New Internet-Draft is available from 
the on-line Internet-Drafts <BR>directories. <BR><BR><BR>&nbsp; &nbsp; &nbsp; 
&nbsp; Title : Optimized MAC Address Operations in VPLS with Redundancy 
<BR>&nbsp; &nbsp; &nbsp; &nbsp; Author(s) : Y. Jiang, Y. Yang <BR>&nbsp; &nbsp; 
&nbsp; &nbsp; Filename : draft-jiang-l2vpn-vpls-mac-operation-00.txt <BR>&nbsp; 
&nbsp; &nbsp; &nbsp; Pages : 16 <BR>&nbsp; &nbsp; &nbsp; &nbsp; Date : 2008-6-24 
<BR>&nbsp; &nbsp; &nbsp; &nbsp; <BR>&nbsp;&nbsp; The Virtual Private LAN Service 
(VPLS) Using Label Distribution &nbsp; &nbsp; <BR>&nbsp; &nbsp;Protocol (LDP) 
Signaling is described in RFC 4762. That document &nbsp; <BR>&nbsp; 
&nbsp;describes a mechanism called MAC Address Withdrawal to remove or &nbsp; 
&nbsp; <BR>&nbsp; &nbsp;unlearn MAC addresses which have been dynamically 
learned in a VPLS &nbsp; <BR>&nbsp;&nbsp; instance. Further work in progress 
defines an extension to MAC <BR>&nbsp; &nbsp;Address Withdrawal procedure which 
can greatly restrict the scope of <BR>&nbsp; &nbsp;MAC flushing. This document 
provides two mechanisms which completely <BR>&nbsp; &nbsp;remove the need for 
MAC address flushing in VPLS instances. The <BR>&nbsp; &nbsp;mechanisms are MAC 
address switching and MAC address notification. &nbsp; &nbsp; <BR><BR>A URL for 
this Internet-Draft is: <BR></FONT><A 
href="http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-mac-operation-00.txt" 
target=_top rel=nofollow><FONT face=Arial 
size=3>http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-mac-operation-00.txt</FONT></A><BR><BR><FONT 
face=Arial><FONT size=3>Internet-Drafts are also available by anonymous FTP at: 
<BR>ftp://ftp.ietf.org/internet-drafts/ </FONT><BR>-&gt;</FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial></FONT>&nbsp;</DIV></FONT>
<DIV><FONT face=Arial>Please comment on the idea.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>Regards,</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>Y.L. Jiang</FONT></DIV></BODY></HTML>

--Boundary_(ID_UACNGQVAHHFO65Lq1S8iVA)--


From l2vpn-bounces@ietf.org  Sat Jun 28 06:49:54 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B25D3A6A78;
	Sat, 28 Jun 2008 06:49:54 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7DAFA3A6A78
	for <l2vpn@core3.amsl.com>; Sat, 28 Jun 2008 06:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.802
X-Spam-Level: ***
X-Spam-Status: No, score=3.802 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, SARE_ADLTSUB2=1.23,
	SARE_ADULT2=1.42, SARE_CHILDPRN1=1.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 NJh93lpE16ZA for <l2vpn@core3.amsl.com>;
	Sat, 28 Jun 2008 06:49:52 -0700 (PDT)
Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.247])
	by core3.amsl.com (Postfix) with ESMTP id 8FB853A6A68
	for <l2vpn@ietf.org>; Sat, 28 Jun 2008 06:49:52 -0700 (PDT)
Received: by ag-out-0708.google.com with SMTP id 26so4081846agb.12
	for <l2vpn@ietf.org>; Sat, 28 Jun 2008 06:49:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:mime-version:content-type;
	bh=SN49sdRlQRXh/UT1T8c3oJbOtbCDSycMzDIQrYDR9FI=;
	b=XDcSMTDy+tOrXWsPMrMkVTP0FtJoqPGbx6zjlDHXrwkgRDziWVkU74RCSUoK48naYr
	2wDY23mc4sGHzWMKImDneMCguLWFebWA93qG4vgsKuag2SAWppJeZ6800zDyB/xyPDC+
	+CF1ZA4SsbstxnO8lyhwoFA7gH3MowRkXvZn8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=eb9H/EOVllfghg83elIIBYqcJTVagY5fqpga+eGfSGNq6RxhykHWv2d8mH53LZ7+PS
	CbsuqXCSD5UQzCFExi4ZznB4oeB0ApKqDzyp9OCK42FcnslbKvcgZlJI873WY7TmKs0d
	POwnv3A/TgHDEP0O5V6ay+nWH7r7PZ1R1Alk0=
Received: by 10.70.45.11 with SMTP id s11mr3080362wxs.18.1214660997231;
	Sat, 28 Jun 2008 06:49:57 -0700 (PDT)
Received: by 10.70.30.20 with HTTP; Sat, 28 Jun 2008 06:49:56 -0700 (PDT)
Message-ID: <2ec60bcc0806280649i36701249p5101a1aec08c119e@mail.gmail.com>
Date: Sat, 28 Jun 2008 17:49:56 +0400
From: "homerbruce571 homerbruce571" <homerbruce571@gmail.com>
To: l2vpn@ietf.org
Subject: preteen pre teen model child porn underage porn underage nudity kids
	naked preteen nudes preteen boys naked kids underage girls
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_11460_24432538.1214660996820"
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

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

http://adultsexkey.com/petite-kids-showing-pussy.avi
http://adultsexkey.com/best-arhives-about-child-porno.avi
http://adultsexkey.com/exclusive-hot-kdz-porn-sites.avi
http://adultsexkey.com/only-very-hq-and-exclusive-cp.avi
http://adultsexkey.com/blond-lolitas-cutie-in-cp-action.avi

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

<a href="http://adultsexkey.com/petite-kids-showing-pussy.avi">http://adultsexkey.com/petite-kids-showing-pussy.avi</a><br><a href="http://adultsexkey.com/best-arhives-about-child-porno.avi">http://adultsexkey.com/best-arhives-about-child-porno.avi</a><br>
<a href="http://adultsexkey.com/exclusive-hot-kdz-porn-sites.avi">http://adultsexkey.com/exclusive-hot-kdz-porn-sites.avi</a><br><a href="http://adultsexkey.com/only-very-hq-and-exclusive-cp.avi">http://adultsexkey.com/only-very-hq-and-exclusive-cp.avi</a><br>
<a href="http://adultsexkey.com/blond-lolitas-cutie-in-cp-action.avi">http://adultsexkey.com/blond-lolitas-cutie-in-cp-action.avi</a><br><br><br>

------=_Part_11460_24432538.1214660996820--


From l2vpn-bounces@ietf.org  Sun Jun 29 09:56:38 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD3D53A68FD;
	Sun, 29 Jun 2008 09:56:38 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1E423A6881;
	Sun, 29 Jun 2008 09:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.116
X-Spam-Level: 
X-Spam-Status: No, score=-1.116 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482,
	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 Lm-C7AzFtaFt; Sun, 29 Jun 2008 09:56:36 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 1CCF23A689C;
	Sun, 29 Jun 2008 09:56:35 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 3DC552684E7; Sun, 29 Jun 2008 10:56:43 -0600 (MDT)
Received: from pmac.castlepoint.net (71-215-92-34.hlrn.qwest.net
	[71.215.92.34]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Sun, 29 Jun 2008 10:56:42 -0600 (MDT)
	(envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.92.34;
	client-port=3477; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS
	10.4.8; data-bytes=0
Message-Id: <DFBCAD0B-A9A5-4E62-B81C-9DEC89CEF443@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: Jiang Yuan-long <yljiang@huawei.com>
In-Reply-To: <009001c8d735$362c71a0$884d460a@china.huawei.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-5-228186289
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: [PWE3] Optimized MAC Address Operations in VPLS with Redundancy
X-Priority: 3
Date: Sun, 29 Jun 2008 10:56:27 -0600
References: <009001c8d735$362c71a0$884d460a@china.huawei.com>
X-Mailer: Apple Mail (2.924)
Cc: l2vpn@ietf.org, pwe3@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org


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

Hi Jiang,

I have a few questions about this draft.

First, "MAC Address Switching" (first explained in Section 3.1).   
Please see the following diagram where I've added CE-5 as a single- 
homed device behind PE-1:

                             PE-1                       PE-3
                           +--------+                +--------+
               CE-5--------|        |                |        |
                           |   --   |           PW1  |   --   | CE-3
                           |  /  \  |----------------|  /  \  |--->
CE-1               /------|  \ s/  |           PW2  |  \S /  |
   \     primary spoke PW  |   --   |         /------|   --   |
    \             /        +--------+        /       +--------+
     \    (MTU-s)/              |    \      /             |
      +--------+/               |     \    /              |
      |        |                |      \  /               |
      |   --   |                |       \/                |
      |  /  \  |             PW5|   H-VPLS Full Mesh Core |
      |  \S /  |                |      /  \               |
      |   --   |                |     /    \              |
     /+--------+\               |    /      \             |
    /     backup spoke PW       |   /        \   PW3      |
   /              \        +--------+         \------+--------+
  CE-2             \       |        |                |        |
                    \------|  --    |            PW4 |  --    | CE-4
                           | /  \   |----------------| /  \   |--->
                           | \s /   |                | \S /   |
                           |  --    |                |  --    |
                           +--------+                +--------+
                             PE-2                       PE-4

Section 3.1 states the following:
---snip---
    ... PE-1 or PE-2 sends out a ''MAC Address Switching'' message to  
PE-3,
    and accordingly PE-3 changes its MAC table items with PW1 as the  
outgoing
    PW, to show PW2 as the outgoing PW. In this way, remote VPLS peer
    node PE-3 needs no MAC flushing and re- learning, and faster  
convergence
    is realized.
---snip---

In no particular order, here are some questions & comments:
1)  First, just to be more clear, I think you likely need to point out  
that, because CE-5 is single-homed into PE-1, that the "MAC Address  
Switching" message (sent to the other PE's) must only contain MAC  
Addresses learned from the "primary spoke PW" going from PE-1 to the  
MTU-s, (not from other AC's attached to PE-1).
2)  Second, shouldn't PE-1 & PE-2 send a "MAC Address Switching"  
message to all other PE's in the H-VPLS instance?  In this case, PE-1  
& PE-2 should be required to send a "MAC Address Switching" message to  
PE-2, PE-3 & PE-4.  This way, PE-3 will switch from PW1 to PW2.  In  
addition, PE-4 will switch from PW3 to PW4.  Finally, PE-2 must also  
switch from PW5 to the "backup spoke PW" in order to reach the MTU-s.   
(Alternatively, PE-1 should at least tell PE-2 to no longer forward  
MAC addresses for the MTU-s down PW5).
3)  I'm not sure how PE-1 would signal to PE-2 the 'PW-ID' of the  
"backup spoke PW", from PE-2 to the MTU-s, in the MAC Address  
Switching Message you have in Section 5.2.  Perhaps I haven't studied  
draft-ietf-pw-redundancy enough, but from where does PE-1 learn/know  
the PW-ID of the "backup spoke PW" from PE-2 down to the MTU-s, in the  
first place?


Second, "MAC Address Notification" (first explained in Section 3.2).

Section 3.2 of this draft states the following:
---snip---
    To facilitate MAC table maintenance on PE-2, the MAC Address  
Notification messages
    should include the outgoing PWs to be associated with the notified  
MAC addresses.
    Multiple PWs and their associated MAC addresses may be carried in  
a single message
    or in separate messages.
---snip---

I'm not sure how you're intending to "include the outgoing PW's to be  
associated with the notified MAC addresses".  Specifically, in my  
understanding of a FEC 129 PW-ID element, both the SAII and TAII are  
null, according to RFC 4762, Section 7.1.1:
---snip---
    Target Attachment Individual Identifier (TAII), Source Attachment  
Individual
    Identifier (SAII): These are null because the mesh of PWs in a  
VPLS terminates
    on MAC learning tables, rather than on individual attachment  
circuits. The use
    of non-null TAII and SAII is reserved for future enhancements.
---snip---
Instead, you only have an AGI in FEC 129, which I don't believe is  
enough to indicate the specific PW over which the MAC addresses were  
learned from remote PE's.  But, perhaps I'm incorrect?

Thanks,

-shane


On Jun 25, 2008, at 8:34 PM, Jiang Yuan-long wrote:
> Hi, all:
>
> In VPLS with redundancy scenarios such as defined in draft-ietf-pwe3- 
> redundancy-00.txt
> or in draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt, MAC address  
> withdrawal mechanism
> is introduced in RFC 4762 for faster convergence.
>
> In progress work of draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt  
> enhances the mechanism
> by flushing only the affected MAC addresses. This method may greatly  
> restrict the scope
> of MAC flushing under some circumstances. That's really a good job.
>
> But in VPLS with redundancy, as the relation of the working PW and  
> the protection PW is
> determined in advance, flushing is not the best choice. So this  
> draft provides two
> mechanisms: MAC address switching and MAC address notification. With  
> these two
> mechanisms  MAC address flushing can be removed completely.
>
> ->
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title : Optimized MAC Address Operations in VPLS with  
> Redundancy
>         Author(s) : Y. Jiang, Y. Yang
>         Filename : draft-jiang-l2vpn-vpls-mac-operation-00.txt
>         Pages : 16
>         Date : 2008-6-24
>
>    The Virtual Private LAN Service (VPLS) Using Label Distribution
>    Protocol (LDP) Signaling is described in RFC 4762. That document
>    describes a mechanism called MAC Address Withdrawal to remove or
>    unlearn MAC addresses which have been dynamically learned in a VPLS
>    instance. Further work in progress defines an extension to MAC
>    Address Withdrawal procedure which can greatly restrict the scope  
> of
>    MAC flushing. This document provides two mechanisms which  
> completely
>    remove the need for MAC address flushing in VPLS instances. The
>    mechanisms are MAC address switching and MAC address notification.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-mac-operation-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> ->
>
> Please comment on the idea.
>
> Regards,
>
> Y.L. Jiang
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3


--Apple-Mail-5-228186289
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi Jiang,<div><br></div><div>I =
have a few questions about this draft. =
&nbsp;</div><div><br></div><div>First, "MAC Address Switching" (first =
explained in Section 3.1). &nbsp;Please see the following diagram where =
I've added CE-5 as a single-homed device behind =
PE-1:</div><div><br></div><div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;PE-1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; PE-3 &nbsp; &nbsp; &nbsp; =
&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;+--------+ &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;+--------+ &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;CE-5--------| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; -- &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; PW1 &nbsp;| &nbsp; -- &nbsp; | CE-3 =
&nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;/ &nbsp;\ =
&nbsp;|----------------| &nbsp;/ &nbsp;\ &nbsp;|---> =
&nbsp;&nbsp;</div><div>CE-1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; /------| &nbsp;\ s/ &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
PW2 &nbsp;| &nbsp;\S / &nbsp;| &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp;\ &nbsp; &nbsp; primary spoke PW =
&nbsp;| &nbsp; -- &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; /------| &nbsp; =
-- &nbsp; | &nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; \ &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; / &nbsp; &nbsp; &nbsp; &nbsp;+--------+ =
&nbsp; &nbsp; &nbsp; &nbsp;/ &nbsp; &nbsp; &nbsp; +--------+ &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp;\ &nbsp; &nbsp;(MTU-s)/ &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;\ &nbsp; &nbsp; =
&nbsp;/ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; +--------+/ &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; \ &nbsp; &nbsp;/ =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; =
&nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp; &nbsp;\ &nbsp;/ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
| &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; | =
&nbsp; -- &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;| &nbsp; &nbsp; &nbsp; \/ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; | &nbsp;/ &nbsp;\ &nbsp;| =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; PW5| &nbsp; H-VPLS Full Mesh =
Core | &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; | =
&nbsp;\S / &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;| &nbsp; &nbsp; &nbsp;/ &nbsp;\ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; =
&nbsp; | &nbsp; -- &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;| &nbsp; &nbsp; / &nbsp; &nbsp;\ &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp;/+--------+\ &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;/ &nbsp; &nbsp; =
&nbsp;\ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; / &nbsp; &nbsp; backup spoke PW =
&nbsp; &nbsp; &nbsp; | &nbsp; / &nbsp; &nbsp; &nbsp; &nbsp;\ &nbsp; PW3 =
&nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp;/ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;\ &nbsp; &nbsp; &nbsp; &nbsp;+--------+ &nbsp; &nbsp; =
&nbsp; &nbsp; \------+--------+ &nbsp; &nbsp;&nbsp;</div><div>&nbsp;CE-2 =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; \ &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; \------| &nbsp;-- &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;PW4 | &nbsp;-- &nbsp; &nbsp;| CE-4 &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| / &nbsp;\ &nbsp; =
|----------------| / &nbsp;\ &nbsp; |---> =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| \s / &nbsp; | &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| \S / &nbsp; | &nbsp; =
&nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;-- &nbsp; =
&nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| =
&nbsp;-- &nbsp; &nbsp;| &nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;+--------+ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;+--------+ &nbsp; &nbsp;&nbsp;</div><div>&nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;PE-2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; PE-4&nbsp;</div><div>&nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div><div>Section 3.1 states =
the following:</div><div>---snip---</div><div>&nbsp;&nbsp; ... PE-1 or =
PE-2 sends out a ''MAC Address Switching''=20
   message to PE-3,</div><div>&nbsp;&nbsp; and accordingly PE-3 changes =
its MAC table items=20
   with PW1 as the outgoing</div><div>&nbsp;&nbsp; PW, to show PW2 as =
the outgoing PW. In this=20
   way, remote VPLS peer</div><div>&nbsp;&nbsp; node PE-3 needs no MAC =
flushing and re-
   learning, and faster convergence</div><div>&nbsp;&nbsp; is =
realized.</div><div>---snip---</div><div><br></div><div>In no particular =
order, here are some questions &amp; comments:</div><div>1) &nbsp;First, =
just to be more clear, I think you likely need to point out that, =
because CE-5 is single-homed into PE-1, that the "MAC Address Switching" =
message (sent to the other PE's) must only contain MAC Addresses learned =
from the "primary spoke PW" going from PE-1 to the MTU-s, (not from =
other AC's attached to PE-1).</div><div>2) &nbsp;Second, shouldn't PE-1 =
&amp; PE-2 send a "MAC Address Switching" message to all other PE's in =
the H-VPLS instance? &nbsp;In this case, PE-1 &amp; PE-2 should be =
required to send a "MAC Address Switching" message to PE-2, PE-3 &amp; =
PE-4. &nbsp;This way, PE-3 will switch from PW1 to PW2. &nbsp;In =
addition, PE-4 will switch from PW3 to PW4. &nbsp;Finally, PE-2 must =
also switch from PW5 to the "backup spoke PW" in order to reach the =
MTU-s. &nbsp;(Alternatively, PE-1 should at least tell PE-2 to no longer =
forward MAC addresses for the MTU-s down PW5).</div><div>3) &nbsp;I'm =
not sure how PE-1 would signal to PE-2 the 'PW-ID' of the "backup spoke =
PW", from PE-2 to the MTU-s, in the MAC Address Switching Message you =
have in Section 5.2. &nbsp;Perhaps I haven't studied =
draft-ietf-pw-redundancy enough, but from where does PE-1 learn/know the =
PW-ID of the "backup spoke PW" from PE-2 down to the MTU-s, in the first =
place?</div><div><br></div><div><br></div><div>Second, "MAC Address =
Notification" (first explained in Section =
3.2).</div><div><br></div><div>Section 3.2 of this draft states the =
following:</div><div>---snip---</div><div>&nbsp;&nbsp; To facilitate MAC =
table maintenance on PE-2, the MAC Address=20
   Notification messages</div><div>&nbsp;&nbsp; should include the =
outgoing PWs to be=20
   associated with the notified MAC addresses.</div><div>&nbsp;&nbsp; =
Multiple PWs and their=20
   associated MAC addresses may be carried in a single =
message</div><div>&nbsp;&nbsp; or in=20
   separate =
messages.&nbsp;</div><div>---snip---</div><div><br></div><div>I'm not =
sure how you're intending to "include the outgoing PW's to be associated =
with the notified MAC addresses". &nbsp;Specifically, in my =
understanding of a FEC 129 PW-ID element, both the SAII and TAII are =
null, according to RFC 4762, Section =
7.1.1:</div><div>---snip---</div><div>&nbsp;&nbsp; Target Attachment =
Individual Identifier (TAII), Source Attachment
   Individual</div><div>&nbsp;&nbsp; Identifier (SAII): These are null =
because the mesh of PWs
   in a VPLS terminates</div><div>&nbsp;&nbsp; on MAC learning tables, =
rather than on
   individual attachment circuits.  The use</div><div>&nbsp;&nbsp; of =
non-null TAII and SAII is
   reserved for future =
enhancements.</div><div>---snip---</div><div>Instead, you only have an =
AGI in FEC 129, which I don't believe is enough to indicate the specific =
PW over which the MAC addresses were learned from remote PE's. =
&nbsp;But, perhaps I'm =
incorrect?</div><div><br></div><div>Thanks,</div><div><br></div><div>-shan=
e</div><div><pre></pre><br></div><div><br></div><div><pre><span =
class=3D"Apple-style-span" style=3D"white-space: normal; ">On Jun 25, =
2008, at 8:34 PM, Jiang Yuan-long =
wrote:</span></pre></div></div><div><div><blockquote type=3D"cite"><div =
bgcolor=3D"#ffffff"><div>Hi, all:</div><div>&nbsp;</div><div>In VPLS =
with redundancy scenarios such as defined in =
draft-ietf-pwe3-redundancy-00.txt</div><div>or in =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt, MAC address withdrawal =
mechanism</div><div>is introduced in RFC 4762 for faster =
convergence.</div><div>&nbsp;</div><div>In progress work of =
draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt enhances the =
mechanism</div><div>by flushing only the affected MAC addresses. This =
method may greatly restrict the scope</div><div>of MAC flushing under =
some circumstances. That's&nbsp;really a good =
job.</div><div>&nbsp;</div><div>But in VPLS with redundancy,&nbsp;as the =
relation of the working PW and the protection PW is</div><div>determined =
in advance, flushing is not the best choice. So this draft provides =
two</div><div>mechanisms: MAC address switching and MAC address =
notification. With these two</div><div>mechanisms&nbsp; MAC address =
flushing&nbsp;can be removed =
completely.</div><div>&nbsp;</div><div>-></div><div>A New Internet-Draft =
is available from the on-line =
Internet-Drafts&nbsp;<br>directories.&nbsp;<br><br><br>&nbsp; &nbsp; =
&nbsp; &nbsp; Title : Optimized MAC Address Operations in VPLS with =
Redundancy&nbsp;<br>&nbsp; &nbsp; &nbsp; &nbsp; Author(s) : Y. Jiang, Y. =
Yang&nbsp;<br>&nbsp; &nbsp; &nbsp; &nbsp; Filename : =
draft-jiang-l2vpn-vpls-mac-operation-00.txt&nbsp;<br>&nbsp; &nbsp; =
&nbsp; &nbsp; Pages : 16&nbsp;<br>&nbsp; &nbsp; &nbsp; &nbsp; Date : =
2008-6-24&nbsp;<br>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br>&nbsp;&nbsp; The =
Virtual Private LAN Service (VPLS) Using Label Distribution &nbsp; =
&nbsp;&nbsp;<br>&nbsp; &nbsp;Protocol (LDP) Signaling is described in =
RFC 4762. That document &nbsp;&nbsp;<br>&nbsp; &nbsp;describes a =
mechanism called MAC Address Withdrawal to remove or &nbsp; =
&nbsp;&nbsp;<br>&nbsp; &nbsp;unlearn MAC addresses which have been =
dynamically learned in a VPLS &nbsp;&nbsp;<br>&nbsp;&nbsp; instance. =
Further work in progress defines an extension to MAC&nbsp;<br>&nbsp; =
&nbsp;Address Withdrawal procedure which can greatly restrict the scope =
of&nbsp;<br>&nbsp; &nbsp;MAC flushing. This document provides two =
mechanisms which completely&nbsp;<br>&nbsp; &nbsp;remove the need for =
MAC address flushing in VPLS instances. The&nbsp;<br>&nbsp; =
&nbsp;mechanisms are MAC address switching and MAC address notification. =
&nbsp; &nbsp;&nbsp;<br><br>A URL for this Internet-Draft is:&nbsp;<br><a =
href=3D"http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-mac-ope=
ration-00.txt">http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-=
mac-operation-00.txt</a><br><br>Internet-Drafts are also available by =
anonymous FTP =
at:&nbsp;<br>ftp://ftp.ietf.org/internet-drafts/&nbsp;<br>-></div><div>&nb=
sp;</div><div>Please comment on the =
idea.</div><div>&nbsp;</div><div>Regards,</div><div>&nbsp;</div><div>Y.L. =
Jiang</div>_______________________________________________<br>pwe3 =
mailing list<br><a =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/pwe3<br></div></blockquote></div><br></div></body></html>=

--Apple-Mail-5-228186289--


From l2vpn-bounces@ietf.org  Sun Jun 29 23:18:05 2008
Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 23B303A68C2;
	Sun, 29 Jun 2008 23:18:05 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 563EE3A6928;
	Sun, 29 Jun 2008 23:18:04 -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 Y0vsXo8mOmAo; Sun, 29 Jun 2008 23:18:03 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id 1533E3A68C2;
	Sun, 29 Jun 2008 23:18:03 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K39002TWIUEZR@usaga01-in.huawei.com>; Sun,
	29 Jun 2008 23:18:14 -0700 (PDT)
Received: from huawei.com ([172.17.1.31])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K39005P3IUCRS@usaga01-in.huawei.com>; Sun,
	29 Jun 2008 23:18:14 -0700 (PDT)
Received: from [172.24.1.18] (Forwarded-For: [10.70.77.136])
	by szxmc03-in.huawei.com (mshttpd); Mon, 30 Jun 2008 14:18:02 +0800
Date: Mon, 30 Jun 2008 14:18:02 +0800
From: jiangyuanlong 59929 <yljiang@huawei.com>
Subject: Re: [PWE3] Optimized MAC Address Operations in VPLS with Redundancy
In-reply-to: <DFBCAD0B-A9A5-4E62-B81C-9DEC89CEF443@castlepoint.net>
To: Shane Amante <shane@castlepoint.net>
Message-id: <f9f6a11e23cf.23cff9f6a11e@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
References: <009001c8d735$362c71a0$884d460a@china.huawei.com>
	<DFBCAD0B-A9A5-4E62-B81C-9DEC89CEF443@castlepoint.net>
Cc: l2vpn@ietf.org, pwe3@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>,
	<mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

Shane: 
Thanks for your comments, please see my replies corresponding to the questions.


Best regards,
Jiang

----- Original Message -----
From: Shane Amante <shane@castlepoint.net>
Date: Monday, June 30, 2008 0:56 am
Subject: Re: [PWE3] Optimized MAC Address Operations in VPLS with Redundancy

> Hi Jiang,
> 
> I have a few questions about this draft.
> 
> First, "MAC Address Switching" (first explained in Section 3.1).   
> Please see the following diagram where I've added CE-5 as a single-
> 
> homed device behind PE-1:
> 
>                             PE-1                       PE-3
>                           +--------+                +--------+
>               CE-5--------|        |                |        |
>                           |   --   |           PW1  |   --   | CE-3
>                           |  /  \  |----------------|  /  \  |--->
> CE-1               /------|  \ s/  |           PW2  |  \S /  |
>   \     primary spoke PW  |   --   |         /------|   --   |
>    \             /        +--------+        /       +--------+
>     \    (MTU-s)/              |    \      /             |
>      +--------+/               |     \    /              |
>      |        |                |      \  /               |
>      |   --   |                |       \/                |
>      |  /  \  |             PW5|   H-VPLS Full Mesh Core |
>      |  \S /  |                |      /  \               |
>      |   --   |                |     /    \              |
>     /+--------+\               |    /      \             |
>    /     backup spoke PW       |   /        \   PW3      |
>   /              \        +--------+         \------+--------+
>  CE-2             \       |        |                |        |
>                    \------|  --    |            PW4 |  --    | CE-4
>                           | /  \   |----------------| /  \   |--->
>                           | \s /   |                | \S /   |
>                           |  --    |                |  --    |
>                           +--------+                +--------+
>                             PE-2                       PE-4
> 
> Section 3.1 states the following:
> ---snip---
>    ... PE-1 or PE-2 sends out a ''MAC Address Switching'' message 
> to  
> PE-3,
>    and accordingly PE-3 changes its MAC table items with PW1 as 
> the  
> outgoing
>    PW, to show PW2 as the outgoing PW. In this way, remote VPLS peer
>    node PE-3 needs no MAC flushing and re- learning, and faster  
> convergence
>    is realized.
> ---snip---
> 
> In no particular order, here are some questions & comments:
> 1)  First, just to be more clear, I think you likely need to point 
> out  
> that, because CE-5 is single-homed into PE-1, that the "MAC 
> Address  
> Switching" message (sent to the other PE's) must only contain MAC  
> Addresses learned from the "primary spoke PW" going from PE-1 to 
> the  
> MTU-s, (not from other AC's attached to PE-1).

Yes, you are right for this kind of mixed scenario, and that is the reason for the inclusion of MAC list.
I will clearly point it out in the next version.

> 2)  Second, shouldn't PE-1 & PE-2 send a "MAC Address Switching"  
> message to all other PE's in the H-VPLS instance?  In this case, 
> PE-1  
> & PE-2 should be required to send a "MAC Address Switching" 
> message to  
> PE-2, PE-3 & PE-4.  This way, PE-3 will switch from PW1 to PW2.  
> In  
> addition, PE-4 will switch from PW3 to PW4.  Finally, PE-2 must 
> also  
> switch from PW5 to the "backup spoke PW" in order to reach the MTU-
> s.   
> (Alternatively, PE-1 should at least tell PE-2 to no longer 
> forward  
> MAC addresses for the MTU-s down PW5).

Yes, you are right. I take PW1 as an example, but the same mechanism applies to the other working PWs effected by the topology change such as PW3. Perhaps I should add some more paraphrases in this section.
But for PW5, I think PE-1 & PE-2 should deal with it locally and no signaling of switching is needed. As for PE-1, PW5 is protecting the "primary spoke PW", and for PE-2, PW5 is protected by the "backup spoke PW". Therefore, PE-1 should switch from the "primary spoke PW" to PW5, while PE-2 should switch from PW5 to the "backup spoke PW". 


> 3)  I'm not sure how PE-1 would signal to PE-2 the 'PW-ID' of the  
> "backup spoke PW", from PE-2 to the MTU-s, in the MAC Address  
> Switching Message you have in Section 5.2.  Perhaps I haven't 
> studied  
> draft-ietf-pw-redundancy enough, but from where does PE-1 
> learn/know  
> the PW-ID of the "backup spoke PW" from PE-2 down to the MTU-s, in 
> the  
> first place?
> 

Please reference my comments in 2), there is no needs for PE-1 to signal to PE-2 the "PW-ID" of the "backup spoke PW".

> 
> Second, "MAC Address Notification" (first explained in Section 3.2).
> 
> Section 3.2 of this draft states the following:
> ---snip---
>    To facilitate MAC table maintenance on PE-2, the MAC Address  
> Notification messages
>    should include the outgoing PWs to be associated with the 
> notified  
> MAC addresses.
>    Multiple PWs and their associated MAC addresses may be carried 
> in  
> a single message
>    or in separate messages.
> ---snip---
> 
> I'm not sure how you're intending to "include the outgoing PW's to 
> be  
> associated with the notified MAC addresses".  Specifically, in my  
> understanding of a FEC 129 PW-ID element, both the SAII and TAII 
> are  
> null, according to RFC 4762, Section 7.1.1:
> ---snip---
>    Target Attachment Individual Identifier (TAII), Source 
> Attachment  
> Individual
>    Identifier (SAII): These are null because the mesh of PWs in a 
> 
> VPLS terminates
>    on MAC learning tables, rather than on individual attachment  
> circuits. The use
>    of non-null TAII and SAII is reserved for future enhancements.
> ---snip---
> Instead, you only have an AGI in FEC 129, which I don't believe is 
> 
> enough to indicate the specific PW over which the MAC addresses 
> were  
> learned from remote PE's.  But, perhaps I'm incorrect?
> 

This seems a problem, maybe we can send the IP address or the LSR-ID of the PW endpoint instead. Any other sugestions?
BTW, I'm not sure about the backgrouds of the decision on nulling the SAII and TAII fields,
but it seems to me this decision makes it a little difficult to implement end to end PW protection and muti-segment PW.

> Thanks,
> 
> -shane
> 
> 
> On Jun 25, 2008, at 8:34 PM, Jiang Yuan-long wrote:
> > Hi, all:
> >
> > In VPLS with redundancy scenarios such as defined in draft-ietf-
> pwe3- 
> > redundancy-00.txt
> > or in draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt, MAC address  
> > withdrawal mechanism
> > is introduced in RFC 4762 for faster convergence.
> >
> > In progress work of draft-pdutta-l2vpn-vpls-ldp-mac-opt-03.txt  
> > enhances the mechanism
> > by flushing only the affected MAC addresses. This method may 
> greatly  
> > restrict the scope
> > of MAC flushing under some circumstances. That's really a good job.
> >
> > But in VPLS with redundancy, as the relation of the working PW 
> and  
> > the protection PW is
> > determined in advance, flushing is not the best choice. So this  
> > draft provides two
> > mechanisms: MAC address switching and MAC address notification. 
> With  
> > these two
> > mechanisms  MAC address flushing can be removed completely.
> >
> > ->
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> >         Title : Optimized MAC Address Operations in VPLS with  
> > Redundancy
> >         Author(s) : Y. Jiang, Y. Yang
> >         Filename : draft-jiang-l2vpn-vpls-mac-operation-00.txt
> >         Pages : 16
> >         Date : 2008-6-24
> >
> >    The Virtual Private LAN Service (VPLS) Using Label Distribution
> >    Protocol (LDP) Signaling is described in RFC 4762. That document
> >    describes a mechanism called MAC Address Withdrawal to remove or
> >    unlearn MAC addresses which have been dynamically learned in 
> a VPLS
> >    instance. Further work in progress defines an extension to MAC
> >    Address Withdrawal procedure which can greatly restrict the 
> scope  
> > of
> >    MAC flushing. This document provides two mechanisms which  
> > completely
> >    remove the need for MAC address flushing in VPLS instances. The
> >    mechanisms are MAC address switching and MAC address 
> notification.>
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-jiang-l2vpn-vpls-mac-
> operation-00.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > ->
> >
> > Please comment on the idea.
> >
> > Regards,
> >
> > Y.L. Jiang
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www.ietf.org/mailman/listinfo/pwe3
> 
> 


