
From giles.heron@gmail.com  Sat Apr  3 03:25:59 2010
Return-Path: <giles.heron@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 E1D8C3A69E9 for <l2vpn@core3.amsl.com>; Sat,  3 Apr 2010 03:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level: 
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 xdSeoBVlfteI for <l2vpn@core3.amsl.com>; Sat,  3 Apr 2010 03:25:59 -0700 (PDT)
Received: from mail-bw0-f228.google.com (mail-bw0-f228.google.com [209.85.218.228]) by core3.amsl.com (Postfix) with ESMTP id 2FD573A69C7 for <l2vpn@ietf.org>; Sat,  3 Apr 2010 03:25:57 -0700 (PDT)
Received: by bwz28 with SMTP id 28so1984981bwz.14 for <l2vpn@ietf.org>; Sat, 03 Apr 2010 03:25:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:mime-version :content-type:content-transfer-encoding; bh=qKtxEyPTcxR1DJv3HruJA47N2JJxwvhzh7ZNVa0pe6U=; b=aHKdAABe+sVkzieZ0giIS6LNiNoAH2hOZzC/lX3RV8M1/DA0bPhJwOAnfWAw+wsWJT xmbjpoCbXnWva8c2e+SwzJhuQZHcRcrb2O8DEzblVSIFPMU5SbreqPT17ESU7wGm83QO XfwCB+8Yu/ArvWGo3TnKcjr8quepGW/ufSC14=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:mime-version:content-type:content-transfer-encoding; b=FvaliX1OQ6TlFmD3BX4xYYVlAyvTOaxW0ZSKvE7MiVWbRYgRXyFqnPvVsUSlr3w7Zr U1foAU0smEeCjWNEWaamuvBAv8baGcankOYL79/6SXHPj0Wy/p6mfN3h0qVTxnBKUS0Q CyvPyMi94TA5rkTETvHegxPVYArvVZzyQyKGE=
Received: by 10.204.6.66 with SMTP id 2mr3947102bky.138.1270290352019; Sat, 03 Apr 2010 03:25:52 -0700 (PDT)
Received: from [192.168.1.13] (host86-145-239-140.range86-145.btcentralplus.com [86.145.239.140]) by mx.google.com with ESMTPS id l1sm86028774bkl.20.2010.04.03.03.25.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 03 Apr 2010 03:25:50 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.24.0.100208
Date: Sat, 03 Apr 2010 11:25:45 +0100
Subject: L2VPN Minutes from IETF77
From: Giles Heron <giles.heron@gmail.com>
To: <l2vpn@ietf.org>
Message-ID: <C7DCD639.3ACE9%giles.heron@gmail.com>
Thread-Topic: L2VPN Minutes from IETF77
Thread-Index: AcrTGAT/Usuy7FSC7kWGMHKRVicssw==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Shane Amante <shane@castlepoint.net>, BOCCI Matthew <Matthew.Bocci@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: Sat, 03 Apr 2010 10:26:00 -0000

The minutes from the L2VPN meeting at IET77 have now been uploaded:

http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt

Many thanks to Matthew Bocci for taking these.

Do please review these and send any corrections - and help fill in missing
names for one or two speakers.

Thanks

Shane & Giles



From shane@castlepoint.net  Sun Apr  4 07:04:10 2010
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 A0E553A68D9 for <l2vpn@core3.amsl.com>; Sun,  4 Apr 2010 07:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 7u-NRs1mnFvD for <l2vpn@core3.amsl.com>; Sun,  4 Apr 2010 07:04:09 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 83B593A6811 for <l2vpn@ietf.org>; Sun,  4 Apr 2010 07:04:09 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id E7B0126867C; Sun,  4 Apr 2010 08:04:07 -0600 (MDT)
Received: from mbpw.castlepoint.net (71.215.81.125 [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 04 Apr 2010 08:04:07 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=54286; client-dnsfail=71.215.81.125: name server failure; syn-fingerprint=65535:56:1:64:M1452,N,W3,N,N,T,S; data-bytes=0
From: Shane Amante <shane@castlepoint.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF 77 L2VPN WG follow-up items
Date: Sun, 4 Apr 2010 08:03:52 -0600
Message-Id: <BA8154CB-6D6A-4C19-A2CA-8B5F17466DCA@castlepoint.net>
To: l2vpn@ietf.org
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
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: Sun, 04 Apr 2010 14:04:10 -0000

Hi everyone,

Enclosed are a list of notes that I took during the most recent L2VPN WG =
meeting @ IETF 77 in Anaheim, CA, USA.  Please review and let us know if =
you have any questions.  If you have technical comments on one or more =
drafts in the list below, please start a new thread, so it's easier to =
track in the archives.

As stated during the WG meeting, we need to complete outstanding items =
on our WG Charter page, *before* we take on new WG items.  So, we =
welcome people to thoroughly review and provide comments on: ARP-MED, =
IPLS, MIB, OAM and Multicast (VPLS multicast & VPMS) work products!

Thanks!

Giles & Shane

---snip---
Follow-up Items from L2VPN WG meeting @ IETF 77

1)  ARP-MED & IPLS + IPv6 changes:
    - draft-ietf-l2vpn-arp-mediation-13
    - draft-ietf-l2vpn-ipls-09
      + Nick DelRegno, Andy Malis and Pranjal Dutta to provide thorough
      reviews, particularly on IPv6 portions, during WG Last Call.
      + The co-chairs welcome additional people to provide comprehensive
      reviews during WG Last Call.
      + WG Last Call will start Monday, April 5th.  Co-chairs will issue =
mails
      to L2VPN mailing list to capture issues/concerns during Last Call.

2)  SNMP MIB:
    - draft-ietf-l2vpn-vpls-mib-03: H-VPLS MIB
      + Authors believe they addressed all outstanding comments.
      + 3 implementations of this MIB.
      + Should be ready for WG Last Call prior to next IETF?
      + Draft to only address H-VPLS.  PBB-VPLS to be pursued in =
separate
      MIB if the need should arise.
      + Please review MIB and send comments/questions to Mailing List.
    - draft-kkoushik-snmp-context-map-mib-02: SNMP Context Mapping MIB
      + Issued new version of this draft.
      + Plan is to submit this as an Individual Informational draft, not
      related to the L2VPN WG, (or any other WG).

3)  MAC Flush Loop Detection in VPLS:
    - draft-ietf-l2vpn-vpls-ldp-mac-opt-01
      + Although there was a concern that the current draft only =
addresses
      Control Plane loop detection and /not/ Data Plane loop detection,
      there was very good support @ WG meeting (6 - 8 for; 1 against) to =
move
      this forward as a WG draft "as is", (just addressing Control Plane =
LD
      for now).  Data Plane Loop Detection can be added to this draft, =
or as
      a separate draft, at a later point in time should be there WG =
consensus
      to do so.
      + Co-chairs to follow-up with call on WG mailing list to make the
      doc "as is" a WG draft before next IETF.

4)  Extensions to LDP MAC Withdraw for PBB-VPLS:
    - draft-balus-l2vpn-pbb-ldp-ext-02
      + Addressed previous comments on existing draft.
      + Co-authors suggested merging the above draft with
      draft-ietf-l2vpn-vpls-ldp-mac-opt-01 (LDP Extensions for Optimized =
MAC
      Withdrawl in H-VPLS), in order to have a single consolidated =
document
      that covers all optimized LDP Extensions for Optimized MAC =
withdrawl
      for all underlying Ethernet technologies.
      + There were 10 people @ WG meeting that agreed to merge the two =
drafts,
      and 1 objection.
      + Co-chairs to follow-up with call on WG mailing list to merge
      the two drafts together before next IETF.

5)  Multicast/VPLS:
    - draft-ietf-l2vpn-vpls-mcast-06: Rahul mentioned that Wim =
Henderickx to
    provide review prior to WG Last Call.

6)  VPMS:
    - draft-raggarwa-l2vpn-p2mp-pw-02: Rahul to issue new Individual I-D=20=

    containing only BGP Auto Discovery portions of the aforementioned =
draft,
    which are relevant to L2VPN WG.  P2MP PW portions are being taken up =
by
    the PWE3 WG.

7)  Active/Active Multihoming:
    - draft-sajassi-l2vpn-rvpls-bgp-00: Routed VPLS using BGP
      + Was presented by Ali at WG meeting
    - draft-raggarwa-mac-vpn-00: BGP MPLS Based MAC VPN
      + Was published immediately after WG meeting, but not discussed.
    - As I, and others, mentioned at the WG meeting, Active/Backup =
Multihomed
    CE's have been part of the architecture of VPLS from the beginning;
    however, Active/Active Multihoming has /not/.  Therefore, we're =
going to
    consider this work as not in the L2VPN WG's charter.
    - People can still work on forming a good _requirements_ (not, =
solutions!)
    doc that may be used as input during a WG recharter in the future.

8)  E-TREE:
    - draft-key-l2vpn-vpls-etree-02
    - draft-jiang-l2vpn-vpls-pe-etree-00
    - draft-ietf-l2vpn-vpls-mib-03
    - Two important things to note about this work:
      a)  Please look at the above comments with respect to:
      draft-raggarwa-l2vpn-p2mp-pw-02.  This, along with associated work =
in
      PWE3, may address some of the E-TREE requirements.  However, this =
work
      is specific to VPMS.
      b)  Any other work related to E-TREE is currently out-of-scope of
      the L2VPN WG charter.  People can work on a candidate set of
      requirements that may be considered during a WG recharter in the =
future.=

From lucyyong@huawei.com  Sun Apr  4 08:42:27 2010
Return-Path: <lucyyong@huawei.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 1E1CD3A6A3B for <l2vpn@core3.amsl.com>; Sun,  4 Apr 2010 08:42:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.105
X-Spam-Level: **
X-Spam-Status: No, score=2.105 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.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 zDqYSetZbXdN for <l2vpn@core3.amsl.com>; Sun,  4 Apr 2010 08:42:26 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id D9BC13A688F for <l2vpn@ietf.org>; Sun,  4 Apr 2010 08:42:25 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L0C00MTEZME9K@szxga04-in.huawei.com> for l2vpn@ietf.org; Sun, 04 Apr 2010 23:42:14 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L0C00GU8ZMDD6@szxga04-in.huawei.com> for l2vpn@ietf.org; Sun, 04 Apr 2010 23:42:14 +0800 (CST)
Received: from y736742 (cpe-173-173-72-140.tx.res.rr.com [173.173.72.140]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0L0C00BKYZM55R@szxml02-in.huawei.com>; Sun, 04 Apr 2010 23:42:13 +0800 (CST)
Date: Sun, 04 Apr 2010 10:42:04 -0500
From: Yong Lucy <lucyyong@huawei.com>
Subject: RE: IETF 77 L2VPN WG follow-up items
In-reply-to: <BA8154CB-6D6A-4C19-A2CA-8B5F17466DCA@castlepoint.net>
To: 'Shane Amante' <shane@castlepoint.net>, l2vpn@ietf.org
Message-id: <009f01cad40d$65ee9b80$6701a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcrT/9b1j9Zh6Gn/SGWRdhZBc/ZtBAADGr3g
References: <BA8154CB-6D6A-4C19-A2CA-8B5F17466DCA@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: Sun, 04 Apr 2010 15:42:27 -0000

Hi Shane,

draft-key-l2vpn-etree-frwk-02 was also presented in the meeting. The
follow-up item is to look at latest VPMS work.

Regards,
Lucy

> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of
> Shane Amante
> Sent: Sunday, April 04, 2010 9:04 AM
> To: l2vpn@ietf.org
> Subject: IETF 77 L2VPN WG follow-up items
> 
> Hi everyone,
> 
> Enclosed are a list of notes that I took during the most recent L2VPN WG
> meeting @ IETF 77 in Anaheim, CA, USA.  Please review and let us know if
> you have any questions.  If you have technical comments on one or more
> drafts in the list below, please start a new thread, so it's easier to
> track in the archives.
> 
> As stated during the WG meeting, we need to complete outstanding items on
> our WG Charter page, *before* we take on new WG items.  So, we welcome
> people to thoroughly review and provide comments on: ARP-MED, IPLS, MIB,
> OAM and Multicast (VPLS multicast & VPMS) work products!
> 
> Thanks!
> 
> Giles & Shane
> 
> ---snip---
> Follow-up Items from L2VPN WG meeting @ IETF 77
> 
> 1)  ARP-MED & IPLS + IPv6 changes:
>     - draft-ietf-l2vpn-arp-mediation-13
>     - draft-ietf-l2vpn-ipls-09
>       + Nick DelRegno, Andy Malis and Pranjal Dutta to provide thorough
>       reviews, particularly on IPv6 portions, during WG Last Call.
>       + The co-chairs welcome additional people to provide comprehensive
>       reviews during WG Last Call.
>       + WG Last Call will start Monday, April 5th.  Co-chairs will issue
> mails
>       to L2VPN mailing list to capture issues/concerns during Last Call.
> 
> 2)  SNMP MIB:
>     - draft-ietf-l2vpn-vpls-mib-03: H-VPLS MIB
>       + Authors believe they addressed all outstanding comments.
>       + 3 implementations of this MIB.
>       + Should be ready for WG Last Call prior to next IETF?
>       + Draft to only address H-VPLS.  PBB-VPLS to be pursued in separate
>       MIB if the need should arise.
>       + Please review MIB and send comments/questions to Mailing List.
>     - draft-kkoushik-snmp-context-map-mib-02: SNMP Context Mapping MIB
>       + Issued new version of this draft.
>       + Plan is to submit this as an Individual Informational draft, not
>       related to the L2VPN WG, (or any other WG).
> 
> 3)  MAC Flush Loop Detection in VPLS:
>     - draft-ietf-l2vpn-vpls-ldp-mac-opt-01
>       + Although there was a concern that the current draft only addresses
>       Control Plane loop detection and /not/ Data Plane loop detection,
>       there was very good support @ WG meeting (6 - 8 for; 1 against) to
> move
>       this forward as a WG draft "as is", (just addressing Control Plane
> LD
>       for now).  Data Plane Loop Detection can be added to this draft, or
> as
>       a separate draft, at a later point in time should be there WG
> consensus
>       to do so.
>       + Co-chairs to follow-up with call on WG mailing list to make the
>       doc "as is" a WG draft before next IETF.
> 
> 4)  Extensions to LDP MAC Withdraw for PBB-VPLS:
>     - draft-balus-l2vpn-pbb-ldp-ext-02
>       + Addressed previous comments on existing draft.
>       + Co-authors suggested merging the above draft with
>       draft-ietf-l2vpn-vpls-ldp-mac-opt-01 (LDP Extensions for Optimized
> MAC
>       Withdrawl in H-VPLS), in order to have a single consolidated
> document
>       that covers all optimized LDP Extensions for Optimized MAC withdrawl
>       for all underlying Ethernet technologies.
>       + There were 10 people @ WG meeting that agreed to merge the two
> drafts,
>       and 1 objection.
>       + Co-chairs to follow-up with call on WG mailing list to merge
>       the two drafts together before next IETF.
> 
> 5)  Multicast/VPLS:
>     - draft-ietf-l2vpn-vpls-mcast-06: Rahul mentioned that Wim Henderickx
> to
>     provide review prior to WG Last Call.
> 
> 6)  VPMS:
>     - draft-raggarwa-l2vpn-p2mp-pw-02: Rahul to issue new Individual I-D
>     containing only BGP Auto Discovery portions of the aforementioned
> draft,
>     which are relevant to L2VPN WG.  P2MP PW portions are being taken up
> by
>     the PWE3 WG.
> 
> 7)  Active/Active Multihoming:
>     - draft-sajassi-l2vpn-rvpls-bgp-00: Routed VPLS using BGP
>       + Was presented by Ali at WG meeting
>     - draft-raggarwa-mac-vpn-00: BGP MPLS Based MAC VPN
>       + Was published immediately after WG meeting, but not discussed.
>     - As I, and others, mentioned at the WG meeting, Active/Backup
> Multihomed
>     CE's have been part of the architecture of VPLS from the beginning;
>     however, Active/Active Multihoming has /not/.  Therefore, we're going
> to
>     consider this work as not in the L2VPN WG's charter.
>     - People can still work on forming a good _requirements_ (not,
> solutions!)
>     doc that may be used as input during a WG recharter in the future.
> 
> 8)  E-TREE:
>     - draft-key-l2vpn-vpls-etree-02
>     - draft-jiang-l2vpn-vpls-pe-etree-00
>     - draft-ietf-l2vpn-vpls-mib-03
>     - Two important things to note about this work:
>       a)  Please look at the above comments with respect to:
>       draft-raggarwa-l2vpn-p2mp-pw-02.  This, along with associated work
> in
>       PWE3, may address some of the E-TREE requirements.  However, this
> work
>       is specific to VPMS.
>       b)  Any other work related to E-TREE is currently out-of-scope of
>       the L2VPN WG charter.  People can work on a candidate set of
>       requirements that may be considered during a WG recharter in the
> future.=


From shane@castlepoint.net  Sun Apr  4 09:19:27 2010
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 4883E3A6893 for <l2vpn@core3.amsl.com>; Sun,  4 Apr 2010 09:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.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 dYUC4wFjU3UY for <l2vpn@core3.amsl.com>; Sun,  4 Apr 2010 09:19:22 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 3A2303A6A62 for <l2vpn@ietf.org>; Sun,  4 Apr 2010 09:19:20 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 097C726867C; Sun,  4 Apr 2010 10:19:19 -0600 (MDT)
Received: from mbpw.castlepoint.net (71.215.81.125 [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Sun, 04 Apr 2010 10:19:18 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=54990; client-dnsfail=71.215.81.125: name server failure; syn-fingerprint=65535:56:1:64:M1452,N,W3,N,N,T,S; data-bytes=0
Subject: Re: IETF 77 L2VPN WG follow-up items
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <009f01cad40d$65ee9b80$6701a8c0@china.huawei.com>
Date: Sun, 4 Apr 2010 10:19:03 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3584BD47-853C-4105-9AA3-6FD54D6E0121@castlepoint.net>
References: <BA8154CB-6D6A-4C19-A2CA-8B5F17466DCA@castlepoint.net> <009f01cad40d$65ee9b80$6701a8c0@china.huawei.com>
To: Yong Lucy <lucyyong@huawei.com>
X-Mailer: Apple Mail (2.1078)
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: Sun, 04 Apr 2010 16:19:28 -0000

Lucy,

Yes it was.  Looks like a cut & paste error on my part.  My apologies & =
thanks!

-shane


On Apr 4, 2010, at 09:42 MDT, Yong Lucy wrote:

> Hi Shane,
>=20
> draft-key-l2vpn-etree-frwk-02 was also presented in the meeting. The
> follow-up item is to look at latest VPMS work.
>=20
> Regards,
> Lucy
>=20
>> -----Original Message-----
>> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On =
Behalf Of
>> Shane Amante
>> Sent: Sunday, April 04, 2010 9:04 AM
>> To: l2vpn@ietf.org
>> Subject: IETF 77 L2VPN WG follow-up items
>>=20
>> Hi everyone,
>>=20
>> Enclosed are a list of notes that I took during the most recent L2VPN =
WG
>> meeting @ IETF 77 in Anaheim, CA, USA.  Please review and let us know =
if
>> you have any questions.  If you have technical comments on one or =
more
>> drafts in the list below, please start a new thread, so it's easier =
to
>> track in the archives.
>>=20
>> As stated during the WG meeting, we need to complete outstanding =
items on
>> our WG Charter page, *before* we take on new WG items.  So, we =
welcome
>> people to thoroughly review and provide comments on: ARP-MED, IPLS, =
MIB,
>> OAM and Multicast (VPLS multicast & VPMS) work products!
>>=20
>> Thanks!
>>=20
>> Giles & Shane
>>=20
>> ---snip---
>> Follow-up Items from L2VPN WG meeting @ IETF 77
>>=20
>> 1)  ARP-MED & IPLS + IPv6 changes:
>>    - draft-ietf-l2vpn-arp-mediation-13
>>    - draft-ietf-l2vpn-ipls-09
>>      + Nick DelRegno, Andy Malis and Pranjal Dutta to provide =
thorough
>>      reviews, particularly on IPv6 portions, during WG Last Call.
>>      + The co-chairs welcome additional people to provide =
comprehensive
>>      reviews during WG Last Call.
>>      + WG Last Call will start Monday, April 5th.  Co-chairs will =
issue
>> mails
>>      to L2VPN mailing list to capture issues/concerns during Last =
Call.
>>=20
>> 2)  SNMP MIB:
>>    - draft-ietf-l2vpn-vpls-mib-03: H-VPLS MIB
>>      + Authors believe they addressed all outstanding comments.
>>      + 3 implementations of this MIB.
>>      + Should be ready for WG Last Call prior to next IETF?
>>      + Draft to only address H-VPLS.  PBB-VPLS to be pursued in =
separate
>>      MIB if the need should arise.
>>      + Please review MIB and send comments/questions to Mailing List.
>>    - draft-kkoushik-snmp-context-map-mib-02: SNMP Context Mapping MIB
>>      + Issued new version of this draft.
>>      + Plan is to submit this as an Individual Informational draft, =
not
>>      related to the L2VPN WG, (or any other WG).
>>=20
>> 3)  MAC Flush Loop Detection in VPLS:
>>    - draft-ietf-l2vpn-vpls-ldp-mac-opt-01
>>      + Although there was a concern that the current draft only =
addresses
>>      Control Plane loop detection and /not/ Data Plane loop =
detection,
>>      there was very good support @ WG meeting (6 - 8 for; 1 against) =
to
>> move
>>      this forward as a WG draft "as is", (just addressing Control =
Plane
>> LD
>>      for now).  Data Plane Loop Detection can be added to this draft, =
or
>> as
>>      a separate draft, at a later point in time should be there WG
>> consensus
>>      to do so.
>>      + Co-chairs to follow-up with call on WG mailing list to make =
the
>>      doc "as is" a WG draft before next IETF.
>>=20
>> 4)  Extensions to LDP MAC Withdraw for PBB-VPLS:
>>    - draft-balus-l2vpn-pbb-ldp-ext-02
>>      + Addressed previous comments on existing draft.
>>      + Co-authors suggested merging the above draft with
>>      draft-ietf-l2vpn-vpls-ldp-mac-opt-01 (LDP Extensions for =
Optimized
>> MAC
>>      Withdrawl in H-VPLS), in order to have a single consolidated
>> document
>>      that covers all optimized LDP Extensions for Optimized MAC =
withdrawl
>>      for all underlying Ethernet technologies.
>>      + There were 10 people @ WG meeting that agreed to merge the two
>> drafts,
>>      and 1 objection.
>>      + Co-chairs to follow-up with call on WG mailing list to merge
>>      the two drafts together before next IETF.
>>=20
>> 5)  Multicast/VPLS:
>>    - draft-ietf-l2vpn-vpls-mcast-06: Rahul mentioned that Wim =
Henderickx
>> to
>>    provide review prior to WG Last Call.
>>=20
>> 6)  VPMS:
>>    - draft-raggarwa-l2vpn-p2mp-pw-02: Rahul to issue new Individual =
I-D
>>    containing only BGP Auto Discovery portions of the aforementioned
>> draft,
>>    which are relevant to L2VPN WG.  P2MP PW portions are being taken =
up
>> by
>>    the PWE3 WG.
>>=20
>> 7)  Active/Active Multihoming:
>>    - draft-sajassi-l2vpn-rvpls-bgp-00: Routed VPLS using BGP
>>      + Was presented by Ali at WG meeting
>>    - draft-raggarwa-mac-vpn-00: BGP MPLS Based MAC VPN
>>      + Was published immediately after WG meeting, but not discussed.
>>    - As I, and others, mentioned at the WG meeting, Active/Backup
>> Multihomed
>>    CE's have been part of the architecture of VPLS from the =
beginning;
>>    however, Active/Active Multihoming has /not/.  Therefore, we're =
going
>> to
>>    consider this work as not in the L2VPN WG's charter.
>>    - People can still work on forming a good _requirements_ (not,
>> solutions!)
>>    doc that may be used as input during a WG recharter in the future.
>>=20
>> 8)  E-TREE:
>>    - draft-key-l2vpn-vpls-etree-02
>>    - draft-jiang-l2vpn-vpls-pe-etree-00
>>    - draft-ietf-l2vpn-vpls-mib-03
>>    - Two important things to note about this work:
>>      a)  Please look at the above comments with respect to:
>>      draft-raggarwa-l2vpn-p2mp-pw-02.  This, along with associated =
work
>> in
>>      PWE3, may address some of the E-TREE requirements.  However, =
this
>> work
>>      is specific to VPMS.
>>      b)  Any other work related to E-TREE is currently out-of-scope =
of
>>      the L2VPN WG charter.  People can work on a candidate set of
>>      requirements that may be considered during a WG recharter in the
>> future.=3D
>=20


From simon.delord@gmail.com  Mon Apr  5 16:55:49 2010
Return-Path: <simon.delord@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 AFC5D3A693D for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 16:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 Nx3Ck+ArKCj9 for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 16:55:48 -0700 (PDT)
Received: from mail-yw0-f182.google.com (mail-yw0-f182.google.com [209.85.211.182]) by core3.amsl.com (Postfix) with ESMTP id 537483A63D3 for <l2vpn@ietf.org>; Mon,  5 Apr 2010 16:55:47 -0700 (PDT)
Received: by ywh12 with SMTP id 12so2553332ywh.32 for <l2vpn@ietf.org>; Mon, 05 Apr 2010 16:55:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=jNULojBHAXg4mDNiSg9hZdhtxLu5vWf3osMR3bW3hHE=; b=CQfG75rO7NYGmp+75VXJT4muKdAqX6GDipdedBjFuqoTiAQYZYfgchQ8krH8BVlMjT FtCsxhKYzY+GSUv3GdUTDEFLefxicSxzgSw0IQu32xSJCZJ15H7F9UXfID1s0htad6jg jLeNkhog47FoWdNLrRjwyYtMJfH6DZ+fBvZD0=
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; b=USTA5wvGDgQz6wgt74uNKh1cj3OEyK3fQJhlc/Bgf2y36yHsS0o5JbcpON5kiMOlhz Adw66wl7W9u8Bn5IrxhZnLCR4NaAeSUW8xAXqVlk82TI4Yh6e0F7GivRD3ae0LhUD+wt zjJyP7cg4brFV6W/MxOMatNaEQf4vOFoWGiSc=
MIME-Version: 1.0
Received: by 10.231.39.197 with HTTP; Mon, 5 Apr 2010 16:55:41 -0700 (PDT)
In-Reply-To: <C7DCD639.3ACE9%giles.heron@gmail.com>
References: <AcrTGAT/Usuy7FSC7kWGMHKRVicssw==> <C7DCD639.3ACE9%giles.heron@gmail.com>
Date: Tue, 6 Apr 2010 09:55:41 +1000
Received: by 10.100.53.6 with SMTP id b6mr15063794ana.135.1270511741862; Mon,  05 Apr 2010 16:55:41 -0700 (PDT)
Message-ID: <u2xef61db5f1004051655we7483284r65e3b44b654dcff5@mail.gmail.com>
Subject: Re: L2VPN Minutes from IETF77
From: Simon Delord <simon.delord@gmail.com>
To: Giles Heron <giles.heron@gmail.com>
Content-Type: multipart/alternative; boundary=001485f80e720e846d04838611d9
Cc: l2vpn@ietf.org, Shane Amante <shane@castlepoint.net>, BOCCI Matthew <Matthew.Bocci@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, 05 Apr 2010 23:55:49 -0000

--001485f80e720e846d04838611d9
Content-Type: text/plain; charset=ISO-8859-1

Giles, Matthew,

there may be an error in the minutes upload since the whole second half of
the L2VPN meeting is missing.

Simon

2010/4/3 Giles Heron <giles.heron@gmail.com>

> The minutes from the L2VPN meeting at IET77 have now been uploaded:
>
> http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
>
> Many thanks to Matthew Bocci for taking these.
>
> Do please review these and send any corrections - and help fill in missing
> names for one or two speakers.
>
> Thanks
>
> Shane & Giles
>
>
>

--001485f80e720e846d04838611d9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Giles, Matthew,<br>=A0<br>there may be an error in the minutes upload =
since the whole second half of the L2VPN meeting is missing.</div>
<div>=A0</div>
<div>Simon<br><br></div>
<div class=3D"gmail_quote">2010/4/3 Giles Heron <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:giles.heron@gmail.com">giles.heron@gmail.com</a>&gt;</span><br=
>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The minutes from the L2VPN meeti=
ng at IET77 have now been uploaded:<br><br><a href=3D"http://www.ietf.org/p=
roceedings/10mar/minutes/l2vpn.txt" target=3D"_blank">http://www.ietf.org/p=
roceedings/10mar/minutes/l2vpn.txt</a><br>
<br>Many thanks to Matthew Bocci for taking these.<br><br>Do please review =
these and send any corrections - and help fill in missing<br>names for one =
or two speakers.<br><br>Thanks<br><br>Shane &amp; Giles<br><br><br></blockq=
uote>
</div><br>

--001485f80e720e846d04838611d9--

From shane@castlepoint.net  Mon Apr  5 18:56:55 2010
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 2A1803A6807 for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 18:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 0Xy03O7Hd7Ij for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 18:56:54 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 44EA23A67BD for <l2vpn@ietf.org>; Mon,  5 Apr 2010 18:56:53 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 9A169268675; Mon,  5 Apr 2010 19:56:51 -0600 (MDT)
Received: from mbpw.castlepoint.net (71.215.81.125 [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Mon, 05 Apr 2010 19:56:51 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=64652; client-dnsfail=71.215.81.125: name server failure; syn-fingerprint=65535:56:1:64:M1452,N,W3,N,N,T,S; data-bytes=0
From: Shane Amante <shane@castlepoint.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: WG Last Call: draft-ietf-l2vpn-arp-mediation-13
Date: Mon, 5 Apr 2010 19:56:36 -0600
Message-Id: <2530B373-F6FF-4310-8513-1F892A725866@castlepoint.net>
To: l2vpn@ietf.org
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
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, 06 Apr 2010 01:56:55 -0000

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-arp-mediation-13

If you have substantial technical comments or concerns, please share =
them with the list.  If you have editorial comments, please share them =
directly with the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and =
comments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the =
time and/or inclination, please let the chairs know if you'll be =
conducting a review.

The Last Call on this draft will end on April 23.

Thanks,

Giles & Shane

From shane@castlepoint.net  Mon Apr  5 18:58:21 2010
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 9BCE63A6819 for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 18:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71+J8+GNXNUl for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 18:58:20 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id E3AB03A6816 for <l2vpn@ietf.org>; Mon,  5 Apr 2010 18:58:20 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 3C966268675; Mon,  5 Apr 2010 19:58:19 -0600 (MDT)
Received: from mbpw.castlepoint.net (71-215-81-125.hlrn.qwest.net [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Mon, 05 Apr 2010 19:58:19 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=64656; syn-fingerprint=65535:56:1:64:M1452,N,W3,N,N,T,S; data-bytes=0
From: Shane Amante <shane@castlepoint.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09
Date: Mon, 5 Apr 2010 19:58:01 -0600
Message-Id: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
To: l2vpn@ietf.org
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
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, 06 Apr 2010 01:58:21 -0000

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share =
them with the list.  If you have editorial comments, please share them =
directly with the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and =
comments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the =
time and/or inclination, please let the chairs know if you'll be =
conducting a review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane=

From Joel.Pauling@alcatel-lucent.com  Mon Apr  5 19:40:16 2010
Return-Path: <Joel.Pauling@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 BF14A3A6A28 for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 19:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 lBFDCu0UYNzo for <l2vpn@core3.amsl.com>; Mon,  5 Apr 2010 19:40:11 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by core3.amsl.com (Postfix) with ESMTP id E40663A67EC for <l2vpn@ietf.org>; Mon,  5 Apr 2010 19:40:10 -0700 (PDT)
Received: from horh1.pdc.alcatel-lucent.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id o362e8D7017836 for <l2vpn@ietf.org>; Mon, 5 Apr 2010 21:40:08 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.pdc.alcatel-lucent.com (8.13.8/emsr) with ESMTP id o362e6Yc028191 for <l2vpn@ietf.org>; Mon, 5 Apr 2010 21:40:07 -0500 (CDT)
Received: from sgsinsbhs01.ad4.ad.alcatel.com (sgsinsbhs01.ap.lucent.com [135.254.109.34]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id o362SWk3015847 for <l2vpn@ietf.org>; Tue, 6 Apr 2010 10:28:33 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.25]) by sgsinsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 Apr 2010 10:40:05 +0800
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: WG Last Call: draft-ietf-l2vpn-ipls-09
Date: Tue, 6 Apr 2010 10:40:03 +0800
Message-ID: <D434F7EE545145439BFA47601F9B2BA302F6ACAB@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLKV0PSguv1yOSDSMtyd3zpMAzQABQgJQ
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
From: "PAULING JOEL" <Joel.Pauling@alcatel-lucent.com>
To: <l2vpn@ietf.org>
X-OriginalArrivalTime: 06 Apr 2010 02:40:05.0394 (UTC) FILETIME=[76EF0F20:01CAD532]
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.28
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
X-Mailman-Approved-At: Tue, 06 Apr 2010 07:29:07 -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, 06 Apr 2010 02:41:09 -0000

Looks good.=20

One comment:=20

Re fallback protocol (proposed to be IPv4) should be a tuneable option. =
While the V6 compatibility flag currently signals v6 stack compatibility =
on the tunnel end point, I would prefer from a future proofing =
perspective if the fallback protocol was definable.=20

Especially in MPLS PE-PE scenarios, it is preferable to run either IPV4 =
+ MPLS OR IPV6 + MPLS, rather than both through a MS core network =
(reducing admin overhead by having to maintain two stacks). Having =
fallback protocol be a tuneable option will cater to this scenario =
better than current proposed draft.


Kind regards


Joel W Pauling

Network Capability Engineer
Alcatel-Lucent New Zealand
+64 4 803 7639
+64 21 171 8049
joel.pauling@alcatel-lucent.com

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf =
Of Shane Amante
Sent: Tuesday, 6 April 2010 1:58 p.m.
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share =
them with the list.  If you have editorial comments, please share them =
directly with the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and =
comments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the =
time and/or inclination, please let the chairs know if you'll be =
conducting a review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From lizhong.jin@zte.com.cn  Wed Apr  7 08:32:57 2010
Return-Path: <lizhong.jin@zte.com.cn>
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 766C33A6A68 for <l2vpn@core3.amsl.com>; Wed,  7 Apr 2010 08:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpvpoTcgA1iN for <l2vpn@core3.amsl.com>; Wed,  7 Apr 2010 08:32:56 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 059483A6AB2 for <l2vpn@ietf.org>; Wed,  7 Apr 2010 08:31:42 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 36887577109098; Wed, 7 Apr 2010 23:29:11 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 83532.683968793; Wed, 7 Apr 2010 23:31:37 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o37FVrkw097194; Wed, 7 Apr 2010 23:31:53 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.66.1270321211.5236.l2vpn@ietf.org>
To: giles.heron@gmail.com
Subject: Re: L2VPN Minutes from IETF77
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF8F1D1693.91380CDD-ON482576FE.0055053E-482576FE.00554765@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Wed, 7 Apr 2010 23:31:29 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-07 23:31:35, Serialize complete at 2010-04-07 23:31:35
Content-Type: multipart/alternative; boundary="=_alternative 00554763482576FE_="
X-MAIL: mse2.zte.com.cn o37FVrkw097194
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, 07 Apr 2010 15:32:57 -0000

This is a multipart message in MIME format.
--=_alternative 00554763482576FE_=
Content-Type: text/plain; charset="US-ASCII"

Hi Giles,
The missing name in 5) MAC Flush Loop Detection in VPLS, is me. Thank you.

Best Regards
Lizhong Jin


----------------------------------------------------------------------

Message: 1
Date: Sat, 03 Apr 2010 11:25:45 +0100
From: Giles Heron <giles.heron@gmail.com>
Subject: L2VPN Minutes from IETF77
To: <l2vpn@ietf.org>
Cc: Shane Amante <shane@castlepoint.net>,                BOCCI Matthew
                 <Matthew.Bocci@alcatel-lucent.com>
Message-ID: <C7DCD639.3ACE9%giles.heron@gmail.com>
Content-Type: text/plain;                charset="US-ASCII"

The minutes from the L2VPN meeting at IET77 have now been uploaded:

http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt

Many thanks to Matthew Bocci for taking these.

Do please review these and send any corrections - and help fill in missing
names for one or two speakers.

Thanks

Shane & Giles




------------------------------

_______________________________________________
L2vpn mailing list
L2vpn@ietf.org
https://www.ietf.org/mailman/listinfo/l2vpn


End of L2vpn Digest, Vol 71, Issue 1
************************************




--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
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 expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 00554763482576FE_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Hi Giles,</font></tt>
<br><tt><font size=2>The missing name in 5) MAC Flush Loop Detection in
VPLS, is me. Thank you.</font></tt>
<br>
<br><tt><font size=2>Best Regards</font></tt>
<br><tt><font size=2>Lizhong Jin<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 03 Apr 2010 11:25:45 +0100<br>
From: Giles Heron &lt;giles.heron@gmail.com&gt;<br>
Subject: L2VPN Minutes from IETF77<br>
To: &lt;l2vpn@ietf.org&gt;<br>
Cc: Shane Amante &lt;shane@castlepoint.net&gt;, &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; BOCCI Matthew<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;Matthew.Bocci@alcatel-lucent.com&gt;<br>
Message-ID: &lt;C7DCD639.3ACE9%giles.heron@gmail.com&gt;<br>
Content-Type: text/plain; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; charset=&quot;US-ASCII&quot;<br>
<br>
The minutes from the L2VPN meeting at IET77 have now been uploaded:<br>
<br>
http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt<br>
<br>
Many thanks to Matthew Bocci for taking these.<br>
<br>
Do please review these and send any corrections - and help fill in missing<br>
names for one or two speakers.<br>
<br>
Thanks<br>
<br>
Shane &amp; Giles<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
L2vpn mailing list<br>
L2vpn@ietf.org<br>
https://www.ietf.org/mailman/listinfo/l2vpn<br>
<br>
<br>
End of L2vpn Digest, Vol 71, Issue 1<br>
************************************<br>
<br>
</font></tt>
<br><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 00554763482576FE_=--


From root@core3.amsl.com  Fri Apr  9 15:30:05 2010
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 C25FD3A6A4F; Fri,  9 Apr 2010 15:30:03 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ietf-l2vpn-vpls-mib-04.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100409223004.C25FD3A6A4F@core3.amsl.com>
Date: Fri,  9 Apr 2010 15:30:04 -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: <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, 09 Apr 2010 22:30:05 -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		: Virtual Private Lan Services (VPLS) Management Information Base
	Author(s)	: R. Mediratta, T. Nadeau, K. Koushik
	Filename	: draft-ietf-l2vpn-vpls-mib-04.txt
	Pages		: 45
	Date		: 2010-4-9
	
This memo defines an experimental portion of the Management
    Information Base for use with network management protocols in the
    Internet community.  In particular, it describes managed objects
    for modeling of Virtual Private LAN services. It needs to be used
    in conjunction with Pseudo Wire (PW) Management Information Base
    [RFC5601].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-mib-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-mib-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-4-9152632.I-D@ietf.org>


--NextPart--


From raymond.key@ieee.org  Sat Apr 17 03:12:13 2010
Return-Path: <raymond.key@ieee.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 4FC003A69CC; Sat, 17 Apr 2010 03:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.492
X-Spam-Level: 
X-Spam-Status: No, score=-98.492 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBKN20gSgU-z; Sat, 17 Apr 2010 03:12:12 -0700 (PDT)
Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by core3.amsl.com (Postfix) with ESMTP id F26D23A6839; Sat, 17 Apr 2010 03:12:11 -0700 (PDT)
Received: from localhost.localdomain (webmail06.syd.optusnet.com.au [211.29.133.86]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o3HAC15O029648; Sat, 17 Apr 2010 20:12:02 +1000
Message-Id: <201004171012.o3HAC15O029648@mail01.syd.optusnet.com.au>
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
X-Mailer: MIME-tools 5.420 (Entity 5.420)
Received: from c122-107-172-84.eburwd5.vic.optusnet.com.au ([122.107.172.84]) by webmail06.syd.optusnet.com.au with http (user=rkey_ieee@optusnet.com.au); Sat, 17 Apr 2010 20:12:01 +1000
From: Raymond Key <raymond.key@ieee.org>
To: l2vpn@ietf.org, pwe3@ietf.org
Date: Sat, 17 Apr 2010 20:12:01 +1000
Subject: Requirements for MEF E-Tree Support in VPLS
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raymond.key@ieee.org
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: Sat, 17 Apr 2010 10:12:13 -0000

Hi L2VPN & PWE3 working groups,

We have submitted a draft "Requirements for MEF E-Tree Support in VPLS"
http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-reqt-00

This hopefully can be used as a base for a "solution-neutral" discussion on 
whether there is a valid requirement to enhance VPLS or not.

Grateful if you could post comments on the mailing list, or email the authors.

Thanks,
Raymond Key 

From lizhong.jin@zte.com.cn  Sat Apr 17 08:16:17 2010
Return-Path: <lizhong.jin@zte.com.cn>
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 792743A6881 for <l2vpn@core3.amsl.com>; Sat, 17 Apr 2010 08:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.631
X-Spam-Level: 
X-Spam-Status: No, score=-100.631 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4x1haa2qN459 for <l2vpn@core3.amsl.com>; Sat, 17 Apr 2010 08:16:16 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 93CA33A68C2 for <l2vpn@ietf.org>; Sat, 17 Apr 2010 08:16:15 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 36887577109098; Sat, 17 Apr 2010 23:12:59 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 83532.5579635923; Sat, 17 Apr 2010 23:15:59 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o3HFGBQM077045; Sat, 17 Apr 2010 23:16:11 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
To: hshah@force10networks.com, karvind@enterasys.com, erosen@cisco.com, giles.heron@gmail.com, flefauch@cisco.com
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFB91AE237.C7D1E90E-ON48257708.0050726D-48257708.0053D26F@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Sat, 17 Apr 2010 23:15:42 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-17 23:15:51, Serialize complete at 2010-04-17 23:15:51
Content-Type: multipart/alternative; boundary="=_alternative 0053D26D48257708_="
X-MAIL: mse2.zte.com.cn o3HFGBQM077045
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: Sat, 17 Apr 2010 15:16:17 -0000

This is a multipart message in MIME format.
--=_alternative 0053D26D48257708_=
Content-Type: text/plain; charset="US-ASCII"

Hi Himanshu and authors,
After reviewing draft-ietf-l2vpn-ipls-09, I have the following comments:
1. Section 2.0, point 5, bullet c, more precisely, the unicast ARP packets 
received from "multicast" pseudowire may do MAC DA lookup, and forward to 
where CE is located. So the context should add this exception for ARP 
packets.
2. Section 7.1, I am wondering how to setup the unidirectional mp2p 
pseudowire. According to RFC4447, one pseudowire will be UP only when both 
local and remote label mapping message is sent and received. But according 
to the descripition of unidirectional mp2p pseudowire in IPLS, if PEx 
sends a label mapping to PEy for CEx, PEy seems to consider the PW as UP 
when receiving the corresponding label mapping, and PEx would consider the 
PW as UP when sending out the label mapping, without the necessarity of 
allocating local labels for the PW.
What's more, it is also difficult to configure the PWid. If PEx uses 
PWid_1 for CEx1, and PWid_2 for CEx2, according to section 7.1, the PEy 
needs to configure both PWid_1 and PWid_2, which is actually not 
necessary. Do I miss something important here to understand the concept of 
unidirectional mp2p pseudowire? There may be a new type of FEC that is 
required, similar with unidirectional P2MP PW.
3. Section 7.2, why not using LDP capability to advertising IPv6 stack 
capability?
4. Will IPLS consider any spoke connectivity to increase the scalability, 
same as VPLS?

Hope to see your reply, thank you.

Best Regards
Lizhong Jin
 

------------------------------

Date: Mon, 5 Apr 2010 19:58:01 -0600
From: Shane Amante <shane@castlepoint.net>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09
To: l2vpn@ietf.org
Message-ID: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
Content-Type: text/plain; charset=us-ascii

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them 
with the list.  If you have editorial comments, please share them directly 
with the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and 
comments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the 
time and/or inclination, please let the chairs know if you'll be 
conducting a review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
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 expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 0053D26D48257708_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Himanshu and authors,</font>
<br><font size=2 face="sans-serif">After reviewing draft-ietf-l2vpn-ipls-09,
I have the following comments:<br>
1. Section 2.0, point 5, bullet c, more precisely, the unicast ARP packets
received from &quot;multicast&quot; pseudowire may do MAC DA lookup, and
forward to where CE is located. So the context should add this exception
for ARP packets.</font>
<br><font size=2 face="sans-serif">2. Section 7.1, I am wondering how to
setup the unidirectional mp2p pseudowire. According to RFC4447, one pseudowire
will be UP only when both local and remote label mapping message is sent
and received. But according to the descripition of unidirectional mp2p
pseudowire in IPLS, if PEx sends a label mapping to PEy for CEx, PEy seems
to consider the PW as UP when receiving the corresponding label mapping,
and PEx would consider the PW as UP when sending out the label mapping,
without the necessarity of allocating local labels for the PW.</font>
<br><font size=2 face="sans-serif">What's more, it is also difficult to
configure the PWid. If PEx uses PWid_1 for CEx1, and PWid_2 for CEx2, according
to section 7.1, the PEy needs to configure both PWid_1 and PWid_2, which
is actually not necessary. Do I miss something important here to understand
the concept of unidirectional mp2p pseudowire? There may be a new type
of FEC that is required, similar with unidirectional P2MP PW.</font>
<br><font size=2 face="sans-serif">3. Section 7.2, why not using LDP capability
to advertising IPv6 stack capability?</font>
<br><font size=2 face="sans-serif">4. Will IPLS consider any spoke connectivity
to increase the scalability, same as VPLS?</font>
<br>
<br><font size=2 face="sans-serif">Hope to see your reply, thank you.</font>
<br>
<br><font size=2 face="sans-serif">Best Regards</font>
<br><font size=2 face="sans-serif">Lizhong Jin</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br><tt><font size=2>------------------------------<br>
<br>
Date: Mon, 5 Apr 2010 19:58:01 -0600<br>
From: Shane Amante &lt;shane@castlepoint.net&gt;<br>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<br>
To: l2vpn@ietf.org<br>
Message-ID: &lt;7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net&gt;<br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi Everyone,<br>
<br>
This is to begin a (final) WG Last Call on:<br>
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09<br>
<br>
If you have substantial technical comments or concerns, please share them
with the list. &nbsp;If you have editorial comments, please share them
directly with the authors and co-chairs.<br>
<br>
So far, we have the following folks signed up for a thorough review and
comments:<br>
- Andy Malis<br>
- Nick DelRegno<br>
- Pranjal Dutta<br>
However, we could use more people to conduct a review. &nbsp;If you have
the time and/or inclination, please let the chairs know if you'll be conducting
a review.<br>
<br>
The Last Call on this draft will also end on April 23.<br>
<br>
Thanks,<br>
<br>
Giles &amp; Shane</font></tt><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 0053D26D48257708_=--


From giles.heron@gmail.com  Sun Apr 18 11:44:42 2010
Return-Path: <giles.heron@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 0FB3E3A6B3F for <l2vpn@core3.amsl.com>; Sun, 18 Apr 2010 11:44:42 -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 TJKyWWraY3cU for <l2vpn@core3.amsl.com>; Sun, 18 Apr 2010 11:44:41 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 36C5F28C130 for <l2vpn@ietf.org>; Sun, 18 Apr 2010 11:44:40 -0700 (PDT)
Received: by wwi18 with SMTP id 18so194743wwi.31 for <l2vpn@ietf.org>; Sun, 18 Apr 2010 11:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:message-id:thread-topic:thread-index:mime-version:content-type :content-transfer-encoding; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=RpQA2fhwkMECVeu1TiOlIFsLOA/DymzoupXBhBb1w9OijJ+uvVhP4xroQ8ddh5rF0R UISDFEws+JVMDGoiLAjR7bRpSpANqUjnjeK8RktCIOz4gn+jDy9VyuJUPnFu6ua7bqYa L9l5dKWzhSB++PF+gK5NyBjyINvAOc92yUNFc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:mime-version:content-type:content-transfer-encoding; b=D1bF04+0s7NerxUVS1SiGk8fS4A50t+VU5pOoKla0prI7AQnVLItc9uariXtvLMjO6 DIadmKdToEaMb0gijWSCPFqKkJN4k+i+W30m1M8nVenbn6YSORiseTuAZWlnl37eT8Zu NvK2ZpwYGnVbk43EtqVDcGgOXE8aYbYwDoe90=
Received: by 10.216.86.196 with SMTP id w46mr1780697wee.201.1271616269125; Sun, 18 Apr 2010 11:44:29 -0700 (PDT)
Received: from [192.168.1.13] (host86-143-168-117.range86-143.btcentralplus.com [86.143.168.117]) by mx.google.com with ESMTPS id t27sm41551140wbc.23.2010.04.18.11.44.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 18 Apr 2010 11:44:28 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.24.0.100208
Date: Sun, 18 Apr 2010 19:44:22 +0100
Subject: Updated minutes from IETF77
From: Giles Heron <giles.heron@gmail.com>
To: <l2vpn@ietf.org>
Message-ID: <C7F11196.3EFC4%giles.heron@gmail.com>
Thread-Topic: Updated minutes from IETF77
Thread-Index: AcrfJykdG+fgAkvwN0q/y2vS0eABSw==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
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: Sun, 18 Apr 2010 18:44:42 -0000


From giles.heron@gmail.com  Sun Apr 18 11:47:51 2010
Return-Path: <giles.heron@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 8ED9F28C147 for <l2vpn@core3.amsl.com>; Sun, 18 Apr 2010 11:47:51 -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 6aZJA-Ais30z for <l2vpn@core3.amsl.com>; Sun, 18 Apr 2010 11:47:50 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 085C528C140 for <l2vpn@ietf.org>; Sun, 18 Apr 2010 11:47:47 -0700 (PDT)
Received: by wwi18 with SMTP id 18so195851wwi.31 for <l2vpn@ietf.org>; Sun, 18 Apr 2010 11:47:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:message-id:thread-topic:thread-index:mime-version:content-type :content-transfer-encoding; bh=mjRXQIFkkPLyu5YoQYBrrlOg49lgzPLfiQdjrUuXb4s=; b=bnqYTfHyjGbtyaHjvB9ItmgKpvL+dHsbLPgPqhbdPCMBqufmopE57Qu172JNqX4fcN eWz6CDnjTeaEABumQSl+LCouP5gtmvJ4dfCBH3O0FOasP8XQx1Qb706GaNrZ/mfjiWaf /Jq1L7jFvghORWNpNHkAVMDpmZriQtZSo49OI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:mime-version:content-type:content-transfer-encoding; b=O00xFYHEsNqhO9VuN9UTxTuigjQ608aV7eTDJ7j7NWm1ZPXHCV/3soalsevA0FDH5s YOre14Jzydrned5BlpWYRWziIjbystVh+ovPkRX93blTMLnO4pEq5d4M3uPCEhXdF0gh K6A9kDXvyypzQlIf03RIX/8lfKgVh4RA28hTI=
Received: by 10.216.156.193 with SMTP id m43mr5712733wek.11.1271616459458; Sun, 18 Apr 2010 11:47:39 -0700 (PDT)
Received: from [192.168.1.13] (host86-143-168-117.range86-143.btcentralplus.com [86.143.168.117]) by mx.google.com with ESMTPS id r29sm8418174wbv.3.2010.04.18.11.47.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 18 Apr 2010 11:47:38 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.24.0.100208
Date: Sun, 18 Apr 2010 19:47:34 +0100
Subject: Updated minutes from IETF 77
From: Giles Heron <giles.heron@gmail.com>
To: <l2vpn@ietf.org>
Message-ID: <C7F11256.3EFC8%giles.heron@gmail.com>
Thread-Topic: Updated minutes from IETF 77
Thread-Index: AcrfJ5uOxJXKRDCOd02ok1rIZAlKzA==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
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: Sun, 18 Apr 2010 18:47:51 -0000

Ok - so it'd help if I actually put some content in my email.

As Simon Delord helpfully pointed out the other day I missed the second half
of the meeting out when I posted these.

I've now updated the online minutes:

http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt

Giles




From hshah@force10networks.com  Mon Apr 19 11:52:45 2010
Return-Path: <hshah@force10networks.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 87EA23A69E6 for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 11:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level: 
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 rOsZLY-6z6GB for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 11:52:36 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id 124C33A683B for <l2vpn@ietf.org>; Mon, 19 Apr 2010 11:52:36 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Mon, 19 Apr 2010 11:52:27 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>, "karvind@enterasys.com" <karvind@enterasys.com>, "erosen@cisco.com" <erosen@cisco.com>, "giles.heron@gmail.com" <giles.heron@gmail.com>, "flefauch@cisco.com" <flefauch@cisco.com>
Date: Mon, 19 Apr 2010 11:52:29 -0700
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcreQOZoMOTYoSD3Suiy0Yz+cEpQuQBmcxbw
Message-ID: <34F81DE93A7AA840A6A3B1187BAD5FC80379CB89FC@EXCH-CLUSTER-10.force10networks.com>
References: <OFB91AE237.C7D1E90E-ON48257708.0050726D-48257708.0053D26F@zte.com.cn>
In-Reply-To: <OFB91AE237.C7D1E90E-ON48257708.0050726D-48257708.0053D26F@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_34F81DE93A7AA840A6A3B1187BAD5FC80379CB89FCEXCHCLUSTER10_"
MIME-Version: 1.0
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "shane@castlepoint.net" <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: Mon, 19 Apr 2010 18:52:45 -0000

--_000_34F81DE93A7AA840A6A3B1187BAD5FC80379CB89FCEXCHCLUSTER10_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for your comments..
Please see the response in line below.

/himanshu

From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
Sent: Saturday, April 17, 2010 11:16 AM
To: Himanshu Shah; karvind@enterasys.com; erosen@cisco.com; giles.heron@gma=
il.com; flefauch@cisco.com
Cc: shane@castlepoint.net; l2vpn@ietf.org
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09


Hi Himanshu and authors,
After reviewing draft-ietf-l2vpn-ipls-09, I have the following comments:
1. Section 2.0, point 5, bullet c, more precisely, the unicast ARP packets =
received from "multicast" pseudowire may do MAC DA lookup, and forward to w=
here CE is located. So the context should add this exception for ARP packet=
s
[Himanshu>] I am not sure I fully understand your comment, but I am guessin=
g you are asking to add text to the draft referring the unicast MAC and ARP=
 as the context
to the exception whereby normally all the packets received over "multicast"=
 PW are broadcasted, including this ARP unicast, but as an exception, in th=
is case, one
can optimize the flooding.
.
2. Section 7.1, I am wondering how to setup the unidirectional mp2p pseudow=
ire. According to RFC4447, one pseudowire will be UP only when both local a=
nd remote label mapping message is sent and received. But according to the =
descripition of unidirectional mp2p pseudowire in IPLS, if PEx sends a labe=
l mapping to PEy for CEx, PEy seems to consider the PW as UP when receiving=
 the corresponding label mapping, and PEx would consider the PW as UP when =
sending out the label mapping, without the necessarity of allocating local =
labels for the PW.
[Himanshu>] There is no one-to-one correspondence with respect to PW direct=
ionality. Meaning, if PE1 has two local CE, it will advertise two labels. I=
f PE2 has 4 local CEs it will advertise 4 labels.
Which does not mean that when PE1 receives 4 labels from PE2 that it needs =
to advertise 4 labels to bring PW 'UP'. So the question, is 'unidirectional=
' PW a deviation from RFC 4447 which
assumes PW to be bi-directional (this used to be true initially, not sure i=
f still is true) by way of uniting to opposite direction unidirectional PW.=
 The unidirectional PW is not illegal.

What's more, it is also difficult to configure the PWid. If PEx uses PWid_1=
 for CEx1, and PWid_2 for CEx2, according to section 7.1, the PEy needs to =
configure both PWid_1 and PWid_2, which is actually not necessary. Do I mis=
s something important here to understand the concept of unidirectional mp2p=
 pseudowire? There may be a new type of FEC that is required, similar with =
unidirectional P2MP PW.
[Himanshu>] PWid is per IPLS instance and not per CE. I do not see any text=
 in 7.1 which talks about configuring difference PWid for each CE.
For a given IPLS instance a PE has following to signal -

a)    PW id

b)    One MP2P 'multicast'  Ethernet PW

c)     Many (i.e. one per local CE) MP2P 'unicast' IP PW along with CE's MA=
C address
[Himanshu>] Section 7.1 describes details for send and receive processing o=
f label mapping message

3. Section 7.2, why not using LDP capability to advertising IPv6 stack capa=
bility?
[Himanshu>] Because this is specific to PW and IPLS instance

4. Will IPLS consider any spoke connectivity to increase the scalability, s=
ame as VPLS?
[Himanshu>] I am not sure I fully understand. IPLS assumes (recommends) tha=
t CEs are IP routers that act as edge box.
Meaning most of the customer's IP hosts and  other routers are behind this =
CE router in customer network and PE does
not see them. This by itself provides good hierarchy & scalability.




Hope to see your reply, thank you.

Best Regards
Lizhong Jin


------------------------------

Date: Mon, 5 Apr 2010 19:58:01 -0600
From: Shane Amante <shane@castlepoint.net>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09
To: l2vpn@ietf.org
Message-ID: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
Content-Type: text/plain; charset=3Dus-ascii

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane



--------------------------------------------------------

ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e not permitted to disclose the contents of this communication to others.

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 th=
e message. Any views expressed in this message are those of the individual =
sender.

This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--_000_34F81DE93A7AA840A6A3B1187BAD5FC80379CB89FCEXCHCLUSTER10_
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: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:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/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.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.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:"Trebuchet MS","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;}
 /* List Definitions */
 @list l0
	{mso-list-id:1763798036;
	mso-list-type:hybrid;
	mso-list-template-ids:-910525658 67698711 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Trebuchet=
 MS","sans-serif";
color:#1F497D'>Thanks for your comments..<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Trebuchet=
 MS","sans-serif";
color:#1F497D'>Please see the response in line below.<o:p></o:p></span></p>

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

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

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

<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"'>
lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn] <br>
<b>Sent:</b> Saturday, April 17, 2010 11:16 AM<br>
<b>To:</b> Himanshu Shah; karvind@enterasys.com; erosen@cisco.com;
giles.heron@gmail.com; flefauch@cisco.com<br>
<b>Cc:</b> shane@castlepoint.net; l2vpn@ietf.org<br>
<b>Subject:</b> Re: WG Last Call: draft-ietf-l2vpn-ipls-09<o:p></o:p></span=
></p>

</div>

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

<p class=3DMsoNormal><br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi Himans=
hu and
authors,</span> <br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>After rev=
iewing
draft-ietf-l2vpn-ipls-09, I have the following comments:<br>
1. Section 2.0, point 5, bullet c, more precisely, the unicast ARP packets
received from &quot;multicast&quot; pseudowire may do MAC DA lookup, and
forward to where CE is located. So the context should add this exception fo=
r
ARP packets<span style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>[Himanshu&gt;] I am not sure I fully understand your comment=
,
but I am guessing you are asking to add text to the draft referring the uni=
cast
MAC and ARP as the context<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>to the exception whereby normally all the packets received o=
ver &#8220;multicast&#8221;
PW are broadcasted, including this ARP unicast, but as an exception, in thi=
s
case, one<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>can optimize the flooding.<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>.</span>
<br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>2. Sectio=
n 7.1,
I am wondering how to setup the unidirectional mp2p pseudowire. According t=
o
RFC4447, one pseudowire will be UP only when both local and remote label
mapping message is sent and received. But according to the descripition of
unidirectional mp2p pseudowire in IPLS, if PEx sends a label mapping to PEy=
 for
CEx, PEy seems to consider the PW as UP when receiving the corresponding la=
bel
mapping, and PEx would consider the PW as UP when sending out the label
mapping, without the necessarity of allocating local labels for the PW.</sp=
an> <span
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>[Himanshu&gt;] There is no one-to-one correspondence with re=
spect
to PW directionality. Meaning, if PE1 has two local CE, it will advertise t=
wo
labels. If PE2 has 4 local CEs it will advertise 4 labels. <o:p></o:p></spa=
n></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>Which does not mean that when PE1 receives 4 labels from PE2
that it needs to advertise 4 labels to bring PW &#8216;UP&#8217;. So the
question, is &#8216;unidirectional&#8217; PW a deviation from RFC 4447 whic=
h <o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>assumes PW to be bi-directional (this used to be true initia=
lly,
not sure if still is true) by way of uniting to opposite direction unidirec=
tional
PW. The unidirectional PW is not illegal.<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>What's mo=
re, it
is also difficult to configure the PWid. If PEx uses PWid_1 for CEx1, and
PWid_2 for CEx2, according to section 7.1, the PEy needs to configure both
PWid_1 and PWid_2, which is actually not necessary. Do I miss something
important here to understand the concept of unidirectional mp2p pseudowire?
There may be a new type of FEC that is required, similar with unidirectiona=
l
P2MP PW.</span> <span style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>[Himanshu&gt;] PWid is per IPLS instance and not per CE. I d=
o
not see any text in 7.1 which talks about configuring difference PWid for e=
ach
CE.<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>For a given IPLS instance a PE has following to signal &#821=
1;<o:p></o:p></span></i></b></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><b><i><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F=
497D'><span
style=3D'mso-list:Ignore'>a)<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><b><i><span style=3D'font-size:10.0p=
t;
font-family:"Trebuchet MS","sans-serif";color:#1F497D'>PW id<o:p></o:p></sp=
an></i></b></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><b><i><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F=
497D'><span
style=3D'mso-list:Ignore'>b)<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><b><i><span style=3D'font-size:10.0p=
t;
font-family:"Trebuchet MS","sans-serif";color:#1F497D'>One MP2P &#8216;mult=
icast&#8217;
&nbsp;Ethernet PW<o:p></o:p></span></i></b></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><b><i><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F=
497D'><span
style=3D'mso-list:Ignore'>c)<span style=3D'font:7.0pt "Times New Roman"'>&n=
bsp;&nbsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><b><i><span style=3D'font-size:10.0p=
t;
font-family:"Trebuchet MS","sans-serif";color:#1F497D'>Many (i.e. one per l=
ocal
CE) MP2P &#8216;unicast&#8217; IP PW along with CE&#8217;s MAC address<o:p>=
</o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Himanshu&gt;] </s=
pan></i></b><span
style=3D'color:#1F497D'>Section 7.1 describes details for send and receive
processing of label mapping message<o:p></o:p></span></p>

<p class=3DMsoNormal><br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>3. Sectio=
n 7.2,
why not using LDP capability to advertising IPv6 stack capability?</span> <=
span
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>[Himanshu&gt;] Because this is specific to PW and IPLS insta=
nce<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>4. Will I=
PLS
consider any spoke connectivity to increase the scalability, same as VPLS?<=
/span>
<span style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>[Himanshu&gt;] I am not sure I fully understand. IPLS assume=
s
(recommends) that CEs are IP routers that act as edge box.<o:p></o:p></span=
></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>Meaning most of the customer&#8217;s IP hosts and &nbsp;othe=
r
routers are behind this CE router in customer network and PE does<o:p></o:p=
></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'>not see them. This by itself provides good hierarchy &amp; s=
calability.
<o:p></o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></i></b></p>

<p class=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;font-family:"Tre=
buchet MS","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></i></b></p>

<p class=3DMsoNormal><br>
<br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Hope to s=
ee
your reply, thank you.</span> <br>
<br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Best Rega=
rds</span>
<br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Lizhong J=
in</span>
<br>
<span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>&nbsp;</sp=
an> <br>
<br>
<tt><span style=3D'font-size:10.0pt'>------------------------------</span><=
/tt><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<br>
<tt>Date: Mon, 5 Apr 2010 19:58:01 -0600</tt><br>
<tt>From: Shane Amante &lt;shane@castlepoint.net&gt;</tt><br>
<tt>Subject: WG Last Call: draft-ietf-l2vpn-ipls-09</tt><br>
<tt>To: l2vpn@ietf.org</tt><br>
<tt>Message-ID: &lt;7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net&gt=
;</tt><br>
<tt>Content-Type: text/plain; charset=3Dus-ascii</tt><br>
<br>
<tt>Hi Everyone,</tt><br>
<br>
<tt>This is to begin a (final) WG Last Call on:</tt><br>
<tt>http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09</tt><br>
<br>
<tt>If you have substantial technical comments or concerns, please share th=
em
with the list. &nbsp;If you have editorial comments, please share them dire=
ctly
with the authors and co-chairs.</tt><br>
<br>
<tt>So far, we have the following folks signed up for a thorough review and
comments:</tt><br>
<tt>- Andy Malis</tt><br>
<tt>- Nick DelRegno</tt><br>
<tt>- Pranjal Dutta</tt><br>
<tt>However, we could use more people to conduct a review. &nbsp;If you hav=
e
the time and/or inclination, please let the chairs know if you'll be conduc=
ting
a review.</tt><br>
<br>
<tt>The Last Call on this draft will also end on April 23.</tt><br>
<br>
<tt>Thanks,</tt><br>
<br>
<tt>Giles &amp; Shane</tt></span><o:p></o:p></p>

<pre><o:p>&nbsp;</o:p></pre><pre>------------------------------------------=
--------------<o:p></o:p></pre><pre>ZTE&nbsp;Information&nbsp;Security&nbsp=
;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;ma=
il&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;or=
ganization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidentia=
l.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nb=
sp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&=
nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&n=
bsp;to&nbsp;others.<o:p></o:p></pre><pre>This&nbsp;email&nbsp;and&nbsp;any&=
nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nb=
sp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;th=
e&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&=
nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;ema=
il&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp=
;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;=
this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp=
;sender.<o:p></o:p></pre><pre>This&nbsp;message&nbsp;has&nbsp;been&nbsp;sca=
nned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Sp=
am&nbsp;system.<o:p></o:p></pre></div>

</body>

</html>

--_000_34F81DE93A7AA840A6A3B1187BAD5FC80379CB89FCEXCHCLUSTER10_--

From hshah@force10networks.com  Mon Apr 19 12:43:46 2010
Return-Path: <hshah@force10networks.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 D21853A68AB for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 12:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level: 
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_50=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 BUzw8oD0lwmX for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 12:43:46 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id EA8463A683C for <l2vpn@ietf.org>; Mon, 19 Apr 2010 12:43:41 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Mon, 19 Apr 2010 12:43:33 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: PAULING JOEL <Joel.Pauling@alcatel-lucent.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Mon, 19 Apr 2010 12:43:36 -0700
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLKV0PSguv1yOSDSMtyd3zpMAzQABQgJQArEKIyA=
Message-ID: <34F81DE93A7AA840A6A3B1187BAD5FC80379CB8A11@EXCH-CLUSTER-10.force10networks.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net> <D434F7EE545145439BFA47601F9B2BA302F6ACAB@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <D434F7EE545145439BFA47601F9B2BA302F6ACAB@SGSINSMBS02.ad4.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-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, 19 Apr 2010 19:43:46 -0000

Hi Joel -
Thanks for your comment.

While you make a good a point, here is what my thinking behind it.

IPLS was designed originally for IPv4 and existed for a long time before
support of IPv6 added. If there is any implementation out there, they
have IPv4 support for it and would like to see a newer implementation
be compatible with existing.

Secondly, it is always desirable that an RFC provide 'a base version' that =
is
at minimum be compatible and interoperable with other implementations.

Nonetheless, you make a good point and would like to hear from other
members of the WG that entertain a possibility of IPv6 only IPLS (a possibi=
lity, with
a fallback tunable option).

Regards,
himanshu


-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of P=
AULING JOEL
Sent: Monday, April 05, 2010 10:40 PM
To: l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Looks good.=20

One comment:=20

Re fallback protocol (proposed to be IPv4) should be a tuneable option. Whi=
le the V6 compatibility flag currently signals v6 stack compatibility on th=
e tunnel end point, I would prefer from a future proofing perspective if th=
e fallback protocol was definable.=20

Especially in MPLS PE-PE scenarios, it is preferable to run either IPV4 + M=
PLS OR IPV6 + MPLS, rather than both through a MS core network (reducing ad=
min overhead by having to maintain two stacks). Having fallback protocol be=
 a tuneable option will cater to this scenario better than current proposed=
 draft.


Kind regards


Joel W Pauling

Network Capability Engineer
Alcatel-Lucent New Zealand
+64 4 803 7639
+64 21 171 8049
joel.pauling@alcatel-lucent.com

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Tuesday, 6 April 2010 1:58 p.m.
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From lizhong.jin@zte.com.cn  Mon Apr 19 18:25:33 2010
Return-Path: <lizhong.jin@zte.com.cn>
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 E55F83A6964 for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 18:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.885
X-Spam-Level: 
X-Spam-Status: No, score=-96.885 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VyJks0s9NRfd for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 18:25:29 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 87D043A67B4 for <l2vpn@ietf.org>; Mon, 19 Apr 2010 18:25:26 -0700 (PDT)
Received: from [10.30.17.99] by mx6.zte.com.cn with surfront esmtp id 58071577109098; Tue, 20 Apr 2010 09:22:20 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 83532.6570126373; Tue, 20 Apr 2010 09:25:08 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o3K1OkpG007590; Tue, 20 Apr 2010 09:24:47 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <34F81DE93A7AA840A6A3B1187BAD5FC80379CB89FC@EXCH-CLUSTER-10.force10networks.com>
To: Himanshu Shah <hshah@force10networks.com>
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF9ED45CDA.DCB1F1E3-ON4825770B.0003AD91-4825770B.0007C02E@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Tue, 20 Apr 2010 09:24:39 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-20 09:24:43, Serialize complete at 2010-04-20 09:24:43
Content-Type: multipart/alternative; boundary="=_alternative 0007C02B4825770B_="
X-MAIL: mse2.zte.com.cn o3K1OkpG007590
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "flefauch@cisco.com" <flefauch@cisco.com>, lmartini@cisco.com, "giles.heron@gmail.com" <giles.heron@gmail.com>, "shane@castlepoint.net" <shane@castlepoint.net>, "erosen@cisco.com" <erosen@cisco.com>, "karvind@enterasys.com" <karvind@enterasys.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: Tue, 20 Apr 2010 01:25:33 -0000

This is a multipart message in MIME format.
--=_alternative 0007C02B4825770B_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgSGltYW5zaHUsDQpUaGFuayB5b3UgZm9yIHlvdXIgcmVwbHkuIFBsZWFzZSBzZWUgbXkgY29t
bWVudHMgaW4gbGluZS4NCg0KQlINCkxpemhvbmcgSmluDQogDQoNCg0KSGltYW5zaHUgU2hhaCA8
aHNoYWhAZm9yY2UxMG5ldHdvcmtzLmNvbT4gDQoyMDEwLTA0LTIwIDAyOjUyDQoNClRvDQoibGl6
aG9uZy5qaW5AenRlLmNvbS5jbiIgPGxpemhvbmcuamluQHp0ZS5jb20uY24+LCAia2FydmluZEBl
bnRlcmFzeXMuY29tIiANCjxrYXJ2aW5kQGVudGVyYXN5cy5jb20+LCAiZXJvc2VuQGNpc2NvLmNv
bSIgPGVyb3NlbkBjaXNjby5jb20+LCANCiJnaWxlcy5oZXJvbkBnbWFpbC5jb20iIDxnaWxlcy5o
ZXJvbkBnbWFpbC5jb20+LCAiZmxlZmF1Y2hAY2lzY28uY29tIiANCjxmbGVmYXVjaEBjaXNjby5j
b20+DQpjYw0KInNoYW5lQGNhc3RsZXBvaW50Lm5ldCIgPHNoYW5lQGNhc3RsZXBvaW50Lm5ldD4s
ICJsMnZwbkBpZXRmLm9yZyIgDQo8bDJ2cG5AaWV0Zi5vcmc+DQpTdWJqZWN0DQpSRTogV0cgTGFz
dCBDYWxsOiBkcmFmdC1pZXRmLWwydnBuLWlwbHMtMDkNCg0KDQoNCg0KDQoNClRoYW5rcyBmb3Ig
eW91ciBjb21tZW50cy4uDQpQbGVhc2Ugc2VlIHRoZSByZXNwb25zZSBpbiBsaW5lIGJlbG93Lg0K
IA0KL2hpbWFuc2h1DQogDQpGcm9tOiBsaXpob25nLmppbkB6dGUuY29tLmNuIFttYWlsdG86bGl6
aG9uZy5qaW5AenRlLmNvbS5jbl0gDQpTZW50OiBTYXR1cmRheSwgQXByaWwgMTcsIDIwMTAgMTE6
MTYgQU0NClRvOiBIaW1hbnNodSBTaGFoOyBrYXJ2aW5kQGVudGVyYXN5cy5jb207IGVyb3NlbkBj
aXNjby5jb207IA0KZ2lsZXMuaGVyb25AZ21haWwuY29tOyBmbGVmYXVjaEBjaXNjby5jb20NCkNj
OiBzaGFuZUBjYXN0bGVwb2ludC5uZXQ7IGwydnBuQGlldGYub3JnDQpTdWJqZWN0OiBSZTogV0cg
TGFzdCBDYWxsOiBkcmFmdC1pZXRmLWwydnBuLWlwbHMtMDkNCiANCg0KSGkgSGltYW5zaHUgYW5k
IGF1dGhvcnMsIA0KQWZ0ZXIgcmV2aWV3aW5nIGRyYWZ0LWlldGYtbDJ2cG4taXBscy0wOSwgSSBo
YXZlIHRoZSBmb2xsb3dpbmcgY29tbWVudHM6DQoxLiBTZWN0aW9uIDIuMCwgcG9pbnQgNSwgYnVs
bGV0IGMsIG1vcmUgcHJlY2lzZWx5LCB0aGUgdW5pY2FzdCBBUlAgcGFja2V0cyANCnJlY2VpdmVk
IGZyb20gIm11bHRpY2FzdCIgcHNldWRvd2lyZSBtYXkgZG8gTUFDIERBIGxvb2t1cCwgYW5kIGZv
cndhcmQgdG8gDQp3aGVyZSBDRSBpcyBsb2NhdGVkLiBTbyB0aGUgY29udGV4dCBzaG91bGQgYWRk
IHRoaXMgZXhjZXB0aW9uIGZvciBBUlAgDQpwYWNrZXRzDQpbSGltYW5zaHU+XSBJIGFtIG5vdCBz
dXJlIEkgZnVsbHkgdW5kZXJzdGFuZCB5b3VyIGNvbW1lbnQsIGJ1dCBJIGFtIA0KZ3Vlc3Npbmcg
eW91IGFyZSBhc2tpbmcgdG8gYWRkIHRleHQgdG8gdGhlIGRyYWZ0IHJlZmVycmluZyB0aGUgdW5p
Y2FzdCBNQUMgDQphbmQgQVJQIGFzIHRoZSBjb250ZXh0DQp0byB0aGUgZXhjZXB0aW9uIHdoZXJl
Ynkgbm9ybWFsbHkgYWxsIHRoZSBwYWNrZXRzIHJlY2VpdmVkIG92ZXIgobANCm11bHRpY2FzdKGx
IFBXIGFyZSBicm9hZGNhc3RlZCwgaW5jbHVkaW5nIHRoaXMgQVJQIHVuaWNhc3QsIGJ1dCBhcyBh
biANCmV4Y2VwdGlvbiwgaW4gdGhpcyBjYXNlLCBvbmUNCmNhbiBvcHRpbWl6ZSB0aGUgZmxvb2Rp
bmcuDQpbTGl6aG9uZ10gWWVzLCB0aGF0J3MgZXhhY3RseSB3aGF0IEkgbWVhbi4NCi4gDQoyLiBT
ZWN0aW9uIDcuMSwgSSBhbSB3b25kZXJpbmcgaG93IHRvIHNldHVwIHRoZSB1bmlkaXJlY3Rpb25h
bCBtcDJwIA0KcHNldWRvd2lyZS4gQWNjb3JkaW5nIHRvIFJGQzQ0NDcsIG9uZSBwc2V1ZG93aXJl
IHdpbGwgYmUgVVAgb25seSB3aGVuIGJvdGggDQpsb2NhbCBhbmQgcmVtb3RlIGxhYmVsIG1hcHBp
bmcgbWVzc2FnZSBpcyBzZW50IGFuZCByZWNlaXZlZC4gQnV0IGFjY29yZGluZyANCnRvIHRoZSBk
ZXNjcmlwaXRpb24gb2YgdW5pZGlyZWN0aW9uYWwgbXAycCBwc2V1ZG93aXJlIGluIElQTFMsIGlm
IFBFeCANCnNlbmRzIGEgbGFiZWwgbWFwcGluZyB0byBQRXkgZm9yIENFeCwgUEV5IHNlZW1zIHRv
IGNvbnNpZGVyIHRoZSBQVyBhcyBVUCANCndoZW4gcmVjZWl2aW5nIHRoZSBjb3JyZXNwb25kaW5n
IGxhYmVsIG1hcHBpbmcsIGFuZCBQRXggd291bGQgY29uc2lkZXIgdGhlIA0KUFcgYXMgVVAgd2hl
biBzZW5kaW5nIG91dCB0aGUgbGFiZWwgbWFwcGluZywgd2l0aG91dCB0aGUgbmVjZXNzYXJpdHkg
b2YgDQphbGxvY2F0aW5nIGxvY2FsIGxhYmVscyBmb3IgdGhlIFBXLiANCltIaW1hbnNodT5dIFRo
ZXJlIGlzIG5vIG9uZS10by1vbmUgY29ycmVzcG9uZGVuY2Ugd2l0aCByZXNwZWN0IHRvIFBXIA0K
ZGlyZWN0aW9uYWxpdHkuIE1lYW5pbmcsIGlmIFBFMSBoYXMgdHdvIGxvY2FsIENFLCBpdCB3aWxs
IGFkdmVydGlzZSB0d28gDQpsYWJlbHMuIElmIFBFMiBoYXMgNCBsb2NhbCBDRXMgaXQgd2lsbCBh
ZHZlcnRpc2UgNCBsYWJlbHMuIA0KV2hpY2ggZG9lcyBub3QgbWVhbiB0aGF0IHdoZW4gUEUxIHJl
Y2VpdmVzIDQgbGFiZWxzIGZyb20gUEUyIHRoYXQgaXQgbmVlZHMgDQp0byBhZHZlcnRpc2UgNCBs
YWJlbHMgdG8gYnJpbmcgUFcgoa5VUKGvLiBTbyB0aGUgcXVlc3Rpb24sIGlzIKGuDQp1bmlkaXJl
Y3Rpb25hbKGvIFBXIGEgZGV2aWF0aW9uIGZyb20gUkZDIDQ0NDcgd2hpY2ggDQphc3N1bWVzIFBX
IHRvIGJlIGJpLWRpcmVjdGlvbmFsICh0aGlzIHVzZWQgdG8gYmUgdHJ1ZSBpbml0aWFsbHksIG5v
dCBzdXJlIA0KaWYgc3RpbGwgaXMgdHJ1ZSkgYnkgd2F5IG9mIHVuaXRpbmcgdG8gb3Bwb3NpdGUg
ZGlyZWN0aW9uIHVuaWRpcmVjdGlvbmFsIA0KUFcuIFRoZSB1bmlkaXJlY3Rpb25hbCBQVyBpcyBu
b3QgaWxsZWdhbC4NCltMaXpob25nXSBGcm9tIG15IHVuZGVyc3RhbmRpbmcsIHVuaWRpcmVjdGlv
bmFsIHBvaW50LXRvLXBvaW50IFBXIGlzIG5vdCANCmRlZmluZWQgaW4gUkZDNDQ0Ny4gU2VlIHNl
Y3Rpb24gNS4zLjMgc2lnbmFsaW5nIHByb2NlZHVyZXMgaW4gUkZDNDQ0Ny4NCg0KV2hhdCdzIG1v
cmUsIGl0IGlzIGFsc28gZGlmZmljdWx0IHRvIGNvbmZpZ3VyZSB0aGUgUFdpZC4gSWYgUEV4IHVz
ZXMgDQpQV2lkXzEgZm9yIENFeDEsIGFuZCBQV2lkXzIgZm9yIENFeDIsIGFjY29yZGluZyB0byBz
ZWN0aW9uIDcuMSwgdGhlIFBFeSANCm5lZWRzIHRvIGNvbmZpZ3VyZSBib3RoIFBXaWRfMSBhbmQg
UFdpZF8yLCB3aGljaCBpcyBhY3R1YWxseSBub3QgDQpuZWNlc3NhcnkuIERvIEkgbWlzcyBzb21l
dGhpbmcgaW1wb3J0YW50IGhlcmUgdG8gdW5kZXJzdGFuZCB0aGUgY29uY2VwdCBvZiANCnVuaWRp
cmVjdGlvbmFsIG1wMnAgcHNldWRvd2lyZT8gVGhlcmUgbWF5IGJlIGEgbmV3IHR5cGUgb2YgRkVD
IHRoYXQgaXMgDQpyZXF1aXJlZCwgc2ltaWxhciB3aXRoIHVuaWRpcmVjdGlvbmFsIFAyTVAgUFcu
IA0KW0hpbWFuc2h1Pl0gUFdpZCBpcyBwZXIgSVBMUyBpbnN0YW5jZSBhbmQgbm90IHBlciBDRS4g
SSBkbyBub3Qgc2VlIGFueSANCnRleHQgaW4gNy4xIHdoaWNoIHRhbGtzIGFib3V0IGNvbmZpZ3Vy
aW5nIGRpZmZlcmVuY2UgUFdpZCBmb3IgZWFjaCBDRS4NCkZvciBhIGdpdmVuIElQTFMgaW5zdGFu
Y2UgYSBQRSBoYXMgZm9sbG93aW5nIHRvIHNpZ25hbCCoQw0KYSkgICAgUFcgaWQNCmIpICAgIE9u
ZSBNUDJQIKGubXVsdGljYXN0oa8gIEV0aGVybmV0IFBXDQpjKSAgICAgTWFueSAoaS5lLiBvbmUg
cGVyIGxvY2FsIENFKSBNUDJQIKGudW5pY2FzdKGvIElQIFBXIGFsb25nIHdpdGggQ0Whrw0KcyBN
QUMgYWRkcmVzcw0KW0hpbWFuc2h1Pl0gU2VjdGlvbiA3LjEgZGVzY3JpYmVzIGRldGFpbHMgZm9y
IHNlbmQgYW5kIHJlY2VpdmUgcHJvY2Vzc2luZyANCm9mIGxhYmVsIG1hcHBpbmcgbWVzc2FnZQ0K
W0xpemhvbmddIERvIHlvdSBtZWFuIFBFIHdpbGwgYWR2ZXJ0aXNlIGFsbCBsYWJlbHMgZm9yIENF
cyB3aXRoIHNhbWUgUFdpZD8gDQpUaGVuIHRoYXQgbWVhbnMgUEUgd2lsbCBhZHZlcnRpc2UgZGlm
ZmVyZW50IGxhYmVscyBmb3Igc2FtZSBGRUMoc2FtZSANClBXaWQpLCB3aGljaCB3aWxsIG5vdCBv
cGVyYXRlIGNvcnJlY3RseSB1bmRlciBjdXJyZW50IGZyYW1ld29yay4gVGhlIHBlZXIgDQpQRSBy
ZWNlaXZpbmcgc2V2ZXJhbCBsYWJlbCBtYXBwaW5nIG1lc3NhZ2VzIHdpdGggc2FtZSBGRUMgYnV0
IGRpZmZlcmVudCANCmxhYmVscyB3aWxsIHVwZGF0ZSB0aGUgYWxyZWFkeSByZWNlaXZlZCBsYWJl
bCwgYW5kIG9ubHkgcmV0YWluIHRoZSBuZXdlc3QgDQpvbmUuIFRoZSB3YXkgdG8gc29sdmUgdGhp
cyBpcyB0byBkZWZpbmUgYSBuZXcgdHlwZSBvZiBGRUMgdG8gc3BlY2lmeSANCmRpZmZlcmVudCBv
cGVyYXRpb24gY29tcGFyaW5nIHdpdGggbm9ybWFsIEZFQyAoZS5nLCB0eXBlIDEyOCBhbmQgMTI5
KS4NCg0KMy4gU2VjdGlvbiA3LjIsIHdoeSBub3QgdXNpbmcgTERQIGNhcGFiaWxpdHkgdG8gYWR2
ZXJ0aXNpbmcgSVB2NiBzdGFjayANCmNhcGFiaWxpdHk/IA0KW0hpbWFuc2h1Pl0gQmVjYXVzZSB0
aGlzIGlzIHNwZWNpZmljIHRvIFBXIGFuZCBJUExTIGluc3RhbmNlDQpbTGl6aG9uZ10gYWN0dWFs
bHksIGN1cnJlbnQgUDJNUCBQVyBjYXBhYmlsaXR5IG5lZ290aWF0aW9uIHVzZXMgTERQIA0KY2Fw
YWJpbGl0eS4gSSBob3BlIHdlIGNhbiBhbGlnbiB0aGlzLCBiZWNhdXNlIGJvdGggYXJlIHJlbGF0
ZWQgd2l0aCBQVyANCmNhcGFiaWxpdHkuDQoNCjQuIFdpbGwgSVBMUyBjb25zaWRlciBhbnkgc3Bv
a2UgY29ubmVjdGl2aXR5IHRvIGluY3JlYXNlIHRoZSBzY2FsYWJpbGl0eSwgDQpzYW1lIGFzIFZQ
TFM/IA0KW0hpbWFuc2h1Pl0gSSBhbSBub3Qgc3VyZSBJIGZ1bGx5IHVuZGVyc3RhbmQuIElQTFMg
YXNzdW1lcyAocmVjb21tZW5kcykgDQp0aGF0IENFcyBhcmUgSVAgcm91dGVycyB0aGF0IGFjdCBh
cyBlZGdlIGJveC4NCk1lYW5pbmcgbW9zdCBvZiB0aGUgY3VzdG9tZXKhr3MgSVAgaG9zdHMgYW5k
ICBvdGhlciByb3V0ZXJzIGFyZSBiZWhpbmQgDQp0aGlzIENFIHJvdXRlciBpbiBjdXN0b21lciBu
ZXR3b3JrIGFuZCBQRSBkb2VzDQpub3Qgc2VlIHRoZW0uIFRoaXMgYnkgaXRzZWxmIHByb3ZpZGVz
IGdvb2QgaGllcmFyY2h5ICYgc2NhbGFiaWxpdHkuIA0KW0xpemhvbmddIFNvcnJ5IGZvciB0aGUg
dW5jbGVhciBzdGF0ZW1lbnQuIFRoZSBzY2FsYWJpbGl0eSBJIHJlZmVyIGlzIFBXIA0Kc2NhbGFi
bGl0eSB0byBjb25zdHJ1Y3QgbGFyZ2UgSVBMUyBuZXR3b3JrLCB3aGljaCBpcyBpbmNsdWRlZCBp
biBSRkM0NzYyIA0Kc2VjdGlvbiAxMC4xLjEuIA0KDQpIb3BlIHRvIHNlZSB5b3VyIHJlcGx5LCB0
aGFuayB5b3UuIA0KDQpCZXN0IFJlZ2FyZHMgDQpMaXpob25nIEppbiANCiAgDQoNCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpEYXRlOiBNb24sIDUgQXByIDIwMTAgMTk6NTg6MDEg
LTA2MDANCkZyb206IFNoYW5lIEFtYW50ZSA8c2hhbmVAY2FzdGxlcG9pbnQubmV0Pg0KU3ViamVj
dDogV0cgTGFzdCBDYWxsOiBkcmFmdC1pZXRmLWwydnBuLWlwbHMtMDkNClRvOiBsMnZwbkBpZXRm
Lm9yZw0KTWVzc2FnZS1JRDogPDdCNkM1MDQwLUMxMDMtNDYyNi04M0Y4LTYxODMzMUY2OEJDRUBj
YXN0bGVwb2ludC5uZXQ+DQpDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9dXMtYXNj
aWkNCg0KSGkgRXZlcnlvbmUsDQoNClRoaXMgaXMgdG8gYmVnaW4gYSAoZmluYWwpIFdHIExhc3Qg
Q2FsbCBvbjoNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbDJ2cG4taXBs
cy0wOQ0KDQpJZiB5b3UgaGF2ZSBzdWJzdGFudGlhbCB0ZWNobmljYWwgY29tbWVudHMgb3IgY29u
Y2VybnMsIHBsZWFzZSBzaGFyZSB0aGVtIA0Kd2l0aCB0aGUgbGlzdC4gIElmIHlvdSBoYXZlIGVk
aXRvcmlhbCBjb21tZW50cywgcGxlYXNlIHNoYXJlIHRoZW0gZGlyZWN0bHkgDQp3aXRoIHRoZSBh
dXRob3JzIGFuZCBjby1jaGFpcnMuDQoNClNvIGZhciwgd2UgaGF2ZSB0aGUgZm9sbG93aW5nIGZv
bGtzIHNpZ25lZCB1cCBmb3IgYSB0aG9yb3VnaCByZXZpZXcgYW5kIA0KY29tbWVudHM6DQotIEFu
ZHkgTWFsaXMNCi0gTmljayBEZWxSZWdubw0KLSBQcmFuamFsIER1dHRhDQpIb3dldmVyLCB3ZSBj
b3VsZCB1c2UgbW9yZSBwZW9wbGUgdG8gY29uZHVjdCBhIHJldmlldy4gIElmIHlvdSBoYXZlIHRo
ZSANCnRpbWUgYW5kL29yIGluY2xpbmF0aW9uLCBwbGVhc2UgbGV0IHRoZSBjaGFpcnMga25vdyBp
ZiB5b3UnbGwgYmUgDQpjb25kdWN0aW5nIGEgcmV2aWV3Lg0KDQpUaGUgTGFzdCBDYWxsIG9uIHRo
aXMgZHJhZnQgd2lsbCBhbHNvIGVuZCBvbiBBcHJpbCAyMy4NCg0KVGhhbmtzLA0KDQpHaWxlcyAm
IFNoYW5lDQogDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KWlRFIEluZm9ybWF0aW9uIFNlY3VyaXR5IE5vdGljZTogVGhlIGluZm9ybWF0
aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMgDQpzb2xlbHkgcHJvcGVydHkgb2YgdGhlIHNl
bmRlcidzIG9yZ2FuaXphdGlvbi4gVGhpcyBtYWlsIGNvbW11bmljYXRpb24gaXMgDQpjb25maWRl
bnRpYWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZCB0byBtYWludGFpbiBz
ZWNyZWN5IGFuZCANCmFyZSBub3QgcGVybWl0dGVkIHRvIGRpc2Nsb3NlIHRoZSBjb250ZW50cyBv
ZiB0aGlzIGNvbW11bmljYXRpb24gdG8gDQpvdGhlcnMuDQpUaGlzIGVtYWlsIGFuZCBhbnkgZmls
ZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCANCnNv
bGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hvbSB0aGV5
IGFyZSBhZGRyZXNzZWQuIA0KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJv
ciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIA0KdGhlIG1lc3NhZ2UuIEFueSB2aWV3
cyBleHByZXNzZWQgaW4gdGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBvZiB0aGUgDQppbmRpdmlkdWFs
IHNlbmRlci4NClRoaXMgbWVzc2FnZSBoYXMgYmVlbiBzY2FubmVkIGZvciB2aXJ1c2VzIGFuZCBT
cGFtIGJ5IFpURSBBbnRpLVNwYW0gDQpzeXN0ZW0uDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFIEluZm9ybWF0aW9uIFNl
Y3VyaXR5IE5vdGljZTogVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMg
c29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBj
b21tdW5pY2F0aW9uIGlzIGNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1lZCBhYm92ZSBhcmUg
b2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVybWl0dGVkIHRvIGRp
c2Nsb3NlIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8gb3RoZXJzLg0KVGhp
cyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlh
bCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVu
dGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBtZXNz
YWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2YgdGhl
IGluZGl2aWR1YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5uZWQgZm9yIHZp
cnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uDQo=
--=_alternative 0007C02B4825770B_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIEhpbWFuc2h1LDwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+VGhhbmsgeW91IGZvciB5b3VyIHJl
cGx5LiBQbGVhc2Ugc2VlDQpteSBjb21tZW50cyBpbiBsaW5lLjwvZm9udD4NCjxicj4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+QlI8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9InNhbnMtc2VyaWYiPkxpemhvbmcgSmluPC9mb250Pg0KPGJyPjxmb250IHNpemU9MSBm
YWNlPSJBcmlhbCI+Jm5ic3A7PC9mb250Pg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+
DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zMyU+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPjxiPkhpbWFuc2h1IFNoYWggJmx0O2hzaGFoQGZvcmNlMTBuZXR3b3Jrcy5jb20mZ3Q7
PC9iPg0KPC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjIwMTAtMDQt
MjAgMDI6NTI8L2ZvbnQ+DQo8dGQgd2lkdGg9NjYlPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIg
dmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNh
bnMtc2VyaWYiPlRvPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNl
cmlmIj4mcXVvdDtsaXpob25nLmppbkB6dGUuY29tLmNuJnF1b3Q7ICZsdDtsaXpob25nLmppbkB6
dGUuY29tLmNuJmd0OywNCiZxdW90O2thcnZpbmRAZW50ZXJhc3lzLmNvbSZxdW90OyAmbHQ7a2Fy
dmluZEBlbnRlcmFzeXMuY29tJmd0OywgJnF1b3Q7ZXJvc2VuQGNpc2NvLmNvbSZxdW90Ow0KJmx0
O2Vyb3NlbkBjaXNjby5jb20mZ3Q7LCAmcXVvdDtnaWxlcy5oZXJvbkBnbWFpbC5jb20mcXVvdDsg
Jmx0O2dpbGVzLmhlcm9uQGdtYWlsLmNvbSZndDssDQomcXVvdDtmbGVmYXVjaEBjaXNjby5jb20m
cXVvdDsgJmx0O2ZsZWZhdWNoQGNpc2NvLmNvbSZndDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4N
Cjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPmNj
PC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4mcXVvdDtz
aGFuZUBjYXN0bGVwb2ludC5uZXQmcXVvdDsgJmx0O3NoYW5lQGNhc3RsZXBvaW50Lm5ldCZndDss
DQomcXVvdDtsMnZwbkBpZXRmLm9yZyZxdW90OyAmbHQ7bDJ2cG5AaWV0Zi5vcmcmZ3Q7PC9mb250
Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBm
YWNlPSJzYW5zLXNlcmlmIj5TdWJqZWN0PC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBm
YWNlPSJzYW5zLXNlcmlmIj5SRTogV0cgTGFzdCBDYWxsOiBkcmFmdC1pZXRmLWwydnBuLWlwbHMt
MDk8L2ZvbnQ+PC90YWJsZT4NCjxicj4NCjx0YWJsZT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0K
PHRkPjwvdGFibGU+DQo8YnI+PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48Zm9udCBzaXplPTIg
Y29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQgTVMiPlRoYW5rcyBmb3IgeW91ciBjb21tZW50
cy4uPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hl
dCBNUyI+UGxlYXNlIHNlZSB0aGUgcmVzcG9uc2UNCmluIGxpbmUgYmVsb3cuPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+Jm5ic3A7PC9m
b250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+
L2hpbWFuc2h1PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IlRy
ZWJ1Y2hldCBNUyI+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJUYWhvbWEi
PjxiPkZyb206PC9iPiBsaXpob25nLmppbkB6dGUuY29tLmNuIFttYWlsdG86bGl6aG9uZy5qaW5A
enRlLmNvbS5jbl0NCjxiPjxicj4NClNlbnQ6PC9iPiBTYXR1cmRheSwgQXByaWwgMTcsIDIwMTAg
MTE6MTYgQU08Yj48YnI+DQpUbzo8L2I+IEhpbWFuc2h1IFNoYWg7IGthcnZpbmRAZW50ZXJhc3lz
LmNvbTsgZXJvc2VuQGNpc2NvLmNvbTsgZ2lsZXMuaGVyb25AZ21haWwuY29tOw0KZmxlZmF1Y2hA
Y2lzY28uY29tPGI+PGJyPg0KQ2M6PC9iPiBzaGFuZUBjYXN0bGVwb2ludC5uZXQ7IGwydnBuQGll
dGYub3JnPGI+PGJyPg0KU3ViamVjdDo8L2I+IFJlOiBXRyBMYXN0IENhbGw6IGRyYWZ0LWlldGYt
bDJ2cG4taXBscy0wOTwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJv
bWFuIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj48YnI+DQpI
aSBIaW1hbnNodSBhbmQgYXV0aG9ycyw8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5l
dyBSb21hbiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPjxicj4NCkFmdGVyIHJl
dmlld2luZyBkcmFmdC1pZXRmLWwydnBuLWlwbHMtMDksIEkgaGF2ZSB0aGUgZm9sbG93aW5nIGNv
bW1lbnRzOjxicj4NCjEuIFNlY3Rpb24gMi4wLCBwb2ludCA1LCBidWxsZXQgYywgbW9yZSBwcmVj
aXNlbHksIHRoZSB1bmljYXN0IEFSUCBwYWNrZXRzDQpyZWNlaXZlZCBmcm9tICZxdW90O211bHRp
Y2FzdCZxdW90OyBwc2V1ZG93aXJlIG1heSBkbyBNQUMgREEgbG9va3VwLCBhbmQNCmZvcndhcmQg
dG8gd2hlcmUgQ0UgaXMgbG9jYXRlZC4gU28gdGhlIGNvbnRleHQgc2hvdWxkIGFkZCB0aGlzIGV4
Y2VwdGlvbg0KZm9yIEFSUCBwYWNrZXRzPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0j
MWY0OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+W0hpbWFuc2h1Jmd0O10NCkkgYW0gbm90
IHN1cmUgSSBmdWxseSB1bmRlcnN0YW5kIHlvdXIgY29tbWVudCwgYnV0IEkgYW0gZ3Vlc3Npbmcg
eW91IGFyZQ0KYXNraW5nIHRvIGFkZCB0ZXh0IHRvIHRoZSBkcmFmdCByZWZlcnJpbmcgdGhlIHVu
aWNhc3QgTUFDIGFuZCBBUlAgYXMgdGhlDQpjb250ZXh0PC9pPjwvYj48L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT50byB0aGUg
ZXhjZXB0aW9uDQp3aGVyZWJ5IG5vcm1hbGx5IGFsbCB0aGUgcGFja2V0cyByZWNlaXZlZCBvdmVy
IKGwbXVsdGljYXN0obEgUFcgYXJlIGJyb2FkY2FzdGVkLA0KaW5jbHVkaW5nIHRoaXMgQVJQIHVu
aWNhc3QsIGJ1dCBhcyBhbiBleGNlcHRpb24sIGluIHRoaXMgY2FzZSwgb25lPC9pPjwvYj48L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48
Yj48aT5jYW4gb3B0aW1pemUgdGhlDQpmbG9vZGluZy48L2k+PC9iPjwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTIgY29sb3I9Ymx1ZSBmYWNlPSJBcmlhbCI+PGI+W0xpemhvbmddIFllcywgdGhhdCdz
IGV4YWN0bHkNCndoYXQgSSBtZWFuLjwvYj48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9
IkFyaWFsIj4uPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPg0KPC9m
b250Pjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+PGJyPg0KMi4gU2VjdGlvbiA3LjEsIEkgYW0g
d29uZGVyaW5nIGhvdyB0byBzZXR1cCB0aGUgdW5pZGlyZWN0aW9uYWwgbXAycCBwc2V1ZG93aXJl
Lg0KQWNjb3JkaW5nIHRvIFJGQzQ0NDcsIG9uZSBwc2V1ZG93aXJlIHdpbGwgYmUgVVAgb25seSB3
aGVuIGJvdGggbG9jYWwgYW5kDQpyZW1vdGUgbGFiZWwgbWFwcGluZyBtZXNzYWdlIGlzIHNlbnQg
YW5kIHJlY2VpdmVkLiBCdXQgYWNjb3JkaW5nIHRvIHRoZQ0KZGVzY3JpcGl0aW9uIG9mIHVuaWRp
cmVjdGlvbmFsIG1wMnAgcHNldWRvd2lyZSBpbiBJUExTLCBpZiBQRXggc2VuZHMgYQ0KbGFiZWwg
bWFwcGluZyB0byBQRXkgZm9yIENFeCwgUEV5IHNlZW1zIHRvIGNvbnNpZGVyIHRoZSBQVyBhcyBV
UCB3aGVuIHJlY2VpdmluZw0KdGhlIGNvcnJlc3BvbmRpbmcgbGFiZWwgbWFwcGluZywgYW5kIFBF
eCB3b3VsZCBjb25zaWRlciB0aGUgUFcgYXMgVVAgd2hlbg0Kc2VuZGluZyBvdXQgdGhlIGxhYmVs
IG1hcHBpbmcsIHdpdGhvdXQgdGhlIG5lY2Vzc2FyaXR5IG9mIGFsbG9jYXRpbmcgbG9jYWwNCmxh
YmVscyBmb3IgdGhlIFBXLjwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFu
Ij4gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hl
dCBNUyI+PGI+PGk+W0hpbWFuc2h1Jmd0O10NClRoZXJlIGlzIG5vIG9uZS10by1vbmUgY29ycmVz
cG9uZGVuY2Ugd2l0aCByZXNwZWN0IHRvIFBXIGRpcmVjdGlvbmFsaXR5Lg0KTWVhbmluZywgaWYg
UEUxIGhhcyB0d28gbG9jYWwgQ0UsIGl0IHdpbGwgYWR2ZXJ0aXNlIHR3byBsYWJlbHMuIElmIFBF
Mg0KaGFzIDQgbG9jYWwgQ0VzIGl0IHdpbGwgYWR2ZXJ0aXNlIDQgbGFiZWxzLiA8L2k+PC9iPjwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTIgY29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQgTVMi
PjxiPjxpPldoaWNoIGRvZXMgbm90DQptZWFuIHRoYXQgd2hlbiBQRTEgcmVjZWl2ZXMgNCBsYWJl
bHMgZnJvbSBQRTIgdGhhdCBpdCBuZWVkcyB0byBhZHZlcnRpc2UNCjQgbGFiZWxzIHRvIGJyaW5n
IFBXIKGuVVChry4gU28gdGhlIHF1ZXN0aW9uLCBpcyChrnVuaWRpcmVjdGlvbmFsoa8NClBXIGEg
ZGV2aWF0aW9uIGZyb20gUkZDIDQ0NDcgd2hpY2ggPC9pPjwvYj48L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT5hc3N1bWVzIFBX
IHRvDQpiZSBiaS1kaXJlY3Rpb25hbCAodGhpcyB1c2VkIHRvIGJlIHRydWUgaW5pdGlhbGx5LCBu
b3Qgc3VyZSBpZiBzdGlsbCBpcw0KdHJ1ZSkgYnkgd2F5IG9mIHVuaXRpbmcgdG8gb3Bwb3NpdGUg
ZGlyZWN0aW9uIHVuaWRpcmVjdGlvbmFsIFBXLiBUaGUgdW5pZGlyZWN0aW9uYWwNClBXIGlzIG5v
dCBpbGxlZ2FsLjwvaT48L2I+PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZh
Y2U9IkFyaWFsIj48Yj5bTGl6aG9uZ10gRnJvbSBteSB1bmRlcnN0YW5kaW5nLA0KdW5pZGlyZWN0
aW9uYWwgcG9pbnQtdG8tcG9pbnQgUFcgaXMgbm90IGRlZmluZWQgaW4gUkZDNDQ0Ny4gU2VlIHNl
Y3Rpb24NCjUuMy4zIHNpZ25hbGluZyBwcm9jZWR1cmVzIGluIFJGQzQ0NDcuPC9iPjwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPjxicj4NCldoYXQncyBtb3JlLCBpdCBpcyBh
bHNvIGRpZmZpY3VsdCB0byBjb25maWd1cmUgdGhlIFBXaWQuIElmIFBFeCB1c2VzIFBXaWRfMQ0K
Zm9yIENFeDEsIGFuZCBQV2lkXzIgZm9yIENFeDIsIGFjY29yZGluZyB0byBzZWN0aW9uIDcuMSwg
dGhlIFBFeSBuZWVkcw0KdG8gY29uZmlndXJlIGJvdGggUFdpZF8xIGFuZCBQV2lkXzIsIHdoaWNo
IGlzIGFjdHVhbGx5IG5vdCBuZWNlc3NhcnkuIERvDQpJIG1pc3Mgc29tZXRoaW5nIGltcG9ydGFu
dCBoZXJlIHRvIHVuZGVyc3RhbmQgdGhlIGNvbmNlcHQgb2YgdW5pZGlyZWN0aW9uYWwNCm1wMnAg
cHNldWRvd2lyZT8gVGhlcmUgbWF5IGJlIGEgbmV3IHR5cGUgb2YgRkVDIHRoYXQgaXMgcmVxdWly
ZWQsIHNpbWlsYXINCndpdGggdW5pZGlyZWN0aW9uYWwgUDJNUCBQVy48L2ZvbnQ+PGZvbnQgc2l6
ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+DQo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNv
bG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT5bSGltYW5zaHUmZ3Q7XQ0KUFdp
ZCBpcyBwZXIgSVBMUyBpbnN0YW5jZSBhbmQgbm90IHBlciBDRS4gSSBkbyBub3Qgc2VlIGFueSB0
ZXh0IGluIDcuMQ0Kd2hpY2ggdGFsa3MgYWJvdXQgY29uZmlndXJpbmcgZGlmZmVyZW5jZSBQV2lk
IGZvciBlYWNoIENFLjwvaT48L2I+PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0
OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+Rm9yIGEgZ2l2ZW4gSVBMUw0KaW5zdGFuY2Ug
YSBQRSBoYXMgZm9sbG93aW5nIHRvIHNpZ25hbCCoQzwvaT48L2I+PC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+YSkgJm5ic3A7
ICZuYnNwO1BXDQppZDwvaT48L2I+PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMWY0
OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+YikgJm5ic3A7ICZuYnNwO09uZQ0KTVAyUCCh
rm11bHRpY2FzdKGvICZuYnNwO0V0aGVybmV0IFBXPC9pPjwvYj48L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT5jKSAmbmJzcDsg
Jm5ic3A7DQpNYW55IChpLmUuIG9uZSBwZXIgbG9jYWwgQ0UpIE1QMlAgoa51bmljYXN0oa8gSVAg
UFcgYWxvbmcgd2l0aCBDRaGvcw0KTUFDIGFkZHJlc3M8L2k+PC9iPjwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTMgY29sb3I9IzFmNDk3ZCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxiPjxpPltIaW1h
bnNodSZndDtdDQo8L2k+PC9iPlNlY3Rpb24gNy4xIGRlc2NyaWJlcyBkZXRhaWxzIGZvciBzZW5k
IGFuZCByZWNlaXZlIHByb2Nlc3Npbmcgb2YNCmxhYmVsIG1hcHBpbmcgbWVzc2FnZTwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZSBmYWNlPSJBcmlhbCI+PGI+W0xpemhvbmddIERv
IHlvdSBtZWFuIFBFIHdpbGwNCmFkdmVydGlzZSBhbGwgbGFiZWxzIGZvciBDRXMgd2l0aCBzYW1l
IFBXaWQ/IFRoZW4gdGhhdCBtZWFucyBQRSB3aWxsIGFkdmVydGlzZQ0KZGlmZmVyZW50IGxhYmVs
cyBmb3Igc2FtZSBGRUMoc2FtZSBQV2lkKSwgd2hpY2ggd2lsbCBub3Qgb3BlcmF0ZSBjb3JyZWN0
bHkNCnVuZGVyIGN1cnJlbnQgZnJhbWV3b3JrLiBUaGUgcGVlciBQRSByZWNlaXZpbmcgc2V2ZXJh
bCBsYWJlbCBtYXBwaW5nIG1lc3NhZ2VzDQp3aXRoIHNhbWUgRkVDIGJ1dCBkaWZmZXJlbnQgbGFi
ZWxzIHdpbGwgdXBkYXRlIHRoZSBhbHJlYWR5IHJlY2VpdmVkIGxhYmVsLA0KYW5kIG9ubHkgcmV0
YWluIHRoZSBuZXdlc3Qgb25lLiBUaGUgd2F5IHRvIHNvbHZlIHRoaXMgaXMgdG8gZGVmaW5lIGEg
bmV3DQp0eXBlIG9mIEZFQyB0byBzcGVjaWZ5IGRpZmZlcmVudCBvcGVyYXRpb24gY29tcGFyaW5n
IHdpdGggbm9ybWFsIEZFQyAoZS5nLA0KdHlwZSAxMjggYW5kIDEyOSkuPC9iPjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPjxicj4NCjMuIFNlY3Rpb24gNy4yLCB3aHkgbm90
IHVzaW5nIExEUCBjYXBhYmlsaXR5IHRvIGFkdmVydGlzaW5nIElQdjYgc3RhY2sNCmNhcGFiaWxp
dHk/PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiA8L2ZvbnQ+DQo8
YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT5b
SGltYW5zaHUmZ3Q7XQ0KQmVjYXVzZSB0aGlzIGlzIHNwZWNpZmljIHRvIFBXIGFuZCBJUExTIGlu
c3RhbmNlPC9pPjwvYj48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWUgZmFjZT0i
QXJpYWwiPjxiPltMaXpob25nXSBhY3R1YWxseSwgY3VycmVudA0KUDJNUCBQVyBjYXBhYmlsaXR5
IG5lZ290aWF0aW9uIHVzZXMgTERQIGNhcGFiaWxpdHkuIEkgaG9wZSB3ZSBjYW4gYWxpZ24NCnRo
aXMsIGJlY2F1c2UgYm90aCBhcmUgcmVsYXRlZCB3aXRoIFBXIGNhcGFiaWxpdHkuPC9iPjwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPjxicj4NCjQuIFdpbGwgSVBMUyBjb25z
aWRlciBhbnkgc3Bva2UgY29ubmVjdGl2aXR5IHRvIGluY3JlYXNlIHRoZSBzY2FsYWJpbGl0eSwN
CnNhbWUgYXMgVlBMUz88L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+
IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgY29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQg
TVMiPjxiPjxpPltIaW1hbnNodSZndDtdDQpJIGFtIG5vdCBzdXJlIEkgZnVsbHkgdW5kZXJzdGFu
ZC4gSVBMUyBhc3N1bWVzIChyZWNvbW1lbmRzKSB0aGF0IENFcyBhcmUNCklQIHJvdXRlcnMgdGhh
dCBhY3QgYXMgZWRnZSBib3guPC9pPjwvYj48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9y
PSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT5NZWFuaW5nIG1vc3Qgb2YNCnRoZSBj
dXN0b21lcqGvcyBJUCBob3N0cyBhbmQgJm5ic3A7b3RoZXIgcm91dGVycyBhcmUgYmVoaW5kIHRo
aXMgQ0Ugcm91dGVyDQppbiBjdXN0b21lciBuZXR3b3JrIGFuZCBQRSBkb2VzPC9pPjwvYj48L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48
Yj48aT5ub3Qgc2VlIHRoZW0uDQpUaGlzIGJ5IGl0c2VsZiBwcm92aWRlcyBnb29kIGhpZXJhcmNo
eSAmYW1wOyBzY2FsYWJpbGl0eS4gPC9pPjwvYj48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNv
bG9yPWJsdWUgZmFjZT0iQXJpYWwiPjxiPltMaXpob25nXSBTb3JyeSBmb3IgdGhlIHVuY2xlYXIN
CnN0YXRlbWVudC4gVGhlIHNjYWxhYmlsaXR5IEkgcmVmZXIgaXMgUFcgc2NhbGFibGl0eSB0byBj
b25zdHJ1Y3QgbGFyZ2UNCklQTFMgbmV0d29yaywgd2hpY2ggaXMgaW5jbHVkZWQgaW4gUkZDNDc2
MiBzZWN0aW9uIDEwLjEuMS48L2I+PC9mb250Pjxmb250IHNpemU9MiBjb2xvcj0jMWY0OTdkIGZh
Y2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+DQo8L2k+PC9iPjwvZm9udD48Zm9udCBzaXplPTMgZmFj
ZT0iVGltZXMgTmV3IFJvbWFuIj48YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFs
Ij48YnI+DQpIb3BlIHRvIHNlZSB5b3VyIHJlcGx5LCB0aGFuayB5b3UuPC9mb250Pjxmb250IHNp
emU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPg0KPGJyPg0KPC9mb250Pjxmb250IHNpemU9MiBm
YWNlPSJBcmlhbCI+PGJyPg0KQmVzdCBSZWdhcmRzPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJU
aW1lcyBOZXcgUm9tYW4iPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj48YnI+DQpM
aXpob25nIEppbjwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4gPC9m
b250Pjxmb250IHNpemU9MSBmYWNlPSJBcmlhbCI+PGJyPg0KIDwvZm9udD48Zm9udCBzaXplPTMg
ZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4mbmJzcDs8YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZh
Y2U9IkNvdXJpZXIgTmV3Ij48YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+
DQo8YnI+DQpEYXRlOiBNb24sIDUgQXByIDIwMTAgMTk6NTg6MDEgLTA2MDA8YnI+DQpGcm9tOiBT
aGFuZSBBbWFudGUgJmx0O3NoYW5lQGNhc3RsZXBvaW50Lm5ldCZndDs8YnI+DQpTdWJqZWN0OiBX
RyBMYXN0IENhbGw6IGRyYWZ0LWlldGYtbDJ2cG4taXBscy0wOTxicj4NClRvOiBsMnZwbkBpZXRm
Lm9yZzxicj4NCk1lc3NhZ2UtSUQ6ICZsdDs3QjZDNTA0MC1DMTAzLTQ2MjYtODNGOC02MTgzMzFG
NjhCQ0VAY2FzdGxlcG9pbnQubmV0Jmd0Ozxicj4NCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsg
Y2hhcnNldD11cy1hc2NpaTxicj4NCjxicj4NCkhpIEV2ZXJ5b25lLDxicj4NCjxicj4NClRoaXMg
aXMgdG8gYmVnaW4gYSAoZmluYWwpIFdHIExhc3QgQ2FsbCBvbjo8YnI+DQpodHRwOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWwydnBuLWlwbHMtMDk8YnI+DQo8YnI+DQpJZiB5b3Ug
aGF2ZSBzdWJzdGFudGlhbCB0ZWNobmljYWwgY29tbWVudHMgb3IgY29uY2VybnMsIHBsZWFzZSBz
aGFyZSB0aGVtDQp3aXRoIHRoZSBsaXN0LiAmbmJzcDtJZiB5b3UgaGF2ZSBlZGl0b3JpYWwgY29t
bWVudHMsIHBsZWFzZSBzaGFyZSB0aGVtDQpkaXJlY3RseSB3aXRoIHRoZSBhdXRob3JzIGFuZCBj
by1jaGFpcnMuPGJyPg0KPGJyPg0KU28gZmFyLCB3ZSBoYXZlIHRoZSBmb2xsb3dpbmcgZm9sa3Mg
c2lnbmVkIHVwIGZvciBhIHRob3JvdWdoIHJldmlldyBhbmQNCmNvbW1lbnRzOjxicj4NCi0gQW5k
eSBNYWxpczxicj4NCi0gTmljayBEZWxSZWdubzxicj4NCi0gUHJhbmphbCBEdXR0YTxicj4NCkhv
d2V2ZXIsIHdlIGNvdWxkIHVzZSBtb3JlIHBlb3BsZSB0byBjb25kdWN0IGEgcmV2aWV3LiAmbmJz
cDtJZiB5b3UgaGF2ZQ0KdGhlIHRpbWUgYW5kL29yIGluY2xpbmF0aW9uLCBwbGVhc2UgbGV0IHRo
ZSBjaGFpcnMga25vdyBpZiB5b3UnbGwgYmUgY29uZHVjdGluZw0KYSByZXZpZXcuPGJyPg0KPGJy
Pg0KVGhlIExhc3QgQ2FsbCBvbiB0aGlzIGRyYWZ0IHdpbGwgYWxzbyBlbmQgb24gQXByaWwgMjMu
PGJyPg0KPGJyPg0KVGhhbmtzLDxicj4NCjxicj4NCkdpbGVzICZhbXA7IFNoYW5lPC9mb250Pg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJDb3VyaWVyIE5ldyI+Jm5ic3A7PC9mb250Pg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJDb3VyaWVyIE5ldyI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9IkNvdXJpZXIgTmV3Ij5aVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkgTm90aWNlOiBUaGUNCmlu
Zm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMgc29sZWx5IHByb3BlcnR5IG9mIHRo
ZSBzZW5kZXIncyBvcmdhbml6YXRpb24uDQpUaGlzIG1haWwgY29tbXVuaWNhdGlvbiBpcyBjb25m
aWRlbnRpYWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZA0KdG8gbWFpbnRh
aW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRz
IG9mIHRoaXMNCmNvbW11bmljYXRpb24gdG8gb3RoZXJzLjwvZm9udD4NCjxicj48Zm9udCBzaXpl
PTIgZmFjZT0iQ291cmllciBOZXciPlRoaXMgZW1haWwgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRl
ZA0Kd2l0aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1
c2Ugb2YgdGhlIGluZGl2aWR1YWwNCm9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3Nl
ZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbg0KZXJyb3IgcGxlYXNlIG5vdGlm
eSB0aGUgb3JpZ2luYXRvciBvZiB0aGUgbWVzc2FnZS4gQW55IHZpZXdzIGV4cHJlc3NlZA0KaW4g
dGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBvZiB0aGUgaW5kaXZpZHVhbCBzZW5kZXIuPC9mb250Pg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJDb3VyaWVyIE5ldyI+VGhpcyBtZXNzYWdlIGhhcyBiZWVu
IHNjYW5uZWQgZm9yIHZpcnVzZXMNCmFuZCBTcGFtIGJ5IFpURSBBbnRpLVNwYW0gc3lzdGVtLjwv
Zm9udD4NCjxicj4NCjxicj48cHJlPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClpURSZuYnNwO0luZm9ybWF0aW9uJm5ic3A7U2VjdXJp
dHkmbmJzcDtOb3RpY2U6Jm5ic3A7VGhlJm5ic3A7aW5mb3JtYXRpb24mbmJzcDtjb250YWluZWQm
bmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttYWlsJm5ic3A7aXMmbmJzcDtzb2xlbHkmbmJzcDtwcm9w
ZXJ0eSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7c2VuZGVyJ3MmbmJzcDtvcmdhbml6YXRpb24uJm5i
c3A7VGhpcyZuYnNwO21haWwmbmJzcDtjb21tdW5pY2F0aW9uJm5ic3A7aXMmbmJzcDtjb25maWRl
bnRpYWwuJm5ic3A7UmVjaXBpZW50cyZuYnNwO25hbWVkJm5ic3A7YWJvdmUmbmJzcDthcmUmbmJz
cDtvYmxpZ2F0ZWQmbmJzcDt0byZuYnNwO21haW50YWluJm5ic3A7c2VjcmVjeSZuYnNwO2FuZCZu
YnNwO2FyZSZuYnNwO25vdCZuYnNwO3Blcm1pdHRlZCZuYnNwO3RvJm5ic3A7ZGlzY2xvc2UmbmJz
cDt0aGUmbmJzcDtjb250ZW50cyZuYnNwO29mJm5ic3A7dGhpcyZuYnNwO2NvbW11bmljYXRpb24m
bmJzcDt0byZuYnNwO290aGVycy4NClRoaXMmbmJzcDtlbWFpbCZuYnNwO2FuZCZuYnNwO2FueSZu
YnNwO2ZpbGVzJm5ic3A7dHJhbnNtaXR0ZWQmbmJzcDt3aXRoJm5ic3A7aXQmbmJzcDthcmUmbmJz
cDtjb25maWRlbnRpYWwmbmJzcDthbmQmbmJzcDtpbnRlbmRlZCZuYnNwO3NvbGVseSZuYnNwO2Zv
ciZuYnNwO3RoZSZuYnNwO3VzZSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7aW5kaXZpZHVhbCZuYnNw
O29yJm5ic3A7ZW50aXR5Jm5ic3A7dG8mbmJzcDt3aG9tJm5ic3A7dGhleSZuYnNwO2FyZSZuYnNw
O2FkZHJlc3NlZC4mbmJzcDtJZiZuYnNwO3lvdSZuYnNwO2hhdmUmbmJzcDtyZWNlaXZlZCZuYnNw
O3RoaXMmbmJzcDtlbWFpbCZuYnNwO2luJm5ic3A7ZXJyb3ImbmJzcDtwbGVhc2UmbmJzcDtub3Rp
ZnkmbmJzcDt0aGUmbmJzcDtvcmlnaW5hdG9yJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDttZXNzYWdl
LiZuYnNwO0FueSZuYnNwO3ZpZXdzJm5ic3A7ZXhwcmVzc2VkJm5ic3A7aW4mbmJzcDt0aGlzJm5i
c3A7bWVzc2FnZSZuYnNwO2FyZSZuYnNwO3Rob3NlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRp
dmlkdWFsJm5ic3A7c2VuZGVyLg0KVGhpcyZuYnNwO21lc3NhZ2UmbmJzcDtoYXMmbmJzcDtiZWVu
Jm5ic3A7c2Nhbm5lZCZuYnNwO2ZvciZuYnNwO3ZpcnVzZXMmbmJzcDthbmQmbmJzcDtTcGFtJm5i
c3A7YnkmbmJzcDtaVEUmbmJzcDtBbnRpLVNwYW0mbmJzcDtzeXN0ZW0uDQo8L3ByZT4=
--=_alternative 0007C02B4825770B_=--


From lizhong.jin@zte.com.cn  Mon Apr 19 19:35:53 2010
Return-Path: <lizhong.jin@zte.com.cn>
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 A96C43A6902 for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 19:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.154
X-Spam-Level: 
X-Spam-Status: No, score=-98.154 tagged_above=-999 required=5 tests=[AWL=1.270, BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQXtM5lrUskZ for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 19:35:52 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id DAB2D3A6892 for <l2vpn@ietf.org>; Mon, 19 Apr 2010 19:35:51 -0700 (PDT)
Received: from [10.30.17.100] by mx6.zte.com.cn with surfront esmtp id 58071577109098; Tue, 20 Apr 2010 10:32:45 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 93587.1106677472; Tue, 20 Apr 2010 10:31:56 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o3K2ZR1s008044; Tue, 20 Apr 2010 10:35:27 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <OF013616A1.49C5FBD9-ON482576A9.00290A40-482576AA.00221B0C@LocalDomain>
MIME-Version: 1.0
To: rahul@juniper.net
Subject: Comments for draft-raggarwa-l2vpn-p2mp-pw-02
Sensitivity: 
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF7372D899.5E732CDC-ON482576B1.0032DE1B-4825770B.000E37E1@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Tue, 20 Apr 2010 10:35:17 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-20 10:35:22, Serialize complete at 2010-04-20 10:35:22
Content-Type: multipart/alternative; boundary="=_alternative 000E37DF4825770B_="
X-MAIL: mse2.zte.com.cn o3K2ZR1s008044
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: Tue, 20 Apr 2010 02:35:54 -0000

This is a multipart message in MIME format.
--=_alternative 000E37DF4825770B_=
Content-Type: text/plain; charset="US-ASCII"

Hi Rahul:
I got some comments for draft-raggarwa-l2vpn-p2mp-pw-02. In section 5, CE 
ID is used instend of VE ID compared with RFC4761. This is correct if 
there is no reverse path requirement for P2MP PW. If the reverse path 
needs to be setup, the NLRI with <RD, CE ID> is not correct now. For 
example, if there are two CEs connected to one leaf PE for one P2MP PW, 
then two NLRI will be generated and advertised to root PE. But the reverse 
path is a unidirctional P2P LSP from leaf PE to root PE, then which NLRI 
will carry the reverse path label information?

One leaf PE in VPMS can connect multiple leaf AC, and there will be also a 
forwarding instance for the leaf PE, like below:
       +-----------------+
  AC1  |  +-----------+  | 
=======|==| Virtual   |  |  P2MP PW  //
       |  | Forwarder |==|===========
=======|==|           |  |           \\
  AC2  |  +-----------+  |
       +-----------------+ 
The "virtual forwarder" will simplely copy the packets from P2MP PW to AC1 
and AC2 unidirectionally.
Then, after some consideration, I think we can still use VE ID for VPMS 
with new address family for NLRI. Then the leaf PE can advertise NLRI with 
<RD, VEID> to setup the reverse path. MH-ID described in 
<draft-ietf-l2vpn-vpls-multihoming-00> can be used for multi-homing for 
VPMS.

What do you think about the above problem?

Best Regards
Lizhong Jin


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
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 expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 000E37DF4825770B_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Rahul:</font>
<br><font size=2 face="sans-serif">I got some comments for draft-raggarwa-l2vpn-p2mp-pw-02.
In section 5, CE ID is used instend of VE ID compared with RFC4761. This
is correct if there is no reverse path requirement for P2MP PW. If the
reverse path needs to be setup, the NLRI with &lt;RD, CE ID&gt; is not
correct now. For example, if there are two CEs connected to one leaf PE
for one P2MP PW, then two NLRI will be generated and advertised to root
PE. But the reverse path is a unidirctional P2P LSP from leaf PE to root
PE, then which NLRI will carry the reverse path label information?</font>
<br>
<br><font size=2 face="sans-serif">One leaf PE in VPMS can connect multiple
leaf AC, and there will be also a forwarding instance for the leaf PE,
like below:</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;+-----------------+</font>
<br><font size=2 face="sans-serif">&nbsp; AC1 &nbsp;| &nbsp;+-----------+
&nbsp;| </font>
<br><font size=2 face="sans-serif">=======|==| Virtual &nbsp; | &nbsp;|
&nbsp;P2MP PW &nbsp;//</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;|
Forwarder |==|===========</font>
<br><font size=2 face="sans-serif">=======|==| &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; | &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; \\</font>
<br><font size=2 face="sans-serif">&nbsp; AC2 &nbsp;| &nbsp;+-----------+
&nbsp;|</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp;+-----------------+
&nbsp;</font>
<br><font size=2 face="sans-serif">The &quot;virtual forwarder&quot; will
simplely copy the packets from P2MP PW to AC1 and AC2 unidirectionally.</font>
<br><font size=2 face="sans-serif">Then, after some consideration, I think
we can still use VE ID for VPMS with new address family for NLRI. Then
the leaf PE can advertise NLRI with &lt;RD, VEID&gt; to setup the reverse
path. MH-ID described in &lt;draft-ietf-l2vpn-vpls-multihoming-00&gt; can
be used for multi-homing for VPMS.</font>
<br>
<br><font size=2 face="sans-serif">What do you think about the above problem?</font>
<br>
<br><font size=2 face="sans-serif">Best Regards</font>
<br><font size=2 face="sans-serif">Lizhong Jin</font>
<br><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 000E37DF4825770B_=--


From joel.pauling@alcatel-lucent.com  Mon Apr 19 20:16:28 2010
Return-Path: <joel.pauling@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 903123A69B7 for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 20:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.826
X-Spam-Level: 
X-Spam-Status: No, score=-0.826 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_20=-0.74]
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 oFNmtat5Y2ND for <l2vpn@core3.amsl.com>; Mon, 19 Apr 2010 20:16:27 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 5DDB93A6809 for <l2vpn@ietf.org>; Mon, 19 Apr 2010 20:16:27 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o3K3GEC5004093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 19 Apr 2010 22:16:16 -0500 (CDT)
Received: from SGSINSXCHHUB01.sg.alcatel-lucent.com (sgsinsxchhub01.sg.alcatel-lucent.com [135.254.109.71]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3K3GBaP009809 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Apr 2010 08:46:13 +0530
Received: from SGSINSXCHMBSA2.sg.alcatel-lucent.com ([135.254.109.84]) by SGSINSXCHHUB01.sg.alcatel-lucent.com ([135.254.109.71]) with mapi; Tue, 20 Apr 2010 11:16:12 +0800
From: "PAULING, JOEL (JOEL)" <joel.pauling@alcatel-lucent.com>
To: Himanshu Shah <hshah@force10networks.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Tue, 20 Apr 2010 11:16:10 +0800
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLKV0PSguv1yOSDSMtyd3zpMAzQABQgJQArEKIyAAEAiqIA==
Message-ID: <2B79F1682D699B45839C711B092EA89EA3EC2FD6BA@SGSINSXCHMBSA2.sg.alcatel-lucent.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net> <D434F7EE545145439BFA47601F9B2BA302F6ACAB@SGSINSMBS02.ad4.ad.alcatel.com> <34F81DE93A7AA840A6A3B1187BAD5FC80379CB8A11@EXCH-CLUSTER-10.force10networks.com>
In-Reply-To: <34F81DE93A7AA840A6A3B1187BAD5FC80379CB8A11@EXCH-CLUSTER-10.force10networks.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 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
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, 20 Apr 2010 03:16:28 -0000

Thanks,=20

I understand your position but I can see ipls being a significant component=
 in a V6 centric infrastructure as an alternative way to deliver v4 sans DS=
-lite etc. Because of this very likely scenario and also the push to MPLS-T=
P in the core (san's any IP layer involvement) I think this may be importan=
t to remove a v4 fallback as a default.=20

-JoelW

-----Original Message-----
From: Himanshu Shah [mailto:hshah@force10networks.com]=20
Sent: Tuesday, 20 April 2010 7:44 a.m.
To: PAULING, JOEL (JOEL); l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Joel -
Thanks for your comment.

While you make a good a point, here is what my thinking behind it.

IPLS was designed originally for IPv4 and existed for a long time before su=
pport of IPv6 added. If there is any implementation out there, they have IP=
v4 support for it and would like to see a newer implementation be compatibl=
e with existing.

Secondly, it is always desirable that an RFC provide 'a base version' that =
is at minimum be compatible and interoperable with other implementations.

Nonetheless, you make a good point and would like to hear from other member=
s of the WG that entertain a possibility of IPv6 only IPLS (a possibility, =
with a fallback tunable option).

Regards,
himanshu


-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of P=
AULING JOEL
Sent: Monday, April 05, 2010 10:40 PM
To: l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Looks good.=20

One comment:=20

Re fallback protocol (proposed to be IPv4) should be a tuneable option. Whi=
le the V6 compatibility flag currently signals v6 stack compatibility on th=
e tunnel end point, I would prefer from a future proofing perspective if th=
e fallback protocol was definable.=20

Especially in MPLS PE-PE scenarios, it is preferable to run either IPV4 + M=
PLS OR IPV6 + MPLS, rather than both through a MS core network (reducing ad=
min overhead by having to maintain two stacks). Having fallback protocol be=
 a tuneable option will cater to this scenario better than current proposed=
 draft.


Kind regards


Joel W Pauling

Network Capability Engineer
Alcatel-Lucent New Zealand
+64 4 803 7639
+64 21 171 8049
joel.pauling@alcatel-lucent.com

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Tuesday, 6 April 2010 1:58 p.m.
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From raymond.key@ieee.org  Tue Apr 20 04:09:48 2010
Return-Path: <raymond.key@ieee.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 3212A3A6B9A for <l2vpn@core3.amsl.com>; Tue, 20 Apr 2010 04:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.492
X-Spam-Level: 
X-Spam-Status: No, score=-98.492 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYYP96pubolB for <l2vpn@core3.amsl.com>; Tue, 20 Apr 2010 04:09:47 -0700 (PDT)
Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by core3.amsl.com (Postfix) with ESMTP id 0F6F228C0DC for <l2vpn@ietf.org>; Tue, 20 Apr 2010 04:09:46 -0700 (PDT)
Received: from localhost.localdomain (webmail01.syd.optusnet.com.au [211.29.132.235]) by mail08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o3KB9ZbK009455; Tue, 20 Apr 2010 21:09:35 +1000
Message-Id: <201004201109.o3KB9ZbK009455@mail08.syd.optusnet.com.au>
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
X-Mailer: MIME-tools 5.420 (Entity 5.420)
Received: from bcano.tcif.telstra.com.au ([203.35.82.133]) by webmail01.syd.optusnet.com.au with http (user=rkey_ieee@optusnet.com.au); Tue, 20 Apr 2010 21:09:35 +1000
From: Raymond Key <raymond.key@ieee.org>
To: rahul@juniper.net
Date: Tue, 20 Apr 2010 21:09:35 +1000
Subject: Re: Updated minutes from IETF 77
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raymond.key@ieee.org
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, 20 Apr 2010 11:09:48 -0000

Hi Rahul,

I go through the recently published IETF77 L2VPN minutes
and would like to follow up on one of your comments. 

Extract from minutes under
8) Discussion of ETREE requirements and solution space
"Rahul Aggarwal: excellent presentation. This spells out the 
 problem well. Option 1 is a must. Once you have done this, 
 how do you identify whether traffic comes from root or leaf 
 AC? CW approach is broken. VLAN tag is appealing if it gives 
 a homogenous solution. If it doesn't could use MPLS label."

Is "CW approach is broken" referring to the solution approach 
proposed in draft-key-l2vpn-vpls-etree-02? Could you elaborate 
a little bit more on how it is broken?

Thanks,
Raymond Key 


> Giles Heron <giles.heron@gmail.com> wrote:
> 
> Ok - so it'd help if I actually put some content in my email.
> 
> As Simon Delord helpfully pointed out the other day I missed the second 
> half
> of the meeting out when I posted these.
> 
> I've now updated the online minutes:
> 
> http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
> 
> Giles

From raymond.key@ieee.org  Wed Apr 21 14:55:39 2010
Return-Path: <raymond.key@ieee.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 9FC3C3A6B43 for <l2vpn@core3.amsl.com>; Wed, 21 Apr 2010 14:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.492
X-Spam-Level: 
X-Spam-Status: No, score=-98.492 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0+2rKlxWjes for <l2vpn@core3.amsl.com>; Wed, 21 Apr 2010 14:55:39 -0700 (PDT)
Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by core3.amsl.com (Postfix) with ESMTP id 9B2423A68D1 for <l2vpn@ietf.org>; Wed, 21 Apr 2010 14:55:38 -0700 (PDT)
Received: from localhost.localdomain (webmail15.syd.optusnet.com.au [211.29.132.102]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o3LLtPLC019971; Thu, 22 Apr 2010 07:55:25 +1000
Message-Id: <201004212155.o3LLtPLC019971@mail07.syd.optusnet.com.au>
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
X-Mailer: MIME-tools 5.420 (Entity 5.420)
Received: from bcavo.tcif.telstra.com.au ([203.35.135.133]) by webmail15.syd.optusnet.com.au with http (user=rkey_ieee@optusnet.com.au); Thu, 22 Apr 2010 07:55:25 +1000
From: Raymond Key <raymond.key@ieee.org>
To: nick.delregno@verizon.com
Date: Thu, 22 Apr 2010 07:55:25 +1000
Subject: Re: Updated minutes from IETF 77
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raymond.key@ieee.org
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, 21 Apr 2010 21:55:39 -0000

Hi Nic,

I go through the recently published IETF77 L2VPN minutes and 
would like to follow up on one of your comments.

Extract from minutes under
10) Extension to VPLS for E-Tree
"Nic: This requires a control word, so a box has to support a control word. 
PW mustn't come up if a CW is not supported."

There may be some confusion here. When one PE does not support 
control word, PW can still come up.

Refer to Section 5.2. Control Word (under Backward Compatibility)
For backward compatibility reason, use of Control Word on Ethernet PW
is not mandatory. If the PE on the other end prefers not to use
Control Word or does not support Control Word (which implies such PE
does not support the extension specified in this document), then
Control Word will not be used on the Ethernet PW.
Refer to Appendix A for different Control Word scenarios.
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5.2)

Regards,
Raymond Key


> Giles Heron <giles.heron@gmail.com> wrote:
> 
> Ok - so it'd help if I actually put some content in my email.
> 
> As Simon Delord helpfully pointed out the other day I missed the second 
> half
> of the meeting out when I posted these.
> 
> I've now updated the online minutes:
> 
> http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
> 
> Giles

From nick.delregno@verizon.com  Wed Apr 21 16:00:55 2010
Return-Path: <nick.delregno@verizon.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 3A08C3A6B27 for <l2vpn@core3.amsl.com>; Wed, 21 Apr 2010 16:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9edCLoCck5Xg for <l2vpn@core3.amsl.com>; Wed, 21 Apr 2010 16:00:54 -0700 (PDT)
Received: from ashesmtp01.verizonbusiness.com (ashesmtp01.verizonbusiness.com [198.4.8.163]) by core3.amsl.com (Postfix) with ESMTP id AD6E828C102 for <l2vpn@ietf.org>; Wed, 21 Apr 2010 16:00:50 -0700 (PDT)
Received: from omzismtp02.vzbi.com ([unknown] [165.122.46.167]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0L19000E2194HX10@firewall.verizonbusiness.com> for l2vpn@ietf.org; Wed, 21 Apr 2010 23:00:40 +0000 (GMT)
Received: from omzismtp02.vzbi.com ([unknown] [127.0.0.1]) by omzismtp02.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0L19003891946T00@omzismtp02.vzbi.com> for l2vpn@ietf.org; Wed, 21 Apr 2010 23:00:40 +0000 (GMT)
Received: from ASHSRV141.mcilink.com ([unknown] [153.39.68.167]) by omzismtp02.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0L190033U1945U00@omzismtp02.vzbi.com> for l2vpn@ietf.org; Wed, 21 Apr 2010 23:00:40 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV141.mcilink.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Apr 2010 23:00:39 +0000
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: Updated minutes from IETF 77
Date: Wed, 21 Apr 2010 23:00:38 +0000
Message-id: <14584D6EE26B314187A4F68BA206060003C92928@ASHEVS008.mcilink.com>
In-reply-to: <201004212155.o3LLtPLC019971@mail07.syd.optusnet.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: Updated minutes from IETF 77
Thread-index: AcrhnWHnXkr/oEv2SpOH0It3fJc5IwACBAUw
References: <201004212155.o3LLtPLC019971@mail07.syd.optusnet.com.au>
From: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
To: raymond.key@ieee.org
X-OriginalArrivalTime: 21 Apr 2010 23:00:39.0835 (UTC) FILETIME=[76422EB0:01CAE1A6]
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, 21 Apr 2010 23:00:55 -0000

Raymond:

>From a purely T-LDP perspective, I agree.  However, if we are relying on
CW to indicate leaf/root and the targeted PE doesn't support CW, then
the ETREE model breaks as I can no longer determine leaf/root and
drop/forward traffic accordingly.  As such, the implementation behavior
when using CW to indicate Leaf/Root MUST NOT allow the CW preference
mismatch to result in an active PW.

Thanks,
Nick

-----Original Message-----
From: Raymond Key [mailto:raymond.key@ieee.org]=20
Sent: Wednesday, April 21, 2010 4:55 PM
To: Delregno, Christopher N (Nick DelRegno)
Cc: l2vpn@ietf.org
Subject: Re: Updated minutes from IETF 77

Hi Nic,

I go through the recently published IETF77 L2VPN minutes and would like
to follow up on one of your comments.

Extract from minutes under
10) Extension to VPLS for E-Tree
"Nic: This requires a control word, so a box has to support a control
word.=20
PW mustn't come up if a CW is not supported."

There may be some confusion here. When one PE does not support control
word, PW can still come up.

Refer to Section 5.2. Control Word (under Backward Compatibility) For
backward compatibility reason, use of Control Word on Ethernet PW is not
mandatory. If the PE on the other end prefers not to use Control Word or
does not support Control Word (which implies such PE does not support
the extension specified in this document), then Control Word will not be
used on the Ethernet PW.
Refer to Appendix A for different Control Word scenarios.
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5.2)

Regards,
Raymond Key


> Giles Heron <giles.heron@gmail.com> wrote:
>=20
> Ok - so it'd help if I actually put some content in my email.
>=20
> As Simon Delord helpfully pointed out the other day I missed the=20
> second half of the meeting out when I posted these.
>=20
> I've now updated the online minutes:
>=20
> http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
>=20
> Giles

From pranjal.dutta@alcatel-lucent.com  Thu Apr 22 08:55:25 2010
Return-Path: <pranjal.dutta@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 CCEDA3A6BE2 for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 08:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 0nk4jFY0JNVf for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 08:55:24 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id B2B593A6BDE for <l2vpn@ietf.org>; Thu, 22 Apr 2010 08:55:24 -0700 (PDT)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id o3MFt7o5016114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 22 Apr 2010 10:55:09 -0500 (CDT)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3MFt6A8001698 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Apr 2010 21:25:06 +0530
Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.50]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Thu, 22 Apr 2010 21:25:06 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Thu, 22 Apr 2010 21:25:03 +0530
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNBG3HA
Message-ID: <C584046466ED224CA92C1BC3313B963E09DFEF6B03@INBANSXCHMBSA3.in.alcatel-lucent.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
In-Reply-To: <7B6C5040-C103-4626-83F8-618331F68BCE@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 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
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, 22 Apr 2010 15:55:25 -0000

Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.=20

In Section 6.1 When to Signal an IPv4 address of a CE
     ....
     Similarly, if the PE detects that an IP address of a CE is no
     longer valid (by methods described above), the PE must re-
     advertise the PW FEC with null IP address to denote the
     withdrawal of IP address of the CE. The receiving PE then waits
     for notification of the remote IP address. During this period,
     propagation of unicast IPv4 traffic is suspended, but multicast
     IPv4 traffic can continue to flow between the AC and the
     pseudowire.
     ....
     <Comment>=20
     I think we need to expand a bit on "PE must re-advertise the=20
     PW FEC with null IP address". Section 6.2 also specifies LDP
     Notification message to reflect any change in CE address without=20
     re-mapping/re-advertising if label has been advertised already.
     Otherwise it's a bit ambiguous on whether to use label withdraw=20
     on moving from 'non-zero' CE address to 'zero' CE address or    =20
     reflect the change with CE address change Notification Message.
    </Comment>

Section 7. IPV6 Capability Advertisement
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....

<Comment>

There is a need to consider the following case on IPV6=20
Capability negotiation.

Let's take some sequence of events in IP L2 PW setup between=20
A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs=20
   to do re-mapping. A sends label withdraw W1 first and=20
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is=20
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It=20
   responds with unsolicited "release" R1 to A with status=20
   code S1 =3D "IP Address Type Mismatch" since B supports=20
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw=20
   W1 that A is waiting for. So it advertises L2 to B - the=20
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -=20
   unsolicited release. =20
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t A but would be fine at B. Both ends are out of sync due to race condition=
s.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) w=
hen it changes from IPV4 to IPV6 (but not vice versa). When B processes lab=
el withdraw with status Code S2, no release should be sent as response and =
B should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section =
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7.2 in draft-ietf-l2vpn-ipls-09 as we=
ll.
</Comment>

Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From pranjal.dutta@alcatel-lucent.com  Thu Apr 22 08:59:10 2010
Return-Path: <pranjal.dutta@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 7D78428C0EE for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 08:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.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 eNu5cDRb-wML for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 08:59:09 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 59CF23A6B9B for <l2vpn@ietf.org>; Thu, 22 Apr 2010 08:59:09 -0700 (PDT)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o3MFwpOJ008098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 22 Apr 2010 10:58:54 -0500 (CDT)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3MFwpp4001782 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Apr 2010 21:28:51 +0530
Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.50]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Thu, 22 Apr 2010 21:28:51 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
To: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Thu, 22 Apr 2010 21:28:48 +0530
Subject: RE: WG Last Call:  draft-ietf-l2vpn-arp-mediation-13
Thread-Topic: WG Last Call:  draft-ietf-l2vpn-arp-mediation-13
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNBG3HAAADNZ5A=
Message-ID: <C584046466ED224CA92C1BC3313B963E09DFEF6B04@INBANSXCHMBSA3.in.alcatel-lucent.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@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 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
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, 22 Apr 2010 15:59:10 -0000

Sorry this was for arp-mediation draft. So please read it for other one
and NOT for ipls draft.=20

Shane : I have changed your subject line :-) in this thread.

-----Original Message-----
From: Dutta, Pranjal K (Pranjal)=20
Sent: Thursday, April 22, 2010 8:55 AM
To: 'Shane Amante'; l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.=20

In Section 6.1 When to Signal an IPv4 address of a CE
     ....
     Similarly, if the PE detects that an IP address of a CE is no
     longer valid (by methods described above), the PE must re-
     advertise the PW FEC with null IP address to denote the
     withdrawal of IP address of the CE. The receiving PE then waits
     for notification of the remote IP address. During this period,
     propagation of unicast IPv4 traffic is suspended, but multicast
     IPv4 traffic can continue to flow between the AC and the
     pseudowire.
     ....
     <Comment>=20
     I think we need to expand a bit on "PE must re-advertise the=20
     PW FEC with null IP address". Section 6.2 also specifies LDP
     Notification message to reflect any change in CE address without=20
     re-mapping/re-advertising if label has been advertised already.
     Otherwise it's a bit ambiguous on whether to use label withdraw=20
     on moving from 'non-zero' CE address to 'zero' CE address or    =20
     reflect the change with CE address change Notification Message.
    </Comment>

Section 7. IPV6 Capability Advertisement
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....

<Comment>

There is a need to consider the following case on IPV6=20
Capability negotiation.

Let's take some sequence of events in IP L2 PW setup between=20
A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs=20
   to do re-mapping. A sends label withdraw W1 first and=20
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is=20
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It=20
   responds with unsolicited "release" R1 to A with status=20
   code S1 =3D "IP Address Type Mismatch" since B supports=20
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw=20
   W1 that A is waiting for. So it advertises L2 to B - the=20
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -=20
   unsolicited release. =20
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t A but would be fine at B. Both ends are out of sync due to race condition=
s.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) w=
hen it changes from IPV4 to IPV6 (but not vice versa). When B processes lab=
el withdraw with status Code S2, no release should be sent as response and =
B should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section =
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7.2 in draft-ietf-l2vpn-ipls-09 as we=
ll.
</Comment>

Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From pranjal.dutta@alcatel-lucent.com  Thu Apr 22 09:09:35 2010
Return-Path: <pranjal.dutta@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 0265128C13B for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 09:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 NKTC0femlmLF for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 09:09:34 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 64C5C3A6B78 for <l2vpn@ietf.org>; Thu, 22 Apr 2010 09:09:18 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o3MG8xOp027473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 22 Apr 2010 11:09:02 -0500 (CDT)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3MG8xhT005601 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Apr 2010 21:38:59 +0530
Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.50]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Thu, 22 Apr 2010 21:38:59 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Thu, 22 Apr 2010 21:38:55 +0530
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNCB0eg
Message-ID: <C584046466ED224CA92C1BC3313B963E09DFEF6B09@INBANSXCHMBSA3.in.alcatel-lucent.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
In-Reply-To: <7B6C5040-C103-4626-83F8-618331F68BCE@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 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
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, 22 Apr 2010 16:09:35 -0000

Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.
  =20
Section 7.2 IPV6 Capability advertisement.
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....
<Comment>

There is a need to consider the following case on IPV6 Capability negotiati=
on.

Let's take some sequence of events in IP L2 PW setup between A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs=20
   to do re-mapping. A sends label withdraw W1 first and=20
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is=20
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It=20
   responds with unsolicited "release" R1 to A with status=20
   code S1 =3D "IP Address Type Mismatch" since B supports=20
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw=20
   W1 that A is waiting for. So it advertises L2 to B - the=20
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -=20
   unsolicited release. =20
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t=20
A but would be fine at B. Both ends are out of sync due to race conditions.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d=20
withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) whe=
n=20
it changes from IPV4 to IPV6 (but not vice versa). When B processes label
withdraw with status Code S2, no release should be sent as response and B=20
should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section=
=20
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-1=
3
as well.

</Comment>

Section 7.3 Signaling Advertisement Processing

A PE should process a received [PWE3-CONTROL] advertisement with PW- type o=
f IP Layer2 transport for IPLS as follows,

        - Verify the IPLS VPN membership by matching the VPN-Id
          signaled in the AGI field or the PW-ID field with all the
          VPN-Ids configured in the PE. Discard and release the PW
          label if VPN-Id is not found.
        - Program the Forwarding Information Base (FIB) such that when
          a unicast IP packet is received from an AC with its
          destination MAC address matching the advertised MAC address,
          the packet is forwarded out over the tunnel to the
          advertising PE with the advertised PW-label as the inner
          label.
  =20
<Comment>

In section 6.1 we have described that there would be one PW (either P2MP or
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that w=
e
are signaling P2P PW per CE with FEC128 to receive unicast traffic and ther=
e
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS mem=
bership with FEC128 Pwid. If we need to advertise multiple CEs from same si=
te over same LDP signaling session, each with different labels then PWid
(VPN-ID) is not unique differentiator at receiver. It needs to be explained
in detail on how the PW setup would take place per CE using FEC128. For FEC=
129 different AC-ID can be used for each CE but with common AGI (=3D VPN-ID=
) to associate them to same IPLS instance at receivers.

</Comment>
  =20
Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From lizhong.jin@zte.com.cn  Thu Apr 22 18:24:23 2010
Return-Path: <lizhong.jin@zte.com.cn>
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 C1D333A67F3 for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 18:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.154
X-Spam-Level: 
X-Spam-Status: No, score=-101.154 tagged_above=-999 required=5 tests=[AWL=0.684, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOFyBAAeA-zA for <l2vpn@core3.amsl.com>; Thu, 22 Apr 2010 18:24:21 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id EBBF03A67BD for <l2vpn@ietf.org>; Thu, 22 Apr 2010 18:24:20 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 36887577109098; Fri, 23 Apr 2010 09:20:33 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 88040.2512463415; Fri, 23 Apr 2010 09:20:18 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o3N1NqVn050963; Fri, 23 Apr 2010 09:23:54 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.3830.1271952575.4756.l2vpn@ietf.org>
To: pranjal.dutta@alcatel-lucent.com
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFDDD55D7A.AD496997-ON4825770E.00074459-4825770E.0007AB38@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Fri, 23 Apr 2010 09:23:45 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-23 09:23:51, Serialize complete at 2010-04-23 09:23:51
Content-Type: multipart/alternative; boundary="=_alternative 0007AB354825770E_="
X-MAIL: mse2.zte.com.cn o3N1NqVn050963
Cc: l2vpn@ietf.org, Shane Amante <shane@castlepoint.net>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 23 Apr 2010 01:24:23 -0000

This is a multipart message in MIME format.
--=_alternative 0007AB354825770E_=
Content-Type: text/plain; charset="US-ASCII"

Hi,
I also agree with Pranjal's two comments. We should solve the two 
problems: capability negotiation and PW setup.

BR
Lizhong


------------------------------------------------------------
Date: Thu, 22 Apr 2010 21:38:55 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
To: Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org"
                 <l2vpn@ietf.org>
Message-ID:
 
<C584046466ED224CA92C1BC3313B963E09DFEF6B09@INBANSXCHMBSA3.in.alcatel-lucent.com>
 
Content-Type: text/plain; charset="us-ascii"

Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.
 
Section 7.2 IPV6 Capability advertisement.
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....
<Comment>

There is a need to consider the following case on IPV6 Capability 
negotiation.

Let's take some sequence of events in IP L2 PW setup between A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs 
   to do re-mapping. A sends label withdraw W1 first and 
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is 
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It 
   responds with unsolicited "release" R1 to A with status 
   code S1 = "IP Address Type Mismatch" since B supports 
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw 
   W1 that A is waiting for. So it advertises L2 to B - the 
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 - 
   unsolicited release. 
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up 
at 
A but would be fine at B. Both ends are out of sync due to race 
conditions.

So we can't overlap releases R1 and R2 from B. The solution is for A to 
send 
withdraw W1 with a new status code S2 = "Wrong IP Address Type" (e.g) when 

it changes from IPV4 to IPV6 (but not vice versa). When B processes label
withdraw with status Code S2, no release should be sent as response and B 
should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section 

6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7 in 
draft-ietf-l2vpn-arp-mediation-13
as well.

</Comment>

Section 7.3 Signaling Advertisement Processing

A PE should process a received [PWE3-CONTROL] advertisement with PW- type 
of IP Layer2 transport for IPLS as follows,

        - Verify the IPLS VPN membership by matching the VPN-Id
          signaled in the AGI field or the PW-ID field with all the
          VPN-Ids configured in the PE. Discard and release the PW
          label if VPN-Id is not found.
        - Program the Forwarding Information Base (FIB) such that when
          a unicast IP packet is received from an AC with its
          destination MAC address matching the advertised MAC address,
          the packet is forwarded out over the tunnel to the
          advertising PE with the advertised PW-label as the inner
          label.
 
<Comment>

In section 6.1 we have described that there would be one PW (either P2MP 
or
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that 
we
are signaling P2P PW per CE with FEC128 to receive unicast traffic and 
there
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS 
membership with FEC128 Pwid. If we need to advertise multiple CEs from 
same site over same LDP signaling session, each with different labels then 
PWid
(VPN-ID) is not unique differentiator at receiver. It needs to be 
explained
in detail on how the PW setup would take place per CE using FEC128. For 
FEC129 different AC-ID can be used for each CE but with common AGI (= 
VPN-ID) to associate them to same IPLS instance at receivers.

</Comment>
 
Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of 
Shane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them 
with the list.  If you have editorial comments, please share them directly 
with the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and 
comments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the 
time and/or inclination, please let the chairs know if you'll be 
conducting a review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane


------------------------------

_______________________________________________
L2vpn mailing list
L2vpn@ietf.org
https://www.ietf.org/mailman/listinfo/l2vpn


End of L2vpn Digest, Vol 71, Issue 11
*************************************




--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
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 expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 0007AB354825770E_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,</font>
<br><font size=2 face="sans-serif">I also agree with </font><tt><font size=2>Pranjal</font></tt><font size=2 face="sans-serif">'s
two comments. We should solve the two problems: capability negotiation
and PW setup.</font>
<br>
<br><font size=2 face="sans-serif">BR</font>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br><font size=2 face="sans-serif"><br>
</font><tt><font size=2>------------------------------------------------------------<br>
Date: Thu, 22 Apr 2010 21:38:55 +0530<br>
From: &quot;Dutta, Pranjal K (Pranjal)&quot; &lt;pranjal.dutta@alcatel-lucent.com&gt;<br>
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09<br>
To: Shane Amante &lt;shane@castlepoint.net&gt;, &quot;l2vpn@ietf.org&quot;<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;l2vpn@ietf.org&gt;<br>
Message-ID:<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;C584046466ED224CA92C1BC3313B963E09DFEF6B09@INBANSXCHMBSA3.in.alcatel-lucent.com&gt;<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
<br>
Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
<br>
Hello Authors and WG,<br>
<br>
 &nbsp; &nbsp;Here are some of my review comments on this version of the
I-D.<br>
 &nbsp; <br>
Section 7.2 IPV6 Capability advertisement.<br>
 &nbsp; ....<br>
 &nbsp; A PE that supports IPv6 on an IP PW MUST signal the stack capability<br>
 &nbsp; sub-TLV in the initial label mapping message for the PW. The PE<br>
 &nbsp; nodes compare the value advertised by the remote PE with the local<br>
 &nbsp; configuration and only use a capability which is advertised by
both.<br>
 &nbsp; If a PE that supports IPv6 does not receive a 'stack capability'<br>
 &nbsp; sub-TLV from the far-end PE in the initial label mapping message,
or<br>
 &nbsp; one is received but it is set to a reserved value, the PE MUST
send<br>
 &nbsp; an unsolicited release for the PW label with the LDP status code<br>
 &nbsp; meaning ''IP Address type mismatch'' (Status Code 0x0000004A).<br>
 &nbsp; ....<br>
&lt;Comment&gt;<br>
<br>
There is a need to consider the following case on IPV6 Capability negotiation.<br>
<br>
Let's take some sequence of events in IP L2 PW setup between A and B.<br>
<br>
 &nbsp; &nbsp; A---------------------B<br>
<br>
A is configured with IPV4 only initially.<br>
B supports both IPV6 + IPv4.<br>
<br>
1. A sends initial label mapping L1 for IPV4 PW setup to B.<br>
 &nbsp; L1 is waiting in B to get processed.<br>
2. Now we configured ipv6 capability in A. So A needs <br>
 &nbsp; to do re-mapping. A sends label withdraw W1 first and <br>
 &nbsp; then awaits for label release from B to re-advertise<br>
 &nbsp; with IPV4 + IPV6 capability. So label withdraw W1 is <br>
 &nbsp; in queue after the initial label Map L1 at B.<br>
3. Now B processes the initial label map L1 from A. It <br>
 &nbsp; responds with unsolicited &quot;release&quot; R1 to A with status
<br>
 &nbsp; code S1 = &quot;IP Address Type Mismatch&quot; since B supports
<br>
 &nbsp; IPV4 + IPV6.<br>
4. Now A processes R1 and thinks it's the Release to withdraw <br>
 &nbsp; W1 that A is waiting for. So it advertises L2 to B - the <br>
 &nbsp; new Label mapping with IPV4 + IPV6.<br>
5. B processes W1 now and responds back with regular Release R2.<br>
6. A thinks that its label map L2 is being released by R2 - <br>
 &nbsp; unsolicited release. &nbsp;<br>
7. B processes L2 and is happy with it.<br>
<br>
At the end of this re-negotiation, the PW would never be operationally
up at <br>
A but would be fine at B. Both ends are out of sync due to race conditions.<br>
<br>
So we can't overlap releases R1 and R2 from B. The solution is for A to
send <br>
withdraw W1 with a new status code S2 = &quot;Wrong IP Address Type&quot;
(e.g) when <br>
it changes from IPV4 to IPV6 (but not vice versa). When B processes label<br>
withdraw with status Code S2, no release should be sent as response and
B <br>
should continue to wait for next control message from A.<br>
<br>
We do similar procedures with cBit re-negotiation. Please refer to section
<br>
6.2 in RFC 4447 on usage of &quot;Wrong C-bit&quot;.<br>
<br>
Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-13<br>
as well.<br>
<br>
&lt;/Comment&gt;<br>
<br>
Section 7.3 Signaling Advertisement Processing<br>
<br>
A PE should process a received [PWE3-CONTROL] advertisement with PW- type
of IP Layer2 transport for IPLS as follows,<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp;- Verify the IPLS VPN membership by matching
the VPN-Id<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;signaled in the AGI field or the PW-ID
field with all the<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;VPN-Ids configured in the PE. Discard
and release the PW<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;label if VPN-Id is not found.<br>
 &nbsp; &nbsp; &nbsp; &nbsp;- Program the Forwarding Information Base (FIB)
such that when<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;a unicast IP packet is received from
an AC with its<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;destination MAC address matching the
advertised MAC address,<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;the packet is forwarded out over the
tunnel to the<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;advertising PE with the advertised PW-label
as the inner<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;label.<br>
 &nbsp; <br>
&lt;Comment&gt;<br>
<br>
In section 6.1 we have described that there would be one PW (either P2MP
or<br>
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that
we<br>
are signaling P2P PW per CE with FEC128 to receive unicast traffic and
there<br>
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS
membership with FEC128 Pwid. If we need to advertise multiple CEs from
same site over same LDP signaling session, each with different labels then
PWid<br>
(VPN-ID) is not unique differentiator at receiver. It needs to be explained<br>
in detail on how the PW setup would take place per CE using FEC128. For
FEC129 different AC-ID can be used for each CE but with common AGI (= VPN-ID)
to associate them to same IPLS instance at receivers.<br>
<br>
&lt;/Comment&gt;<br>
 &nbsp; <br>
Thanks,<br>
Pranjal<br>
<br>
-----Original Message-----<br>
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Shane Amante<br>
Sent: Monday, April 05, 2010 6:58 PM<br>
To: l2vpn@ietf.org<br>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<br>
<br>
Hi Everyone,<br>
<br>
This is to begin a (final) WG Last Call on:<br>
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09<br>
<br>
If you have substantial technical comments or concerns, please share them
with the list. &nbsp;If you have editorial comments, please share them
directly with the authors and co-chairs.<br>
<br>
So far, we have the following folks signed up for a thorough review and
comments:<br>
- Andy Malis<br>
- Nick DelRegno<br>
- Pranjal Dutta<br>
However, we could use more people to conduct a review. &nbsp;If you have
the time and/or inclination, please let the chairs know if you'll be conducting
a review.<br>
<br>
The Last Call on this draft will also end on April 23.<br>
<br>
Thanks,<br>
<br>
Giles &amp; Shane<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
L2vpn mailing list<br>
L2vpn@ietf.org<br>
https://www.ietf.org/mailman/listinfo/l2vpn<br>
<br>
<br>
End of L2vpn Digest, Vol 71, Issue 11<br>
*************************************<br>
<br>
</font></tt>
<br><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 0007AB354825770E_=--


From raymond.key@ieee.org  Fri Apr 23 18:39:42 2010
Return-Path: <raymond.key@ieee.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 839A83A67A6 for <l2vpn@core3.amsl.com>; Fri, 23 Apr 2010 18:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.862
X-Spam-Level: 
X-Spam-Status: No, score=-98.862 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xixLA0V7RrTq for <l2vpn@core3.amsl.com>; Fri, 23 Apr 2010 18:39:41 -0700 (PDT)
Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by core3.amsl.com (Postfix) with ESMTP id 0D6F93A6783 for <l2vpn@ietf.org>; Fri, 23 Apr 2010 18:39:40 -0700 (PDT)
Received: from localhost.localdomain (webmail03.syd.optusnet.com.au [211.29.132.237]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o3O1dRpw010203; Sat, 24 Apr 2010 11:39:28 +1000
Message-Id: <201004240139.o3O1dRpw010203@mail04.syd.optusnet.com.au>
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
X-Mailer: MIME-tools 5.420 (Entity 5.420)
Received: from bcbno.tcif.telstra.com.au ([203.35.82.136]) by webmail03.syd.optusnet.com.au with http (user=rkey_ieee@optusnet.com.au); Sat, 24 Apr 2010 11:39:27 +1000
From: Raymond Key <raymond.key@ieee.org>
To: "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
Date: Sat, 24 Apr 2010 11:39:27 +1000
Subject: Comments on draft-key-l2vpn-vpls-etree-02
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raymond.key@ieee.org
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: Sat, 24 Apr 2010 01:39:43 -0000

Hi Nick,

Thanks for your comment.

Quote from your email, "However, if we are relying on CW to indicate
leaf/root and the targeted PE doesn't support CW, then the ETREE model
breaks as I can no longer determine leaf/root and drop/forward traffic
accordingly."

There may be some confusion here. When the targeted PE doesn't support 
CW, it also implies the targeted PE doesn't support the extension 
specified in this draft (see section 4.2, "A PE MUST be capable of 
sending and receiving the Control Word on Ethernet PW") and hence the 
targeted PE has only Root ACs. This is a backward compatibility 
scenario and does not result in any problem.

Backward compatibility issues are discussed in section 5 in the draft. 
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5)
Some paragraphs are extracted below.

(5.3. Additional Action in Data Forwarding)

For backward compatibility reason, a PE not supporting the extension
specified in this document can participate in an E-Tree construct,
but only Root ACs can be connected to such PE.

Lack of Control Word L-bit per-payload signaling between a PE
supporting the extension specified in this document and a PE not
supporting such extension does not result in any problem.

(5.3.1 Ingress PE Support the Extension but Egress PE Not)

If Control Word is not used on the Ethernet PW, there will be no CW
L-bit. The egress PE will forward the frame as per current standard.
This is correct as only Root ACs exist on a PE not supporting the
extension specified in this document.  A Root AC can receive from any
other ACs.

By the way I recently posted a draft "Requirements for MEF E-Tree 
Support in VPLS" 
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-reqt-00)
trying to start a "solution-neutral" discussion on whether there is a 
valid requirement to enhance VPLS or not. Any comments on that draft?

Thanks,
Raymond 


> Delregno, Christopher N (Nick DelRegno) <nick.delregno@verizon.com> wrote:
> 
> Raymond:
> 
> From a purely T-LDP perspective, I agree.  However, if we are relying on
> CW to indicate leaf/root and the targeted PE doesn't support CW, then
> the ETREE model breaks as I can no longer determine leaf/root and
> drop/forward traffic accordingly.  As such, the implementation behavior
> when using CW to indicate Leaf/Root MUST NOT allow the CW preference
> mismatch to result in an active PW.
> 
> Thanks,
> Nick
> 
> -----Original Message-----
> From: Raymond Key [mailto:raymond.key@ieee.org] 
> Sent: Wednesday, April 21, 2010 4:55 PM
> To: Delregno, Christopher N (Nick DelRegno)
> Cc: l2vpn@ietf.org
> Subject: Re: Updated minutes from IETF 77
> 
> Hi Nic,
> 
> I go through the recently published IETF77 L2VPN minutes and would like
> to follow up on one of your comments.
> 
> Extract from minutes under
> 10) Extension to VPLS for E-Tree
> "Nic: This requires a control word, so a box has to support a control
> word. 
> PW mustn't come up if a CW is not supported."
> 
> There may be some confusion here. When one PE does not support control
> word, PW can still come up.
> 
> Refer to Section 5.2. Control Word (under Backward Compatibility) For
> backward compatibility reason, use of Control Word on Ethernet PW is not
> mandatory. If the PE on the other end prefers not to use Control Word or
> does not support Control Word (which implies such PE does not support
> the extension specified in this document), then Control Word will not be
> used on the Ethernet PW.
> Refer to Appendix A for different Control Word scenarios.
> (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5.2)
> 
> Regards,
> Raymond Key
> 
> 
> > Giles Heron <giles.heron@gmail.com> wrote:
> > 
> > Ok - so it'd help if I actually put some content in my email.
> > 
> > As Simon Delord helpfully pointed out the other day I missed the 
> > second half of the meeting out when I posted these.
> > 
> > I've now updated the online minutes:
> > 
> > http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
> > 
> > Giles

From shane@castlepoint.net  Sun Apr 25 14:12:20 2010
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 A07823A6AF5 for <l2vpn@core3.amsl.com>; Sun, 25 Apr 2010 14:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level: 
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[AWL=-1.044, BAYES_50=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 osZuZgyND9JK for <l2vpn@core3.amsl.com>; Sun, 25 Apr 2010 14:12:19 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id DCF5C3A6917 for <l2vpn@ietf.org>; Sun, 25 Apr 2010 14:12:18 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 8785826866A; Sun, 25 Apr 2010 15:12:06 -0600 (MDT)
Received: from mbpw.castlepoint.net (71-215-81-125.hlrn.qwest.net [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 25 Apr 2010 15:12:06 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=49745; syn-fingerprint=65535:56:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
Date: Sun, 25 Apr 2010 15:11:51 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <92D92366-BEA0-40F3-8120-3D3260D6B261@castlepoint.net>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
To: l2vpn@ietf.org
X-Mailer: Apple Mail (2.1078)
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: Sun, 25 Apr 2010 21:12:20 -0000

Thank you Joel, Lizhong and Pranjal for your reviews and comments.

The WG Last Call on IPLS is now closed. =20

Would the authors please address the outstanding comments & questions, =
to the satisfaction of the reviewers, so that we can move forward with =
this document?

Giles & Shane


On Apr 5, 2010, at 19:58 MDT, Shane Amante wrote:

> Hi Everyone,
>=20
> This is to begin a (final) WG Last Call on:
> http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09
>=20
> If you have substantial technical comments or concerns, please share =
them with the list.  If you have editorial comments, please share them =
directly with the authors and co-chairs.
>=20
> So far, we have the following folks signed up for a thorough review =
and comments:
> - Andy Malis
> - Nick DelRegno
> - Pranjal Dutta
> However, we could use more people to conduct a review.  If you have =
the time and/or inclination, please let the chairs know if you'll be =
conducting a review.
>=20
> The Last Call on this draft will also end on April 23.
>=20
> Thanks,
>=20
> Giles & Shane


From shane@castlepoint.net  Sun Apr 25 14:15:03 2010
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 4D9733A6AC4 for <l2vpn@core3.amsl.com>; Sun, 25 Apr 2010 14:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.239
X-Spam-Level: 
X-Spam-Status: No, score=-2.239 tagged_above=-999 required=5 tests=[AWL=0.360,  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 aujlhpMPtbte for <l2vpn@core3.amsl.com>; Sun, 25 Apr 2010 14:15:02 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id CFE483A6ABF for <l2vpn@ietf.org>; Sun, 25 Apr 2010 14:15:01 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id A064626866A; Sun, 25 Apr 2010 15:14:50 -0600 (MDT)
Received: from mbpw.castlepoint.net (71-215-81-125.hlrn.qwest.net [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 25 Apr 2010 15:14:50 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=49746; syn-fingerprint=65535:56:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: WG Last Call: draft-ietf-l2vpn-arp-mediation-13
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <2530B373-F6FF-4310-8513-1F892A725866@castlepoint.net>
Date: Sun, 25 Apr 2010 15:14:35 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D7281B4-8CBA-4A25-B42C-A600DE087DEA@castlepoint.net>
References: <2530B373-F6FF-4310-8513-1F892A725866@castlepoint.net>
To: l2vpn@ietf.org
X-Mailer: Apple Mail (2.1078)
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: Sun, 25 Apr 2010 21:15:03 -0000

Thank you Pranjal for your reviews and comments.

The WG Last Call on ARP-MED is now closed. =20

Would the authors please address the outstanding comments & questions, =
to the satisfaction of the reviewers, so that we can move forward with =
this document?

Giles & Shane



On Apr 5, 2010, at 19:56 MDT, Shane Amante wrote:
> Hi Everyone,
>=20
> This is to begin a (final) WG Last Call on:
> http://tools.ietf.org/html/draft-ietf-l2vpn-arp-mediation-13
>=20
> If you have substantial technical comments or concerns, please share =
them with the list.  If you have editorial comments, please share them =
directly with the authors and co-chairs.
>=20
> So far, we have the following folks signed up for a thorough review =
and comments:
> - Andy Malis
> - Nick DelRegno
> - Pranjal Dutta
> However, we could use more people to conduct a review.  If you have =
the time and/or inclination, please let the chairs know if you'll be =
conducting a review.
>=20
> The Last Call on this draft will end on April 23.
>=20
> Thanks,
>=20
> Giles & Shane


From ju1738@att.com  Mon Apr 26 06:46:18 2010
Return-Path: <ju1738@att.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 0C96C3A6A8C for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 06:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1iIRvJe4Mb0 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 06:46:16 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id A011428C152 for <l2vpn@ietf.org>; Mon, 26 Apr 2010 06:46:02 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ju1738@att.com
X-Msg-Ref: server-5.tower-167.messagelabs.com!1272289549!17696270!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 8546 invoked from network); 26 Apr 2010 13:45:50 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-5.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Apr 2010 13:45:50 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3QDjX3f022495; Mon, 26 Apr 2010 09:45:34 -0400
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com [144.155.43.107]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3QDjR4p022379; Mon, 26 Apr 2010 09:45:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Comments on draft-key-l2vpn-vpls-etree-02
Date: Mon, 26 Apr 2010 09:41:46 -0400
Message-ID: <1477DEAE19DD884CB004730D0FD77FD7041A8814@misout7msgusr7e.ugd.att.com>
In-Reply-To: <201004240139.o3O1dRpw010203@mail04.syd.optusnet.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-key-l2vpn-vpls-etree-02
Thread-Index: AcrjTwP9vrSUv4l/ToCTo0Li4vBqnAB9k/Aw
References: <201004240139.o3O1dRpw010203@mail04.syd.optusnet.com.au>
From: "UTTARO, JAMES (ATTLABS)" <ju1738@att.com>
To: <raymond.key@ieee.org>, "Delregno, Christopher N (Nick DelRegno)" <nick.delregno@verizon.com>
X-Mailman-Approved-At: Mon, 26 Apr 2010 07:26:28 -0700
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: Mon, 26 Apr 2010 14:18:03 -0000

I guess  am still a bit confused as to how this would work when there
are leafs and roots on the same PE..

a) If Leafs are on the same PE how will the CW function? Will we need to
rely on some other mechanism to prevent Leaf<>Leaf traffic on the same
PE ?

b) Leaf->Root traffic on the same PE? We don't want the Root to simply
forward the traffic directly to another Leaf either on the PE or via a
PW to a remote PE.. How is this accomplished?

Comments In-Line..

Jim Uttaro

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
Of Raymond Key
Sent: Friday, April 23, 2010 9:39 PM
To: Delregno, Christopher N (Nick DelRegno)
Cc: l2vpn@ietf.org
Subject: Comments on draft-key-l2vpn-vpls-etree-02

Hi Nick,

Thanks for your comment.

Quote from your email, "However, if we are relying on CW to indicate
leaf/root and the targeted PE doesn't support CW, then the ETREE model
breaks as I can no longer determine leaf/root and drop/forward traffic
accordingly."

There may be some confusion here. When the targeted PE doesn't support=20
CW, it also implies the targeted PE doesn't support the extension=20
specified in this draft (see section 4.2, "A PE MUST be capable of=20
sending and receiving the Control Word on Ethernet PW") and hence the=20
targeted PE has only Root ACs. This is a backward compatibility=20
scenario and does not result in any problem.

[Jim U>] From an SP perspective this approach represents a major
operational/provisioning challenge.. We would now need to track the set
of PEs that are candidates for Roots ( No CW Capable ), Roots and Leafs,
Leafs only. We cannot easily go back and change our homing rules. This
would also impact the provisonable footprint.

Backward compatibility issues are discussed in section 5 in the draft.=20
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5)
Some paragraphs are extracted below.

(5.3. Additional Action in Data Forwarding)

For backward compatibility reason, a PE not supporting the extension
specified in this document can participate in an E-Tree construct,
but only Root ACs can be connected to such PE.

Lack of Control Word L-bit per-payload signaling between a PE
supporting the extension specified in this document and a PE not
supporting such extension does not result in any problem.

(5.3.1 Ingress PE Support the Extension but Egress PE Not)

If Control Word is not used on the Ethernet PW, there will be no CW
L-bit. The egress PE will forward the frame as per current standard.
This is correct as only Root ACs exist on a PE not supporting the
extension specified in this document.  A Root AC can receive from any
other ACs.

By the way I recently posted a draft "Requirements for MEF E-Tree=20
Support in VPLS"=20
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-reqt-00)
trying to start a "solution-neutral" discussion on whether there is a=20
valid requirement to enhance VPLS or not. Any comments on that draft?

Thanks,
Raymond=20


> Delregno, Christopher N (Nick DelRegno) <nick.delregno@verizon.com>
wrote:
>=20
> Raymond:
>=20
> From a purely T-LDP perspective, I agree.  However, if we are relying
on
> CW to indicate leaf/root and the targeted PE doesn't support CW, then
> the ETREE model breaks as I can no longer determine leaf/root and
> drop/forward traffic accordingly.  As such, the implementation
behavior
> when using CW to indicate Leaf/Root MUST NOT allow the CW preference
> mismatch to result in an active PW.
>=20
> Thanks,
> Nick
>=20
> -----Original Message-----
> From: Raymond Key [mailto:raymond.key@ieee.org]=20
> Sent: Wednesday, April 21, 2010 4:55 PM
> To: Delregno, Christopher N (Nick DelRegno)
> Cc: l2vpn@ietf.org
> Subject: Re: Updated minutes from IETF 77
>=20
> Hi Nic,
>=20
> I go through the recently published IETF77 L2VPN minutes and would
like
> to follow up on one of your comments.
>=20
> Extract from minutes under
> 10) Extension to VPLS for E-Tree
> "Nic: This requires a control word, so a box has to support a control
> word.=20
> PW mustn't come up if a CW is not supported."
>=20
> There may be some confusion here. When one PE does not support control
> word, PW can still come up.
>=20
> Refer to Section 5.2. Control Word (under Backward Compatibility) For
> backward compatibility reason, use of Control Word on Ethernet PW is
not
> mandatory. If the PE on the other end prefers not to use Control Word
or
> does not support Control Word (which implies such PE does not support
> the extension specified in this document), then Control Word will not
be
> used on the Ethernet PW.
> Refer to Appendix A for different Control Word scenarios.
> (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5.2)
>=20
> Regards,
> Raymond Key
>=20
>=20
> > Giles Heron <giles.heron@gmail.com> wrote:
> >=20
> > Ok - so it'd help if I actually put some content in my email.
> >=20
> > As Simon Delord helpfully pointed out the other day I missed the=20
> > second half of the meeting out when I posted these.
> >=20
> > I've now updated the online minutes:
> >=20
> > http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
> >=20
> > Giles

From hshah@force10networks.com  Mon Apr 26 15:00:49 2010
Return-Path: <hshah@force10networks.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 59B8D28C1A4 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 15:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.698
X-Spam-Level: 
X-Spam-Status: No, score=-3.698 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, 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 npFEzF+gZuMX for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 15:00:37 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id A53CE3A63D3 for <l2vpn@ietf.org>; Mon, 26 Apr 2010 15:00:37 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Mon, 26 Apr 2010 15:00:25 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Mon, 26 Apr 2010 15:00:22 -0700
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrgKFN4bkr2dOtaS3eWNJZzuRwxlQFY4p1m
Message-ID: <C7FB8536.3830%hshah@force10networks.com>
In-Reply-To: <OF9ED45CDA.DCB1F1E3-ON4825770B.0003AD91-4825770B.0007C02E@zte.com.cn>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7FB85363830hshahforce10networkscom_"
MIME-Version: 1.0
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "flefauch@cisco.com" <flefauch@cisco.com>, "lmartini@cisco.com" <lmartini@cisco.com>, "giles.heron@gmail.com" <giles.heron@gmail.com>, "shane@castlepoint.net" <shane@castlepoint.net>, "erosen@cisco.com" <erosen@cisco.com>, Krishnamoorthy Arvind <karvind@enterasys.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, 26 Apr 2010 22:00:49 -0000

--_000_C7FB85363830hshahforce10networkscom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Lizhong Jin,
Again thanks for the comments, response to your comments in line (marked in=
 green).
/himanshu



On 4/19/10 9:24 PM, "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn> wrote=
:


Hi Himanshu,
Thank you for your reply. Please see my comments in line.

BR
Lizhong Jin


Himanshu Shah <hshah@force10networks.com> 2010-04-20 02:52

To

"lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>, "karvind@enterasys.com" =
<karvind@enterasys.com>, "erosen@cisco.com" <erosen@cisco.com>, "giles.hero=
n@gmail.com" <giles.heron@gmail.com>, "flefauch@cisco.com" <flefauch@cisco.=
com>

cc

"shane@castlepoint.net" <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ie=
tf.org>

Subject

RE: WG Last Call: draft-ietf-l2vpn-ipls-09




Thanks for your comments..
Please see the response in line below.

/himanshu

From: lizhong.jin@zte.com.cn [mailto:lizhong.jin@zte.com.cn]
Sent: Saturday, April 17, 2010 11:16 AM
To: Himanshu Shah; karvind@enterasys.com; erosen@cisco.com; giles.heron@gma=
il.com; flefauch@cisco.com
Cc: shane@castlepoint.net; l2vpn@ietf.org
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09


Hi Himanshu and authors,
After reviewing draft-ietf-l2vpn-ipls-09, I have the following comments:
1. Section 2.0, point 5, bullet c, more precisely, the unicast ARP packets =
received from "multicast" pseudowire may do MAC DA lookup, and forward to w=
here CE is located. So the context should add this exception for ARP packet=
s
[Himanshu>] I am not sure I fully understand your comment, but I am guessin=
g you are asking to add text to the draft referring the unicast MAC and ARP=
 as the context
to the exception whereby normally all the packets received over "multicast"=
 PW are broadcasted, including this ARP unicast, but as an exception, in th=
is case, one
can optimize the flooding.
[Lizhong] Yes, that's exactly what I mean.

<himanshu> I have following paragraph from the draft. I have added a senten=
ce (in red). See if it addresses your comment.
Personally, I feel it is repeating what is already stated in the draft and =
does not need more clarification. I do want to clarify
on your comment that flooding optimization is not limited to ARP packets on=
ly. It is simply based on MAC DA.

   "When a unicast ARP Ethernet frame is received over the 'multicast'
   PW, PE may optionally do MAC DA lookup in the forwarding table and
   forward it to the AC where the CE is located. If the CE is not
   accessible through any local AC, the frame is dropped. Conversely,
   the PE may simply forward the frame to all the ACs associated with
   that IPLS instance without any lookup in the forwarding table."

   Typically, frames received over the 'multicast' PW are flooded to
    local ACs that are member of the IPLS instance. However, as an optimiza=
tion,
    PE may lookup MAC DA to limit the flooding based on local database. Thi=
s
    includes unicast MAC as well as multicast MAC frames.


.
2. Section 7.1, I am wondering how to setup the unidirectional mp2p pseudow=
ire. According to RFC4447, one pseudowire will be UP only when both local a=
nd remote label mapping message is sent and received. But according to the =
descripition of unidirectional mp2p pseudowire in IPLS, if PEx sends a labe=
l mapping to PEy for CEx, PEy seems to consider the PW as UP when receiving=
 the corresponding label mapping, and PEx would consider the PW as UP when =
sending out the label mapping, without the necessarity of allocating local =
labels for the PW.
[Himanshu>] There is no one-to-one correspondence with respect to PW direct=
ionality. Meaning, if PE1 has two local CE, it will advertise two labels. I=
f PE2 has 4 local CEs it will advertise 4 labels.
Which does not mean that when PE1 receives 4 labels from PE2 that it needs =
to advertise 4 labels to bring PW 'UP'. So the question, is 'unidirectional=
' PW a deviation from RFC 4447 which
assumes PW to be bi-directional (this used to be true initially, not sure i=
f still is true) by way of uniting to opposite direction unidirectional PW.=
 The unidirectional PW is not illegal.
[Lizhong] From my understanding, unidirectional point-to-point PW is not de=
fined in RFC4447. See section 5.3.3 signaling procedures in RFC4447.

<himanshu> RFC4447 is a base document and does not prevent other drafts to =
utilize and/or extend for specific application (as defined in L2VPN).
Frankly, I would consider unicast PW as a subset of the RFC4447 defined met=
hodologies.


What's more, it is also difficult to configure the PWid. If PEx uses PWid_1=
 for CEx1, and PWid_2 for CEx2, according to section 7.1, the PEy needs to =
configure both PWid_1 and PWid_2, which is actually not necessary. Do I mis=
s something important here to understand the concept of unidirectional mp2p=
 pseudowire? There may be a new type of FEC that is required, similar with =
unidirectional P2MP PW.
[Himanshu>] PWid is per IPLS instance and not per CE. I do not see any text=
 in 7.1 which talks about configuring difference PWid for each CE.
For a given IPLS instance a PE has following to signal -
a)    PW id
b)    One MP2P 'multicast'  Ethernet PW
c)    Many (i.e. one per local CE) MP2P 'unicast' IP PW along with CE's MAC=
 address
[Himanshu>] Section 7.1 describes details for send and receive processing o=
f label mapping message
[Lizhong] Do you mean PE will advertise all labels for CEs with same PWid? =
Then that means PE will advertise different labels for same FEC(same PWid),=
 which will not operate correctly under current framework. The peer PE rece=
iving several label mapping messages with same FEC but different labels wil=
l update the already received label, and only retain the newest one. The wa=
y to solve this is to define a new type of FEC to specify different operati=
on comparing with normal FEC (e.g, type 128 and 129).


<himanshu> Not true. The draft clearly states that (CE's) MAC address must =
be advertised in the LM message. The MAC address is augmented and is treate=
d as
part of PW-FEC. May be a sentence needs to be added to avoid the confusion.

3. Section 7.2, why not using LDP capability to advertising IPv6 stack capa=
bility?
[Himanshu>] Because this is specific to PW and IPLS instance
[Lizhong] actually, current P2MP PW capability negotiation uses LDP capabil=
ity. I hope we can align this, because both are related with PW capability.

<himanshu> We (authors) will look into this.

4. Will IPLS consider any spoke connectivity to increase the scalability, s=
ame as VPLS?
[Himanshu>] I am not sure I fully understand. IPLS assumes (recommends) tha=
t CEs are IP routers that act as edge box.
Meaning most of the customer's IP hosts and  other routers are behind this =
CE router in customer network and PE does
not see them. This by itself provides good hierarchy & scalability.
[Lizhong] Sorry for the unclear statement. The scalability I refer is PW sc=
alablity to construct large IPLS network, which is included in RFC4762 sect=
ion 10.1.1.

<himanshu> My feeling is that current draft is adequate for the scalability=
 that is envisioned for its applicability in the existing networks.
However, if field experience suggest that scalability is an issue, wg can u=
ndertake a separate work item to extend the architecture to address
scalability.

Hope to see your reply, thank you.

Best Regards
Lizhong Jin


------------------------------

Date: Mon, 5 Apr 2010 19:58:01 -0600
From: Shane Amante <shane@castlepoint.net>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09
To: l2vpn@ietf.org
Message-ID: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net>
Content-Type: text/plain; charset=3Dus-ascii

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e not permitted to disclose the contents of this communication to others.
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 th=
e message. Any views expressed in this message are those of the individual =
sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e not permitted to disclose the contents of this communication to others.
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 th=
e message. Any views expressed in this message are those of the individual =
sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.


--_000_C7FB85363830hshahforce10networkscom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: WG Last Call: draft-ietf-l2vpn-ipls-09</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:9pt'>Hi Lizhong Jin,<BR>
Again thanks for the comments, response to your comments in line (marked in=
 green).<BR>
/himanshu<BR>
<BR>
<BR>
<BR>
On 4/19/10 9:24 PM, &quot;<a href=3D"lizhong.jin@zte.com.cn">lizhong.jin@zt=
e.com.cn</a>&quot; &lt;<a href=3D"lizhong.jin@zte.com.cn">lizhong.jin@zte.c=
om.cn</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:=
9pt'><BR>
Hi Himanshu, <BR>
Thank you for your reply. Please see my comments in line. <BR>
<BR>
BR <BR>
Lizhong Jin <BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Arial"> <BR>
</FONT><FONT FACE=3D"Ayuthaya"><BR>
<B>Himanshu Shah &lt;<a href=3D"hshah@force10networks.com">hshah@force10net=
works.com</a>&gt;</B> 2010-04-20 02:52=20
</FONT></SPAN>
<P ALIGN=3DRIGHT>
<SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya">To
</FONT></SPAN>
<P>
<SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya">&quot;<a href=3D"lizh=
ong.jin@zte.com.cn">lizhong.jin@zte.com.cn</a>&quot; &lt;<a href=3D"lizhong=
.jin@zte.com.cn">lizhong.jin@zte.com.cn</a>&gt;, &quot;<a href=3D"karvind@e=
nterasys.com">karvind@enterasys.com</a>&quot; &lt;<a href=3D"karvind@entera=
sys.com">karvind@enterasys.com</a>&gt;, &quot;<a href=3D"erosen@cisco.com">=
erosen@cisco.com</a>&quot; &lt;<a href=3D"erosen@cisco.com">erosen@cisco.co=
m</a>&gt;, &quot;<a href=3D"giles.heron@gmail.com">giles.heron@gmail.com</a=
>&quot; &lt;<a href=3D"giles.heron@gmail.com">giles.heron@gmail.com</a>&gt;=
, &quot;<a href=3D"flefauch@cisco.com">flefauch@cisco.com</a>&quot; &lt;<a =
href=3D"flefauch@cisco.com">flefauch@cisco.com</a>&gt;=20
</FONT></SPAN>
<P ALIGN=3DRIGHT>
<SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya">cc
</FONT></SPAN>
<P>
<SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya">&quot;<a href=3D"shan=
e@castlepoint.net">shane@castlepoint.net</a>&quot; &lt;<a href=3D"shane@cas=
tlepoint.net">shane@castlepoint.net</a>&gt;, &quot;<a href=3D"l2vpn@ietf.or=
g">l2vpn@ietf.org</a>&quot; &lt;<a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</=
a>&gt;=20
</FONT></SPAN>
<P ALIGN=3DRIGHT>
<SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya">Subject
</FONT></SPAN>
<P>
<SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya">RE: WG Last Call: dra=
ft-ietf-l2vpn-ipls-09 <BR>
<BR>
<BR>
<BR>
<BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS">Thanks for your =
comments..</FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS">Please see the r=
esponse in line below.</FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"> <BR>
/himanshu</FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"> <BR>
</FONT></FONT><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"><B>From:</B>=
 <a href=3D"lizhong.jin@zte.com.cn">lizhong.jin@zte.com.cn</a> [<a href=3D"=
mailto:lizhong.jin@zte.com.cn">mailto:lizhong.jin@zte.com.cn</a>] <BR>
<B>Sent:</B> Saturday, April 17, 2010 11:16 AM<BR>
<B>To:</B> Himanshu Shah; <a href=3D"karvind@enterasys.com">karvind@enteras=
ys.com</a>; <a href=3D"erosen@cisco.com">erosen@cisco.com</a>; <a href=3D"g=
iles.heron@gmail.com">giles.heron@gmail.com</a>; <a href=3D"flefauch@cisco.=
com">flefauch@cisco.com</a><BR>
<B>Cc:</B> <a href=3D"shane@castlepoint.net">shane@castlepoint.net</a>; <a =
href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><BR>
<B>Subject:</B> Re: WG Last Call: draft-ietf-l2vpn-ipls-09</FONT><FONT FACE=
=3D"Ayuthaya"> <BR>
</FONT></SPAN><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN STYLE=
=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:9pt'><BR=
>
Hi Himanshu and authors,</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times =
New Roman"><SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:9pt'>Aft=
er reviewing draft-ietf-l2vpn-ipls-09, I have the following comments:<BR>
1. Section 2.0, point 5, bullet c, more precisely, the unicast ARP packets =
received from &quot;multicast&quot; pseudowire may do MAC DA lookup, and fo=
rward to where CE is located. So the context should add this exception for =
ARP packets</SPAN></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayutha=
ya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>[Himanshu&=
gt;] I am not sure I fully understand your comment, but I am guessing you a=
re asking to add text to the draft referring the unicast MAC and ARP as the=
 context</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>to the exc=
eption whereby normally all the packets received over &#8220;multicast&#822=
1; PW are broadcasted, including this ARP unicast, but as an exception, in =
this case, one</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>can optimi=
ze the flooding.</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"><B>[Lizhong] Yes, that'=
s exactly what I mean.</B></FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayut=
haya"><BR>
<FONT COLOR=3D"#008000">&lt;himanshu&gt; </FONT> <FONT COLOR=3D"#008000">I =
have following paragraph from the draft. I have added a sentence (in red). =
See if it addresses your comment.<BR>
Personally, I feel it is repeating what is already stated in the draft and =
does not need more clarification. I do want to clarify<BR>
on your comment that flooding optimization is not limited to ARP packets on=
ly. It is simply based on MAC DA.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&#8220;When a unicast ARP Ethernet frame is received over=
 the 'multicast' <BR>
&nbsp;&nbsp;&nbsp;PW, PE may optionally do MAC DA lookup in the forwarding =
table and <BR>
&nbsp;&nbsp;&nbsp;forward it to the AC where the CE is located. If the CE i=
s not <BR>
&nbsp;&nbsp;&nbsp;accessible through any local AC, the frame is dropped. Co=
nversely, <BR>
&nbsp;&nbsp;&nbsp;the PE may simply forward the frame to all the ACs associ=
ated with <BR>
&nbsp;&nbsp;&nbsp;that IPLS instance without any lookup in the forwarding t=
able.&#8221;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;<BR>
</FONT> &nbsp;&nbsp;&nbsp;<FONT COLOR=3D"#FF0000">Typically, frames receive=
d over the &#8216;multicast&#8217; PW are flooded to <BR>
&nbsp;&nbsp;&nbsp;&nbsp;local ACs that are member of the IPLS instance. How=
ever, as an optimization,<BR>
&nbsp;&nbsp;&nbsp;&nbsp;PE may lookup MAC DA to limit the flooding based on=
 local database. This<BR>
&nbsp;&nbsp;&nbsp;&nbsp;includes unicast MAC as well as multicast MAC frame=
s.<BR>
</FONT> &nbsp;&nbsp;<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayuth=
aya"><BR>
</FONT><FONT FACE=3D"Arial">.</FONT></SPAN><FONT SIZE=3D"4"><FONT FACE=3D"T=
imes New Roman"><SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:9pt'>2. =
Section 7.1, I am wondering how to setup the unidirectional mp2p pseudowire=
. According to RFC4447, one pseudowire will be UP only when both local and =
remote label mapping message is sent and received. But according to the des=
cripition of unidirectional mp2p pseudowire in IPLS, if PEx sends a label m=
apping to PEy for CEx, PEy seems to consider the PW as UP when receiving th=
e corresponding label mapping, and PEx would consider the PW as UP when sen=
ding out the label mapping, without the necessarity of allocating local lab=
els for the PW.</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman=
"><SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><S=
PAN STYLE=3D'font-size:9pt'><B><I>[Himanshu&gt;] There is no one-to-one cor=
respondence with respect to PW directionality. Meaning, if PE1 has two loca=
l CE, it will advertise two labels. If PE2 has 4 local CEs it will advertis=
e 4 labels. <BR>
Which does not mean that when PE1 receives 4 labels from PE2 that it needs =
to advertise 4 labels to bring PW &#8216;UP&#8217;. So the question, is &#8=
216;unidirectional&#8217; PW a deviation from RFC 4447 which <BR>
assumes PW to be bi-directional (this used to be true initially, not sure i=
f still is true) by way of uniting to opposite direction unidirectional PW.=
 The unidirectional PW is not illegal.</I></B></SPAN></FONT></FONT><SPAN ST=
YLE=3D'font-size:9pt'><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"><B>[Lizhong] From my un=
derstanding, unidirectional point-to-point PW is not defined in RFC4447. Se=
e section 5.3.3 signaling procedures in RFC4447.</B></FONT></FONT><FONT FAC=
E=3D"Ayuthaya"> <BR>
<BR>
<FONT COLOR=3D"#008000">&lt;himanshu&gt; RFC4447 is a base document and doe=
s not prevent other drafts to utilize and/or extend for specific applicatio=
n (as defined in L2VPN).<BR>
Frankly, I would consider unicast PW as a subset of the RFC4447 defined met=
hodologies.<BR>
</FONT><BR>
</FONT><FONT FACE=3D"Arial"><BR>
What's more, it is also difficult to configure the PWid. If PEx uses PWid_1=
 for CEx1, and PWid_2 for CEx2, according to section 7.1, the PEy needs to =
configure both PWid_1 and PWid_2, which is actually not necessary. Do I mis=
s something important here to understand the concept of unidirectional mp2p=
 pseudowire? There may be a new type of FEC that is required, similar with =
unidirectional P2MP PW.</FONT></SPAN><FONT SIZE=3D"4"><FONT FACE=3D"Times N=
ew Roman"><SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><S=
PAN STYLE=3D'font-size:9pt'><B><I>[Himanshu&gt;] PWid is per IPLS instance =
and not per CE. I do not see any text in 7.1 which talks about configuring =
difference PWid for each CE.</I></B></SPAN></FONT></FONT><SPAN STYLE=3D'fon=
t-size:9pt'><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>For a give=
n IPLS instance a PE has following to signal &#8211;</I></B></FONT></FONT><=
FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>a) &nbsp;&=
nbsp;&nbsp;PW id</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>b) &nbsp;&=
nbsp;&nbsp;One MP2P &#8216;multicast&#8217; &nbsp;Ethernet PW</I></B></FONT=
></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>c) &nbsp;&=
nbsp;&nbsp;Many (i.e. one per local CE) MP2P &#8216;unicast&#8217; IP PW al=
ong with CE&#8217;s MAC address</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya=
"> <BR>
</FONT></SPAN><FONT COLOR=3D"#1F497D"><FONT SIZE=3D"4"><FONT FACE=3D"Times =
New Roman"><SPAN STYLE=3D'font-size:10pt'><B><I>[Himanshu&gt;] </I></B></SP=
AN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:9p=
t'>Section 7.1 describes details for send and receive processing of label m=
apping message</SPAN></FONT></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=
=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"><B>[Lizhong] Do you mea=
n PE will advertise all labels for CEs with same PWid? Then that means PE w=
ill advertise different labels for same FEC(same PWid), which will not oper=
ate correctly under current framework. The peer PE receiving several label =
mapping messages with same FEC but different labels will update the already=
 received label, and only retain the newest one. The way to solve this is t=
o define a new type of FEC to specify different operation comparing with no=
rmal FEC (e.g, type 128 and 129).</B></FONT></FONT><FONT FACE=3D"Ayuthaya">=
 <BR>
<BR>
<BR>
<FONT COLOR=3D"#008000">&lt;himanshu&gt; Not true. The draft clearly states=
 that (CE&#8217;s) MAC address must be advertised in the LM message. The MA=
C address is augmented and is treated as<BR>
part of PW-FEC. May be a sentence needs to be added to avoid the confusion.=
<BR>
</FONT></FONT><FONT FACE=3D"Arial"><BR>
3. Section 7.2, why not using LDP capability to advertising IPv6 stack capa=
bility?</FONT></SPAN><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN =
STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><S=
PAN STYLE=3D'font-size:9pt'><B><I>[Himanshu&gt;] Because this is specific t=
o PW and IPLS instance</I></B></SPAN></FONT></FONT><SPAN STYLE=3D'font-size=
:9pt'><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"><B>[Lizhong] actually, =
current P2MP PW capability negotiation uses LDP capability. I hope we can a=
lign this, because both are related with PW capability.</B></FONT></FONT><F=
ONT FACE=3D"Ayuthaya"> <BR>
<BR>
<FONT COLOR=3D"#008000">&lt;himanshu&gt; We (authors) will look into this.<=
BR>
</FONT></FONT><FONT FACE=3D"Arial"><BR>
4. Will IPLS consider any spoke connectivity to increase the scalability, s=
ame as VPLS?</FONT></SPAN><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><=
SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><S=
PAN STYLE=3D'font-size:9pt'><B><I>[Himanshu&gt;] I am not sure I fully unde=
rstand. IPLS assumes (recommends) that CEs are IP routers that act as edge =
box.</I></B></SPAN></FONT></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=
=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>Meaning mo=
st of the customer&#8217;s IP hosts and &nbsp;other routers are behind this=
 CE router in customer network and PE does</I></B></FONT></FONT><FONT FACE=
=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><B><I>not see th=
em. This by itself provides good hierarchy &amp; scalability. <BR>
</I></B></FONT></FONT><B><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial">[Lizh=
ong] Sorry for the unclear statement. The scalability I refer is PW scalabl=
ity to construct large IPLS network, which is included in RFC4762 section 1=
0.1.1.</FONT></FONT><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Trebuchet MS"><I>=
 <BR>
</I></FONT></FONT></B></SPAN><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman=
"><SPAN STYLE=3D'font-size:10pt'><BR>
</SPAN></FONT></FONT><FONT COLOR=3D"#008000"><FONT FACE=3D"Ayuthaya"><SPAN =
STYLE=3D'font-size:9pt'>&lt;himanshu&gt; My feeling is that current draft i=
s adequate for the scalability that is envisioned for its applicability in =
the existing networks.<BR>
However, if field experience suggest that scalability is an issue, wg can u=
ndertake a separate work item to extend the architecture to address<BR>
scalability. &nbsp;&nbsp;<BR>
</SPAN></FONT></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Arial"><BR=
>
Hope to see your reply, thank you.</FONT></SPAN><FONT SIZE=3D"4"><FONT FACE=
=3D"Times New Roman"><SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:9pt'><BR=
>
Best Regards</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><=
SPAN STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:9pt'>Liz=
hong Jin</SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN=
 STYLE=3D'font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Arial"><SPAN STYLE=3D'font-size:9pt'> </=
SPAN></FONT><FONT SIZE=3D"4"><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'=
font-size:10pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Courier New"><SPAN STYLE=3D'font-size:9p=
t'><BR>
------------------------------<BR>
<BR>
Date: Mon, 5 Apr 2010 19:58:01 -0600<BR>
From: Shane Amante &lt;<a href=3D"shane@castlepoint.net">shane@castlepoint.=
net</a>&gt;<BR>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<BR>
To: <a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><BR>
Message-ID: &lt;<a href=3D"7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint=
.net">7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net</a>&gt;<BR>
Content-Type: text/plain; charset=3Dus-ascii<BR>
<BR>
Hi Everyone,<BR>
<BR>
This is to begin a (final) WG Last Call on:<BR>
<a href=3D"http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09">http://tool=
s.ietf.org/html/draft-ietf-l2vpn-ipls-09</a><BR>
<BR>
If you have substantial technical comments or concerns, please share them w=
ith the list. &nbsp;If you have editorial comments, please share them direc=
tly with the authors and co-chairs.<BR>
<BR>
So far, we have the following folks signed up for a thorough review and com=
ments:<BR>
- Andy Malis<BR>
- Nick DelRegno<BR>
- Pranjal Dutta<BR>
However, we could use more people to conduct a review. &nbsp;If you have th=
e time and/or inclination, please let the chairs know if you'll be conducti=
ng a review.<BR>
<BR>
The Last Call on this draft will also end on April 23.<BR>
<BR>
Thanks,<BR>
<BR>
Giles &amp; Shane</SPAN></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"=
Ayuthaya"> <BR>
</FONT><FONT FACE=3D"Courier New"> <BR>
--------------------------------------------------------</FONT><FONT FACE=
=3D"Ayuthaya"> <BR>
</FONT><FONT FACE=3D"Courier New">ZTE Information Security Notice: The info=
rmation contained in this mail is solely property of the sender's organizat=
ion. This mail communication is confidential. Recipients named above are ob=
ligated to maintain secrecy and are not permitted to disclose the contents =
of this communication to others.</FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT FACE=3D"Courier New">This email and any files transmitted with=
 it are confidential and intended solely for the use of the individual or e=
ntity to whom they are addressed. If you have received this email in error =
please notify the originator of the message. Any views expressed in this me=
ssage are those of the individual sender.</FONT><FONT FACE=3D"Ayuthaya"> <B=
R>
</FONT><FONT FACE=3D"Courier New">This message has been scanned for viruses=
 and Spam by ZTE Anti-Spam system.</FONT><FONT FACE=3D"Ayuthaya"> <BR>
<BR>
<BR>
--------------------------------------------------------<BR>
ZTE Information Security Notice: The information contained in this mail is =
solely property of the sender's organization. This mail communication is co=
nfidential. Recipients named above are obligated to maintain secrecy and ar=
e not permitted to disclose the contents of this communication to others.<B=
R>
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 th=
e message. Any views expressed in this message are those of the individual =
sender.<BR>
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.=
<BR>
<BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C7FB85363830hshahforce10networkscom_--

From lizhong.jin@zte.com.cn  Mon Apr 26 18:19:28 2010
Return-Path: <lizhong.jin@zte.com.cn>
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 4C7E33A6AC9 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 18:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.814
X-Spam-Level: 
X-Spam-Status: No, score=-98.814 tagged_above=-999 required=5 tests=[AWL=-1.929, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6-Kxe8U0sThJ for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 18:19:25 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 1BA763A6ABB for <l2vpn@ietf.org>; Mon, 26 Apr 2010 18:19:20 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 36887577109098; Tue, 27 Apr 2010 09:15:11 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 57638.6570126373; Tue, 27 Apr 2010 09:15:06 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o3R1IZ3P071379; Tue, 27 Apr 2010 09:18:35 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <C7FB8536.3830%hshah@force10networks.com>
To: Himanshu Shah <hshah@force10networks.com>
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF623D5ADF.B723124B-ON48257712.0004D2F2-48257712.00072FE2@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Tue, 27 Apr 2010 09:18:26 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-27 09:18:31, Serialize complete at 2010-04-27 09:18:31
Content-Type: multipart/alternative; boundary="=_alternative 00072FDF48257712_="
X-MAIL: mse2.zte.com.cn o3R1IZ3P071379
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "flefauch@cisco.com" <flefauch@cisco.com>, "lmartini@cisco.com" <lmartini@cisco.com>, "giles.heron@gmail.com" <giles.heron@gmail.com>, "shane@castlepoint.net" <shane@castlepoint.net>, "erosen@cisco.com" <erosen@cisco.com>, Krishnamoorthy Arvind <karvind@enterasys.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: Tue, 27 Apr 2010 01:19:29 -0000

This is a multipart message in MIME format.
--=_alternative 00072FDF48257712_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgSGltYW5zaHUsDQpUaGFuayB5b3UgZm9yIHlvdXIgcmVwbHkuIFBsZWFzZSBzZWUgbXkgbmV3
IGNvbW1lbnRzIHdpdGggaXRhbGljIGZvcm1hdCBpbiANCmxpbmUuDQoNCkJSDQpMaXpob25nIEpp
bg0KDQoNCkZyb206IGxpemhvbmcuamluQHp0ZS5jb20uY24gW21haWx0bzpsaXpob25nLmppbkB6
dGUuY29tLmNuXSANClNlbnQ6IFNhdHVyZGF5LCBBcHJpbCAxNywgMjAxMCAxMToxNiBBTQ0KVG86
IEhpbWFuc2h1IFNoYWg7IGthcnZpbmRAZW50ZXJhc3lzLmNvbTsgZXJvc2VuQGNpc2NvLmNvbTsg
DQpnaWxlcy5oZXJvbkBnbWFpbC5jb207IGZsZWZhdWNoQGNpc2NvLmNvbQ0KQ2M6IHNoYW5lQGNh
c3RsZXBvaW50Lm5ldDsgbDJ2cG5AaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBXRyBMYXN0IENhbGw6
IGRyYWZ0LWlldGYtbDJ2cG4taXBscy0wOSANCg0KDQpIaSBIaW1hbnNodSBhbmQgYXV0aG9ycywg
DQpBZnRlciByZXZpZXdpbmcgZHJhZnQtaWV0Zi1sMnZwbi1pcGxzLTA5LCBJIGhhdmUgdGhlIGZv
bGxvd2luZyBjb21tZW50czoNCjEuIFNlY3Rpb24gMi4wLCBwb2ludCA1LCBidWxsZXQgYywgbW9y
ZSBwcmVjaXNlbHksIHRoZSB1bmljYXN0IEFSUCBwYWNrZXRzIA0KcmVjZWl2ZWQgZnJvbSAibXVs
dGljYXN0IiBwc2V1ZG93aXJlIG1heSBkbyBNQUMgREEgbG9va3VwLCBhbmQgZm9yd2FyZCB0byAN
CndoZXJlIENFIGlzIGxvY2F0ZWQuIFNvIHRoZSBjb250ZXh0IHNob3VsZCBhZGQgdGhpcyBleGNl
cHRpb24gZm9yIEFSUCANCnBhY2tldHMgDQpbSGltYW5zaHU+XSBJIGFtIG5vdCBzdXJlIEkgZnVs
bHkgdW5kZXJzdGFuZCB5b3VyIGNvbW1lbnQsIGJ1dCBJIGFtIA0KZ3Vlc3NpbmcgeW91IGFyZSBh
c2tpbmcgdG8gYWRkIHRleHQgdG8gdGhlIGRyYWZ0IHJlZmVycmluZyB0aGUgdW5pY2FzdCBNQUMg
DQphbmQgQVJQIGFzIHRoZSBjb250ZXh0IA0KdG8gdGhlIGV4Y2VwdGlvbiB3aGVyZWJ5IG5vcm1h
bGx5IGFsbCB0aGUgcGFja2V0cyByZWNlaXZlZCBvdmVyIKGwDQptdWx0aWNhc3ShsSBQVyBhcmUg
YnJvYWRjYXN0ZWQsIGluY2x1ZGluZyB0aGlzIEFSUCB1bmljYXN0LCBidXQgYXMgYW4gDQpleGNl
cHRpb24sIGluIHRoaXMgY2FzZSwgb25lIA0KY2FuIG9wdGltaXplIHRoZSBmbG9vZGluZy4gDQpb
TGl6aG9uZ10gWWVzLCB0aGF0J3MgZXhhY3RseSB3aGF0IEkgbWVhbi4gDQoNCjxoaW1hbnNodT4g
SSBoYXZlIGZvbGxvd2luZyBwYXJhZ3JhcGggZnJvbSB0aGUgZHJhZnQuIEkgaGF2ZSBhZGRlZCBh
IA0Kc2VudGVuY2UgKGluIHJlZCkuIFNlZSBpZiBpdCBhZGRyZXNzZXMgeW91ciBjb21tZW50Lg0K
UGVyc29uYWxseSwgSSBmZWVsIGl0IGlzIHJlcGVhdGluZyB3aGF0IGlzIGFscmVhZHkgc3RhdGVk
IGluIHRoZSBkcmFmdCBhbmQgDQpkb2VzIG5vdCBuZWVkIG1vcmUgY2xhcmlmaWNhdGlvbi4gSSBk
byB3YW50IHRvIGNsYXJpZnkNCm9uIHlvdXIgY29tbWVudCB0aGF0IGZsb29kaW5nIG9wdGltaXph
dGlvbiBpcyBub3QgbGltaXRlZCB0byBBUlAgcGFja2V0cyANCm9ubHkuIEl0IGlzIHNpbXBseSBi
YXNlZCBvbiBNQUMgREEuDQoNCiAgIKGwV2hlbiBhIHVuaWNhc3QgQVJQIEV0aGVybmV0IGZyYW1l
IGlzIHJlY2VpdmVkIG92ZXIgdGhlICdtdWx0aWNhc3QnIA0KICAgUFcsIFBFIG1heSBvcHRpb25h
bGx5IGRvIE1BQyBEQSBsb29rdXAgaW4gdGhlIGZvcndhcmRpbmcgdGFibGUgYW5kIA0KICAgZm9y
d2FyZCBpdCB0byB0aGUgQUMgd2hlcmUgdGhlIENFIGlzIGxvY2F0ZWQuIElmIHRoZSBDRSBpcyBu
b3QgDQogICBhY2Nlc3NpYmxlIHRocm91Z2ggYW55IGxvY2FsIEFDLCB0aGUgZnJhbWUgaXMgZHJv
cHBlZC4gQ29udmVyc2VseSwgDQogICB0aGUgUEUgbWF5IHNpbXBseSBmb3J3YXJkIHRoZSBmcmFt
ZSB0byBhbGwgdGhlIEFDcyBhc3NvY2lhdGVkIHdpdGggDQogICB0aGF0IElQTFMgaW5zdGFuY2Ug
d2l0aG91dCBhbnkgbG9va3VwIGluIHRoZSBmb3J3YXJkaW5nIHRhYmxlLqGxDQogICAgDQogICBU
eXBpY2FsbHksIGZyYW1lcyByZWNlaXZlZCBvdmVyIHRoZSChrm11bHRpY2FzdKGvIFBXIGFyZSBm
bG9vZGVkIHRvIA0KICAgIGxvY2FsIEFDcyB0aGF0IGFyZSBtZW1iZXIgb2YgdGhlIElQTFMgaW5z
dGFuY2UuIEhvd2V2ZXIsIGFzIGFuIA0Kb3B0aW1pemF0aW9uLA0KICAgIFBFIG1heSBsb29rdXAg
TUFDIERBIHRvIGxpbWl0IHRoZSBmbG9vZGluZyBiYXNlZCBvbiBsb2NhbCBkYXRhYmFzZS4gDQpU
aGlzDQogICAgaW5jbHVkZXMgdW5pY2FzdCBNQUMgYXMgd2VsbCBhcyBtdWx0aWNhc3QgTUFDIGZy
YW1lcy4NCltMaXpob25nXSBOb3cgaXQgaXMgZmluZSBmb3IgbWUuDQoNCi4gDQoyLiBTZWN0aW9u
IDcuMSwgSSBhbSB3b25kZXJpbmcgaG93IHRvIHNldHVwIHRoZSB1bmlkaXJlY3Rpb25hbCBtcDJw
IA0KcHNldWRvd2lyZS4gQWNjb3JkaW5nIHRvIFJGQzQ0NDcsIG9uZSBwc2V1ZG93aXJlIHdpbGwg
YmUgVVAgb25seSB3aGVuIGJvdGggDQpsb2NhbCBhbmQgcmVtb3RlIGxhYmVsIG1hcHBpbmcgbWVz
c2FnZSBpcyBzZW50IGFuZCByZWNlaXZlZC4gQnV0IGFjY29yZGluZyANCnRvIHRoZSBkZXNjcmlw
aXRpb24gb2YgdW5pZGlyZWN0aW9uYWwgbXAycCBwc2V1ZG93aXJlIGluIElQTFMsIGlmIFBFeCAN
CnNlbmRzIGEgbGFiZWwgbWFwcGluZyB0byBQRXkgZm9yIENFeCwgUEV5IHNlZW1zIHRvIGNvbnNp
ZGVyIHRoZSBQVyBhcyBVUCANCndoZW4gcmVjZWl2aW5nIHRoZSBjb3JyZXNwb25kaW5nIGxhYmVs
IG1hcHBpbmcsIGFuZCBQRXggd291bGQgY29uc2lkZXIgdGhlIA0KUFcgYXMgVVAgd2hlbiBzZW5k
aW5nIG91dCB0aGUgbGFiZWwgbWFwcGluZywgd2l0aG91dCB0aGUgbmVjZXNzYXJpdHkgb2YgDQph
bGxvY2F0aW5nIGxvY2FsIGxhYmVscyBmb3IgdGhlIFBXLiANCltIaW1hbnNodT5dIFRoZXJlIGlz
IG5vIG9uZS10by1vbmUgY29ycmVzcG9uZGVuY2Ugd2l0aCByZXNwZWN0IHRvIFBXIA0KZGlyZWN0
aW9uYWxpdHkuIE1lYW5pbmcsIGlmIFBFMSBoYXMgdHdvIGxvY2FsIENFLCBpdCB3aWxsIGFkdmVy
dGlzZSB0d28gDQpsYWJlbHMuIElmIFBFMiBoYXMgNCBsb2NhbCBDRXMgaXQgd2lsbCBhZHZlcnRp
c2UgNCBsYWJlbHMuIA0KV2hpY2ggZG9lcyBub3QgbWVhbiB0aGF0IHdoZW4gUEUxIHJlY2VpdmVz
IDQgbGFiZWxzIGZyb20gUEUyIHRoYXQgaXQgbmVlZHMgDQp0byBhZHZlcnRpc2UgNCBsYWJlbHMg
dG8gYnJpbmcgUFcgoa5VUKGvLiBTbyB0aGUgcXVlc3Rpb24sIGlzIKGuDQp1bmlkaXJlY3Rpb25h
bKGvIFBXIGEgZGV2aWF0aW9uIGZyb20gUkZDIDQ0NDcgd2hpY2ggDQphc3N1bWVzIFBXIHRvIGJl
IGJpLWRpcmVjdGlvbmFsICh0aGlzIHVzZWQgdG8gYmUgdHJ1ZSBpbml0aWFsbHksIG5vdCBzdXJl
IA0KaWYgc3RpbGwgaXMgdHJ1ZSkgYnkgd2F5IG9mIHVuaXRpbmcgdG8gb3Bwb3NpdGUgZGlyZWN0
aW9uIHVuaWRpcmVjdGlvbmFsIA0KUFcuIFRoZSB1bmlkaXJlY3Rpb25hbCBQVyBpcyBub3QgaWxs
ZWdhbC4gDQpbTGl6aG9uZ10gRnJvbSBteSB1bmRlcnN0YW5kaW5nLCB1bmlkaXJlY3Rpb25hbCBw
b2ludC10by1wb2ludCBQVyBpcyBub3QgDQpkZWZpbmVkIGluIFJGQzQ0NDcuIFNlZSBzZWN0aW9u
IDUuMy4zIHNpZ25hbGluZyBwcm9jZWR1cmVzIGluIFJGQzQ0NDcuIA0KDQo8aGltYW5zaHU+IFJG
QzQ0NDcgaXMgYSBiYXNlIGRvY3VtZW50IGFuZCBkb2VzIG5vdCBwcmV2ZW50IG90aGVyIGRyYWZ0
cyB0byANCnV0aWxpemUgYW5kL29yIGV4dGVuZCBmb3Igc3BlY2lmaWMgYXBwbGljYXRpb24gKGFz
IGRlZmluZWQgaW4gTDJWUE4pLg0KRnJhbmtseSwgSSB3b3VsZCBjb25zaWRlciB1bmljYXN0IFBX
IGFzIGEgc3Vic2V0IG9mIHRoZSBSRkM0NDQ3IGRlZmluZWQgDQptZXRob2RvbG9naWVzLg0KDQpX
aGF0J3MgbW9yZSwgaXQgaXMgYWxzbyBkaWZmaWN1bHQgdG8gY29uZmlndXJlIHRoZSBQV2lkLiBJ
ZiBQRXggdXNlcyANClBXaWRfMSBmb3IgQ0V4MSwgYW5kIFBXaWRfMiBmb3IgQ0V4MiwgYWNjb3Jk
aW5nIHRvIHNlY3Rpb24gNy4xLCB0aGUgUEV5IA0KbmVlZHMgdG8gY29uZmlndXJlIGJvdGggUFdp
ZF8xIGFuZCBQV2lkXzIsIHdoaWNoIGlzIGFjdHVhbGx5IG5vdCANCm5lY2Vzc2FyeS4gRG8gSSBt
aXNzIHNvbWV0aGluZyBpbXBvcnRhbnQgaGVyZSB0byB1bmRlcnN0YW5kIHRoZSBjb25jZXB0IG9m
IA0KdW5pZGlyZWN0aW9uYWwgbXAycCBwc2V1ZG93aXJlPyBUaGVyZSBtYXkgYmUgYSBuZXcgdHlw
ZSBvZiBGRUMgdGhhdCBpcyANCnJlcXVpcmVkLCBzaW1pbGFyIHdpdGggdW5pZGlyZWN0aW9uYWwg
UDJNUCBQVy4gDQpbSGltYW5zaHU+XSBQV2lkIGlzIHBlciBJUExTIGluc3RhbmNlIGFuZCBub3Qg
cGVyIENFLiBJIGRvIG5vdCBzZWUgYW55IA0KdGV4dCBpbiA3LjEgd2hpY2ggdGFsa3MgYWJvdXQg
Y29uZmlndXJpbmcgZGlmZmVyZW5jZSBQV2lkIGZvciBlYWNoIENFLiANCkZvciBhIGdpdmVuIElQ
TFMgaW5zdGFuY2UgYSBQRSBoYXMgZm9sbG93aW5nIHRvIHNpZ25hbCCoQyANCmEpICAgIFBXIGlk
IA0KYikgICAgT25lIE1QMlAgoa5tdWx0aWNhc3ShryAgRXRoZXJuZXQgUFcgDQpjKSAgICBNYW55
IChpLmUuIG9uZSBwZXIgbG9jYWwgQ0UpIE1QMlAgoa51bmljYXN0oa8gSVAgUFcgYWxvbmcgd2l0
aCBDRaGvcyANCk1BQyBhZGRyZXNzIA0KW0hpbWFuc2h1Pl0gU2VjdGlvbiA3LjEgZGVzY3JpYmVz
IGRldGFpbHMgZm9yIHNlbmQgYW5kIHJlY2VpdmUgcHJvY2Vzc2luZyANCm9mIGxhYmVsIG1hcHBp
bmcgbWVzc2FnZSANCltMaXpob25nXSBEbyB5b3UgbWVhbiBQRSB3aWxsIGFkdmVydGlzZSBhbGwg
bGFiZWxzIGZvciBDRXMgd2l0aCBzYW1lIFBXaWQ/IA0KVGhlbiB0aGF0IG1lYW5zIFBFIHdpbGwg
YWR2ZXJ0aXNlIGRpZmZlcmVudCBsYWJlbHMgZm9yIHNhbWUgRkVDKHNhbWUgDQpQV2lkKSwgd2hp
Y2ggd2lsbCBub3Qgb3BlcmF0ZSBjb3JyZWN0bHkgdW5kZXIgY3VycmVudCBmcmFtZXdvcmsuIFRo
ZSBwZWVyIA0KUEUgcmVjZWl2aW5nIHNldmVyYWwgbGFiZWwgbWFwcGluZyBtZXNzYWdlcyB3aXRo
IHNhbWUgRkVDIGJ1dCBkaWZmZXJlbnQgDQpsYWJlbHMgd2lsbCB1cGRhdGUgdGhlIGFscmVhZHkg
cmVjZWl2ZWQgbGFiZWwsIGFuZCBvbmx5IHJldGFpbiB0aGUgbmV3ZXN0IA0Kb25lLiBUaGUgd2F5
IHRvIHNvbHZlIHRoaXMgaXMgdG8gZGVmaW5lIGEgbmV3IHR5cGUgb2YgRkVDIHRvIHNwZWNpZnkg
DQpkaWZmZXJlbnQgb3BlcmF0aW9uIGNvbXBhcmluZyB3aXRoIG5vcm1hbCBGRUMgKGUuZywgdHlw
ZSAxMjggYW5kIDEyOSkuIA0KDQoNCjxoaW1hbnNodT4gTm90IHRydWUuIFRoZSBkcmFmdCBjbGVh
cmx5IHN0YXRlcyB0aGF0IChDRaGvcykgTUFDIGFkZHJlc3MgDQptdXN0IGJlIGFkdmVydGlzZWQg
aW4gdGhlIExNIG1lc3NhZ2UuIFRoZSBNQUMgYWRkcmVzcyBpcyBhdWdtZW50ZWQgYW5kIGlzIA0K
dHJlYXRlZCBhcw0KcGFydCBvZiBQVy1GRUMuIE1heSBiZSBhIHNlbnRlbmNlIG5lZWRzIHRvIGJl
IGFkZGVkIHRvIGF2b2lkIHRoZSANCmNvbmZ1c2lvbi4NCltMaXpob25nXSBOb3cgSSBnZXQgeW91
ciBtZWFuaW5nLiBUaGVuIHRoZSBtZXRob2QgZGVzY3JpYmVkIGluIGRyYWZ0IGlzIA0KaW1wbGVt
ZW50YWJsZSwgYnV0IHRoZSBGRUMgZGVmaW5pdGlvbiBpcyBub3QgZ29vZCBpZiBNQUMgYWRkcmVz
cyBpcyANCmF1Z21lbnRlZCB0byBQVy1GRUMuIEkgY2FuIHN1bW1hcmlzZSBsaWtlIHRoYXQgd2hl
biBQRSBhZHZlcnRpc2Ugb25lIEZFQyANCihlLmcsIHR5cGUgMTI4IG9yIDEyOSkgd2l0aCBNQUMg
YWRkcmVzcyBhbmQgSVAgUFcgdHlwZSwgdGhlbiBQRSBzaG91bGQgDQp0cmVhdCBpdCBhcyBhbiB1
bmlkaXJlY3Rpb25hbCBQVyBhbmQgYWxsb2NhdGUgYSBsYWJlbCBmb3IgY29tYmluYXRpb24gb2Yg
DQpGRUMgYW5kIE1BQyBhZGRyZXNzLiBUaGUgY29uY2VwdCBpcyBhIGJpdCBkaWZmZXJlbnQgd2l0
aCB0aGUgdHJhZGl0aW9uYWwgDQpvbmUgKFJGQzUwMzYpIHdoZXJlIFBFIHdpbGwgb25seSBhbGxv
Y2F0ZSBsYWJlbCBmb3IgRkVDIHdpdGhvdXQgDQpjb25zaWRlcmluZyBhbnkgb3RoZXIgdmFsdWUu
IEEgY2xhcmlmaWVkIHNlbnRhbmNlIG1heSBub3Qgc3VmZmljaWVudCANCmhlcmUuLi4uLi5hIG5l
dyB0eXBlIG9mIEZFQyB3b3VsZCBiZSBiZXN0IGZyb20gbXkgdW5kZXJzdGFuZGluZy4NCg0KDQoz
LiBTZWN0aW9uIDcuMiwgd2h5IG5vdCB1c2luZyBMRFAgY2FwYWJpbGl0eSB0byBhZHZlcnRpc2lu
ZyBJUHY2IHN0YWNrIA0KY2FwYWJpbGl0eT8gDQpbSGltYW5zaHU+XSBCZWNhdXNlIHRoaXMgaXMg
c3BlY2lmaWMgdG8gUFcgYW5kIElQTFMgaW5zdGFuY2UgDQpbTGl6aG9uZ10gYWN0dWFsbHksIGN1
cnJlbnQgUDJNUCBQVyBjYXBhYmlsaXR5IG5lZ290aWF0aW9uIHVzZXMgTERQIA0KY2FwYWJpbGl0
eS4gSSBob3BlIHdlIGNhbiBhbGlnbiB0aGlzLCBiZWNhdXNlIGJvdGggYXJlIHJlbGF0ZWQgd2l0
aCBQVyANCmNhcGFiaWxpdHkuIA0KDQo8aGltYW5zaHU+IFdlIChhdXRob3JzKSB3aWxsIGxvb2sg
aW50byB0aGlzLg0KW0xpemhvbmddIFRoYXQncyBnb29kLg0KDQoNCjQuIFdpbGwgSVBMUyBjb25z
aWRlciBhbnkgc3Bva2UgY29ubmVjdGl2aXR5IHRvIGluY3JlYXNlIHRoZSBzY2FsYWJpbGl0eSwg
DQpzYW1lIGFzIFZQTFM/IA0KW0hpbWFuc2h1Pl0gSSBhbSBub3Qgc3VyZSBJIGZ1bGx5IHVuZGVy
c3RhbmQuIElQTFMgYXNzdW1lcyAocmVjb21tZW5kcykgDQp0aGF0IENFcyBhcmUgSVAgcm91dGVy
cyB0aGF0IGFjdCBhcyBlZGdlIGJveC4gDQpNZWFuaW5nIG1vc3Qgb2YgdGhlIGN1c3RvbWVyoa9z
IElQIGhvc3RzIGFuZCAgb3RoZXIgcm91dGVycyBhcmUgYmVoaW5kIA0KdGhpcyBDRSByb3V0ZXIg
aW4gY3VzdG9tZXIgbmV0d29yayBhbmQgUEUgZG9lcyANCm5vdCBzZWUgdGhlbS4gVGhpcyBieSBp
dHNlbGYgcHJvdmlkZXMgZ29vZCBoaWVyYXJjaHkgJiBzY2FsYWJpbGl0eS4gDQpbTGl6aG9uZ10g
U29ycnkgZm9yIHRoZSB1bmNsZWFyIHN0YXRlbWVudC4gVGhlIHNjYWxhYmlsaXR5IEkgcmVmZXIg
aXMgUFcgDQpzY2FsYWJsaXR5IHRvIGNvbnN0cnVjdCBsYXJnZSBJUExTIG5ldHdvcmssIHdoaWNo
IGlzIGluY2x1ZGVkIGluIFJGQzQ3NjIgDQpzZWN0aW9uIDEwLjEuMS4gDQoNCjxoaW1hbnNodT4g
TXkgZmVlbGluZyBpcyB0aGF0IGN1cnJlbnQgZHJhZnQgaXMgYWRlcXVhdGUgZm9yIHRoZSANCnNj
YWxhYmlsaXR5IHRoYXQgaXMgZW52aXNpb25lZCBmb3IgaXRzIGFwcGxpY2FiaWxpdHkgaW4gdGhl
IGV4aXN0aW5nIA0KbmV0d29ya3MuDQpIb3dldmVyLCBpZiBmaWVsZCBleHBlcmllbmNlIHN1Z2dl
c3QgdGhhdCBzY2FsYWJpbGl0eSBpcyBhbiBpc3N1ZSwgd2cgY2FuIA0KdW5kZXJ0YWtlIGEgc2Vw
YXJhdGUgd29yayBpdGVtIHRvIGV4dGVuZCB0aGUgYXJjaGl0ZWN0dXJlIHRvIGFkZHJlc3MNCnNj
YWxhYmlsaXR5LiANCltMaXpob25nXSBUaGF0J3MgT0suDQoNCkhvcGUgdG8gc2VlIHlvdXIgcmVw
bHksIHRoYW5rIHlvdS4gDQoNCkJlc3QgUmVnYXJkcyANCkxpemhvbmcgSmluIA0KDQoNCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpEYXRlOiBNb24sIDUgQXByIDIwMTAgMTk6NTg6
MDEgLTA2MDANCkZyb206IFNoYW5lIEFtYW50ZSA8c2hhbmVAY2FzdGxlcG9pbnQubmV0Pg0KU3Vi
amVjdDogV0cgTGFzdCBDYWxsOiBkcmFmdC1pZXRmLWwydnBuLWlwbHMtMDkNClRvOiBsMnZwbkBp
ZXRmLm9yZw0KTWVzc2FnZS1JRDogPDdCNkM1MDQwLUMxMDMtNDYyNi04M0Y4LTYxODMzMUY2OEJD
RUBjYXN0bGVwb2ludC5uZXQ+DQpDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9dXMt
YXNjaWkNCg0KSGkgRXZlcnlvbmUsDQoNClRoaXMgaXMgdG8gYmVnaW4gYSAoZmluYWwpIFdHIExh
c3QgQ2FsbCBvbjoNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbDJ2cG4t
aXBscy0wOQ0KDQpJZiB5b3UgaGF2ZSBzdWJzdGFudGlhbCB0ZWNobmljYWwgY29tbWVudHMgb3Ig
Y29uY2VybnMsIHBsZWFzZSBzaGFyZSB0aGVtIA0Kd2l0aCB0aGUgbGlzdC4gIElmIHlvdSBoYXZl
IGVkaXRvcmlhbCBjb21tZW50cywgcGxlYXNlIHNoYXJlIHRoZW0gZGlyZWN0bHkgDQp3aXRoIHRo
ZSBhdXRob3JzIGFuZCBjby1jaGFpcnMuDQoNClNvIGZhciwgd2UgaGF2ZSB0aGUgZm9sbG93aW5n
IGZvbGtzIHNpZ25lZCB1cCBmb3IgYSB0aG9yb3VnaCByZXZpZXcgYW5kIA0KY29tbWVudHM6DQot
IEFuZHkgTWFsaXMNCi0gTmljayBEZWxSZWdubw0KLSBQcmFuamFsIER1dHRhDQpIb3dldmVyLCB3
ZSBjb3VsZCB1c2UgbW9yZSBwZW9wbGUgdG8gY29uZHVjdCBhIHJldmlldy4gIElmIHlvdSBoYXZl
IHRoZSANCnRpbWUgYW5kL29yIGluY2xpbmF0aW9uLCBwbGVhc2UgbGV0IHRoZSBjaGFpcnMga25v
dyBpZiB5b3UnbGwgYmUgDQpjb25kdWN0aW5nIGEgcmV2aWV3Lg0KDQpUaGUgTGFzdCBDYWxsIG9u
IHRoaXMgZHJhZnQgd2lsbCBhbHNvIGVuZCBvbiBBcHJpbCAyMy4NCg0KVGhhbmtzLA0KDQpHaWxl
cyAmIFNoYW5lIA0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLSANClpURSBJbmZvcm1hdGlvbiBTZWN1cml0eSBOb3RpY2U6IFRoZSBpbmZv
cm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWlsIGlzIA0Kc29sZWx5IHByb3BlcnR5IG9mIHRo
ZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uIGlzIA0KY29u
ZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFib3ZlIGFyZSBvYmxpZ2F0ZWQgdG8gbWFpbnRh
aW4gc2VjcmVjeSBhbmQgDQphcmUgbm90IHBlcm1pdHRlZCB0byBkaXNjbG9zZSB0aGUgY29udGVu
dHMgb2YgdGhpcyBjb21tdW5pY2F0aW9uIHRvIA0Kb3RoZXJzLiANClRoaXMgZW1haWwgYW5kIGFu
eSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwgYW5kIGludGVuZGVk
IA0Kc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSB0byB3aG9t
IHRoZXkgYXJlIGFkZHJlc3NlZC4gDQpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGlu
IGVycm9yIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YgDQp0aGUgbWVzc2FnZS4gQW55
IHZpZXdzIGV4cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3NlIG9mIHRoZSANCmluZGl2
aWR1YWwgc2VuZGVyLiANClRoaXMgbWVzc2FnZSBoYXMgYmVlbiBzY2FubmVkIGZvciB2aXJ1c2Vz
IGFuZCBTcGFtIGJ5IFpURSBBbnRpLVNwYW0gDQpzeXN0ZW0uIA0KDQoNCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUgSW5mb3JtYXRp
b24gU2VjdXJpdHkgTm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFp
bCBpcyANCnNvbGVseSBwcm9wZXJ0eSBvZiB0aGUgc2VuZGVyJ3Mgb3JnYW5pemF0aW9uLiBUaGlz
IG1haWwgY29tbXVuaWNhdGlvbiBpcyANCmNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1lZCBh
Ym92ZSBhcmUgb2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kgYW5kIA0KYXJlIG5vdCBwZXJt
aXR0ZWQgdG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byAN
Cm90aGVycy4NClRoaXMgZW1haWwgYW5kIGFueSBmaWxlcyB0cmFuc21pdHRlZCB3aXRoIGl0IGFy
ZSBjb25maWRlbnRpYWwgYW5kIGludGVuZGVkIA0Kc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBp
bmRpdmlkdWFsIG9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gDQpJZiB5b3Ug
aGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdp
bmF0b3Igb2YgDQp0aGUgbWVzc2FnZS4gQW55IHZpZXdzIGV4cHJlc3NlZCBpbiB0aGlzIG1lc3Nh
Z2UgYXJlIHRob3NlIG9mIHRoZSANCmluZGl2aWR1YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhh
cyBiZWVuIHNjYW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSANCnN5
c3RlbS4NCg0KDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NClpURSBJbmZvcm1hdGlvbiBTZWN1cml0eSBOb3RpY2U6IFRoZSBpbmZv
cm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWlsIGlzIHNvbGVseSBwcm9wZXJ0eSBvZiB0aGUg
c2VuZGVyJ3Mgb3JnYW5pemF0aW9uLiBUaGlzIG1haWwgY29tbXVuaWNhdGlvbiBpcyBjb25maWRl
bnRpYWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZCB0byBtYWludGFpbiBz
ZWNyZWN5IGFuZCBhcmUgbm90IHBlcm1pdHRlZCB0byBkaXNjbG9zZSB0aGUgY29udGVudHMgb2Yg
dGhpcyBjb21tdW5pY2F0aW9uIHRvIG90aGVycy4NClRoaXMgZW1haWwgYW5kIGFueSBmaWxlcyB0
cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwgYW5kIGludGVuZGVkIHNvbGVseSBm
b3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hvbSB0aGV5IGFyZSBh
ZGRyZXNzZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IgcGxlYXNl
IG5vdGlmeSB0aGUgb3JpZ2luYXRvciBvZiB0aGUgbWVzc2FnZS4gQW55IHZpZXdzIGV4cHJlc3Nl
ZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3NlIG9mIHRoZSBpbmRpdmlkdWFsIHNlbmRlci4NClRo
aXMgbWVzc2FnZSBoYXMgYmVlbiBzY2FubmVkIGZvciB2aXJ1c2VzIGFuZCBTcGFtIGJ5IFpURSBB
bnRpLVNwYW0gc3lzdGVtLg0K
--=_alternative 00072FDF48257712_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIEhpbWFuc2h1LDwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+VGhhbmsgeW91IGZvciB5b3VyIHJl
cGx5LiBQbGVhc2Ugc2VlDQpteSBuZXcgY29tbWVudHMgd2l0aCBpdGFsaWMgZm9ybWF0IGluIGxp
bmUuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5CUjwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+TGl6aG9uZyBKaW48L2Zv
bnQ+DQo8cD48Zm9udCBzaXplPTEgY29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQgTVMiPjxi
cj4NCjwvZm9udD48Zm9udCBzaXplPTEgZmFjZT0iVGFob21hIj48Yj48YnI+DQpGcm9tOjwvYj4g
PC9mb250PjxhIGhyZWY9bGl6aG9uZy5qaW5AenRlLmNvbS5jbj48Zm9udCBzaXplPTEgY29sb3I9
Ymx1ZSBmYWNlPSJUYWhvbWEiPjx1PmxpemhvbmcuamluQHp0ZS5jb20uY248L3U+PC9mb250Pjwv
YT48Zm9udCBzaXplPTEgZmFjZT0iVGFob21hIj4NCls8L2ZvbnQ+PGEgaHJlZj1tYWlsdG86bGl6
aG9uZy5qaW5AenRlLmNvbS5jbj48Zm9udCBzaXplPTEgY29sb3I9Ymx1ZSBmYWNlPSJUYWhvbWEi
Pjx1Pm1haWx0bzpsaXpob25nLmppbkB6dGUuY29tLmNuPC91PjwvZm9udD48L2E+PGZvbnQgc2l6
ZT0xIGZhY2U9IlRhaG9tYSI+XQ0KPGI+PGJyPg0KU2VudDo8L2I+IFNhdHVyZGF5LCBBcHJpbCAx
NywgMjAxMCAxMToxNiBBTTxiPjxicj4NClRvOjwvYj4gSGltYW5zaHUgU2hhaDsgPC9mb250Pjxh
IGhyZWY9a2FydmluZEBlbnRlcmFzeXMuY29tPjxmb250IHNpemU9MSBjb2xvcj1ibHVlIGZhY2U9
IlRhaG9tYSI+PHU+a2FydmluZEBlbnRlcmFzeXMuY29tPC91PjwvZm9udD48L2E+PGZvbnQgc2l6
ZT0xIGZhY2U9IlRhaG9tYSI+Ow0KPC9mb250PjxhIGhyZWY9ZXJvc2VuQGNpc2NvLmNvbT48Zm9u
dCBzaXplPTEgY29sb3I9Ymx1ZSBmYWNlPSJUYWhvbWEiPjx1PmVyb3NlbkBjaXNjby5jb208L3U+
PC9mb250PjwvYT48Zm9udCBzaXplPTEgZmFjZT0iVGFob21hIj47DQo8L2ZvbnQ+PGEgaHJlZj1n
aWxlcy5oZXJvbkBnbWFpbC5jb20+PGZvbnQgc2l6ZT0xIGNvbG9yPWJsdWUgZmFjZT0iVGFob21h
Ij48dT5naWxlcy5oZXJvbkBnbWFpbC5jb208L3U+PC9mb250PjwvYT48Zm9udCBzaXplPTEgZmFj
ZT0iVGFob21hIj47DQo8L2ZvbnQ+PGEgaHJlZj1mbGVmYXVjaEBjaXNjby5jb20+PGZvbnQgc2l6
ZT0xIGNvbG9yPWJsdWUgZmFjZT0iVGFob21hIj48dT5mbGVmYXVjaEBjaXNjby5jb208L3U+PC9m
b250PjwvYT48Zm9udCBzaXplPTEgZmFjZT0iVGFob21hIj48Yj48YnI+DQpDYzo8L2I+IDwvZm9u
dD48YSBocmVmPXNoYW5lQGNhc3RsZXBvaW50Lm5ldD48Zm9udCBzaXplPTEgY29sb3I9Ymx1ZSBm
YWNlPSJUYWhvbWEiPjx1PnNoYW5lQGNhc3RsZXBvaW50Lm5ldDwvdT48L2ZvbnQ+PC9hPjxmb250
IHNpemU9MSBmYWNlPSJUYWhvbWEiPjsNCjwvZm9udD48YSBocmVmPWwydnBuQGlldGYub3JnPjxm
b250IHNpemU9MSBjb2xvcj1ibHVlIGZhY2U9IlRhaG9tYSI+PHU+bDJ2cG5AaWV0Zi5vcmc8L3U+
PC9mb250PjwvYT48Zm9udCBzaXplPTEgZmFjZT0iVGFob21hIj48Yj48YnI+DQpTdWJqZWN0Ojwv
Yj4gUmU6IFdHIExhc3QgQ2FsbDogZHJhZnQtaWV0Zi1sMnZwbi1pcGxzLTA5PC9mb250Pjxmb250
IHNpemU9MT4NCjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48YnI+
DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGZhY2U9IkFyaWFsIj48YnI+DQo8YnI+DQpIaSBIaW1hbnNo
dSBhbmQgYXV0aG9ycyw8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+
IDwvZm9udD48Zm9udCBzaXplPTEgZmFjZT0iQXJpYWwiPjxicj4NCkFmdGVyIHJldmlld2luZyBk
cmFmdC1pZXRmLWwydnBuLWlwbHMtMDksIEkgaGF2ZSB0aGUgZm9sbG93aW5nIGNvbW1lbnRzOjxi
cj4NCjEuIFNlY3Rpb24gMi4wLCBwb2ludCA1LCBidWxsZXQgYywgbW9yZSBwcmVjaXNlbHksIHRo
ZSB1bmljYXN0IEFSUCBwYWNrZXRzDQpyZWNlaXZlZCBmcm9tICZxdW90O211bHRpY2FzdCZxdW90
OyBwc2V1ZG93aXJlIG1heSBkbyBNQUMgREEgbG9va3VwLCBhbmQNCmZvcndhcmQgdG8gd2hlcmUg
Q0UgaXMgbG9jYXRlZC4gU28gdGhlIGNvbnRleHQgc2hvdWxkIGFkZCB0aGlzIGV4Y2VwdGlvbg0K
Zm9yIEFSUCBwYWNrZXRzPC9mb250Pjxmb250IHNpemU9MT4gPC9mb250Pjxmb250IHNpemU9MSBj
b2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+PGJyPg0KW0hpbWFuc2h1Jmd0
O10gSSBhbSBub3Qgc3VyZSBJIGZ1bGx5IHVuZGVyc3RhbmQgeW91ciBjb21tZW50LCBidXQgSSBh
bQ0KZ3Vlc3NpbmcgeW91IGFyZSBhc2tpbmcgdG8gYWRkIHRleHQgdG8gdGhlIGRyYWZ0IHJlZmVy
cmluZyB0aGUgdW5pY2FzdA0KTUFDIGFuZCBBUlAgYXMgdGhlIGNvbnRleHQ8L2k+PC9iPjwvZm9u
dD48Zm9udCBzaXplPTE+IDwvZm9udD48Zm9udCBzaXplPTEgY29sb3I9IzFmNDk3ZCBmYWNlPSJU
cmVidWNoZXQgTVMiPjxiPjxpPjxicj4NCnRvIHRoZSBleGNlcHRpb24gd2hlcmVieSBub3JtYWxs
eSBhbGwgdGhlIHBhY2tldHMgcmVjZWl2ZWQgb3ZlciChsG11bHRpY2FzdKGxDQpQVyBhcmUgYnJv
YWRjYXN0ZWQsIGluY2x1ZGluZyB0aGlzIEFSUCB1bmljYXN0LCBidXQgYXMgYW4gZXhjZXB0aW9u
LCBpbg0KdGhpcyBjYXNlLCBvbmU8L2k+PC9iPjwvZm9udD48Zm9udCBzaXplPTE+IDwvZm9udD48
Zm9udCBzaXplPTEgY29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQgTVMiPjxiPjxpPjxicj4N
CmNhbiBvcHRpbWl6ZSB0aGUgZmxvb2RpbmcuPC9pPjwvYj48L2ZvbnQ+PGZvbnQgc2l6ZT0xPiA8
L2ZvbnQ+PGZvbnQgc2l6ZT0xIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPjxiPjxicj4NCltMaXpo
b25nXSBZZXMsIHRoYXQncyBleGFjdGx5IHdoYXQgSSBtZWFuLjwvYj48L2ZvbnQ+PGZvbnQgc2l6
ZT0xPiA8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgY29sb3I9IzAwODAwMD48YnI+DQombHQ7aGlt
YW5zaHUmZ3Q7IEkgaGF2ZSBmb2xsb3dpbmcgcGFyYWdyYXBoIGZyb20gdGhlIGRyYWZ0LiBJIGhh
dmUgYWRkZWQNCmEgc2VudGVuY2UgKGluIHJlZCkuIFNlZSBpZiBpdCBhZGRyZXNzZXMgeW91ciBj
b21tZW50Ljxicj4NClBlcnNvbmFsbHksIEkgZmVlbCBpdCBpcyByZXBlYXRpbmcgd2hhdCBpcyBh
bHJlYWR5IHN0YXRlZCBpbiB0aGUgZHJhZnQNCmFuZCBkb2VzIG5vdCBuZWVkIG1vcmUgY2xhcmlm
aWNhdGlvbi4gSSBkbyB3YW50IHRvIGNsYXJpZnk8YnI+DQpvbiB5b3VyIGNvbW1lbnQgdGhhdCBm
bG9vZGluZyBvcHRpbWl6YXRpb24gaXMgbm90IGxpbWl0ZWQgdG8gQVJQIHBhY2tldHMNCm9ubHku
IEl0IGlzIHNpbXBseSBiYXNlZCBvbiBNQUMgREEuPGJyPg0KPGJyPg0KICZuYnNwOyChsFdoZW4g
YSB1bmljYXN0IEFSUCBFdGhlcm5ldCBmcmFtZSBpcyByZWNlaXZlZCBvdmVyIHRoZSAnbXVsdGlj
YXN0Jw0KPGJyPg0KICZuYnNwOyBQVywgUEUgbWF5IG9wdGlvbmFsbHkgZG8gTUFDIERBIGxvb2t1
cCBpbiB0aGUgZm9yd2FyZGluZyB0YWJsZQ0KYW5kIDxicj4NCiAmbmJzcDsgZm9yd2FyZCBpdCB0
byB0aGUgQUMgd2hlcmUgdGhlIENFIGlzIGxvY2F0ZWQuIElmIHRoZSBDRSBpcyBub3QNCjxicj4N
CiAmbmJzcDsgYWNjZXNzaWJsZSB0aHJvdWdoIGFueSBsb2NhbCBBQywgdGhlIGZyYW1lIGlzIGRy
b3BwZWQuIENvbnZlcnNlbHksDQo8YnI+DQogJm5ic3A7IHRoZSBQRSBtYXkgc2ltcGx5IGZvcndh
cmQgdGhlIGZyYW1lIHRvIGFsbCB0aGUgQUNzIGFzc29jaWF0ZWQgd2l0aA0KPGJyPg0KICZuYnNw
OyB0aGF0IElQTFMgaW5zdGFuY2Ugd2l0aG91dCBhbnkgbG9va3VwIGluIHRoZSBmb3J3YXJkaW5n
IHRhYmxlLqGxPGJyPg0KICZuYnNwOyAmbmJzcDs8L2ZvbnQ+PGZvbnQgc2l6ZT0xPjxicj4NCiAm
bmJzcDsgPC9mb250Pjxmb250IHNpemU9MSBjb2xvcj1yZWQ+VHlwaWNhbGx5LCBmcmFtZXMgcmVj
ZWl2ZWQgb3ZlciB0aGUNCqGubXVsdGljYXN0oa8gUFcgYXJlIGZsb29kZWQgdG8gPGJyPg0KICZu
YnNwOyAmbmJzcDtsb2NhbCBBQ3MgdGhhdCBhcmUgbWVtYmVyIG9mIHRoZSBJUExTIGluc3RhbmNl
LiBIb3dldmVyLA0KYXMgYW4gb3B0aW1pemF0aW9uLDxicj4NCiAmbmJzcDsgJm5ic3A7UEUgbWF5
IGxvb2t1cCBNQUMgREEgdG8gbGltaXQgdGhlIGZsb29kaW5nIGJhc2VkIG9uIGxvY2FsDQpkYXRh
YmFzZS4gVGhpczxicj4NCiAmbmJzcDsgJm5ic3A7aW5jbHVkZXMgdW5pY2FzdCBNQUMgYXMgd2Vs
bCBhcyBtdWx0aWNhc3QgTUFDIGZyYW1lcy48L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgY29sb3I9
Ymx1ZT48aT5bTGl6aG9uZ10gTm93IGl0IGlzIGZpbmUgZm9yIG1lLjwvaT48L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0xIGZhY2U9IkFyaWFsIj48YnI+DQouPC9mb250Pjxmb250IHNpemU9MiBmYWNl
PSJUaW1lcyBOZXcgUm9tYW4iPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGZhY2U9IkFyaWFsIj48YnI+
DQoyLiBTZWN0aW9uIDcuMSwgSSBhbSB3b25kZXJpbmcgaG93IHRvIHNldHVwIHRoZSB1bmlkaXJl
Y3Rpb25hbCBtcDJwIHBzZXVkb3dpcmUuDQpBY2NvcmRpbmcgdG8gUkZDNDQ0Nywgb25lIHBzZXVk
b3dpcmUgd2lsbCBiZSBVUCBvbmx5IHdoZW4gYm90aCBsb2NhbCBhbmQNCnJlbW90ZSBsYWJlbCBt
YXBwaW5nIG1lc3NhZ2UgaXMgc2VudCBhbmQgcmVjZWl2ZWQuIEJ1dCBhY2NvcmRpbmcgdG8gdGhl
DQpkZXNjcmlwaXRpb24gb2YgdW5pZGlyZWN0aW9uYWwgbXAycCBwc2V1ZG93aXJlIGluIElQTFMs
IGlmIFBFeCBzZW5kcyBhDQpsYWJlbCBtYXBwaW5nIHRvIFBFeSBmb3IgQ0V4LCBQRXkgc2VlbXMg
dG8gY29uc2lkZXIgdGhlIFBXIGFzIFVQIHdoZW4gcmVjZWl2aW5nDQp0aGUgY29ycmVzcG9uZGlu
ZyBsYWJlbCBtYXBwaW5nLCBhbmQgUEV4IHdvdWxkIGNvbnNpZGVyIHRoZSBQVyBhcyBVUCB3aGVu
DQpzZW5kaW5nIG91dCB0aGUgbGFiZWwgbWFwcGluZywgd2l0aG91dCB0aGUgbmVjZXNzYXJpdHkg
b2YgYWxsb2NhdGluZyBsb2NhbA0KbGFiZWxzIGZvciB0aGUgUFcuPC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGNvbG9yPSMxZjQ5
N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT48YnI+DQpbSGltYW5zaHUmZ3Q7XSBUaGVyZSBp
cyBubyBvbmUtdG8tb25lIGNvcnJlc3BvbmRlbmNlIHdpdGggcmVzcGVjdCB0byBQVw0KZGlyZWN0
aW9uYWxpdHkuIE1lYW5pbmcsIGlmIFBFMSBoYXMgdHdvIGxvY2FsIENFLCBpdCB3aWxsIGFkdmVy
dGlzZSB0d28NCmxhYmVscy4gSWYgUEUyIGhhcyA0IGxvY2FsIENFcyBpdCB3aWxsIGFkdmVydGlz
ZSA0IGxhYmVscy4gPGJyPg0KV2hpY2ggZG9lcyBub3QgbWVhbiB0aGF0IHdoZW4gUEUxIHJlY2Vp
dmVzIDQgbGFiZWxzIGZyb20gUEUyIHRoYXQgaXQgbmVlZHMNCnRvIGFkdmVydGlzZSA0IGxhYmVs
cyB0byBicmluZyBQVyChrlVQoa8uIFNvIHRoZSBxdWVzdGlvbiwgaXMgoa51bmlkaXJlY3Rpb25h
bKGvDQpQVyBhIGRldmlhdGlvbiBmcm9tIFJGQyA0NDQ3IHdoaWNoIDxicj4NCmFzc3VtZXMgUFcg
dG8gYmUgYmktZGlyZWN0aW9uYWwgKHRoaXMgdXNlZCB0byBiZSB0cnVlIGluaXRpYWxseSwgbm90
IHN1cmUNCmlmIHN0aWxsIGlzIHRydWUpIGJ5IHdheSBvZiB1bml0aW5nIHRvIG9wcG9zaXRlIGRp
cmVjdGlvbiB1bmlkaXJlY3Rpb25hbA0KUFcuIFRoZSB1bmlkaXJlY3Rpb25hbCBQVyBpcyBub3Qg
aWxsZWdhbC48L2k+PC9iPjwvZm9udD48Zm9udCBzaXplPTE+IDwvZm9udD48Zm9udCBzaXplPTEg
Y29sb3I9Ymx1ZSBmYWNlPSJBcmlhbCI+PGI+PGJyPg0KW0xpemhvbmddIEZyb20gbXkgdW5kZXJz
dGFuZGluZywgdW5pZGlyZWN0aW9uYWwgcG9pbnQtdG8tcG9pbnQgUFcgaXMgbm90DQpkZWZpbmVk
IGluIFJGQzQ0NDcuIFNlZSBzZWN0aW9uIDUuMy4zIHNpZ25hbGluZyBwcm9jZWR1cmVzIGluIFJG
QzQ0NDcuPC9iPjwvZm9udD48Zm9udCBzaXplPTE+DQo8YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0x
IGNvbG9yPSMwMDgwMDA+PGJyPg0KJmx0O2hpbWFuc2h1Jmd0OyBSRkM0NDQ3IGlzIGEgYmFzZSBk
b2N1bWVudCBhbmQgZG9lcyBub3QgcHJldmVudCBvdGhlcg0KZHJhZnRzIHRvIHV0aWxpemUgYW5k
L29yIGV4dGVuZCBmb3Igc3BlY2lmaWMgYXBwbGljYXRpb24gKGFzIGRlZmluZWQgaW4NCkwyVlBO
KS48YnI+DQpGcmFua2x5LCBJIHdvdWxkIGNvbnNpZGVyIHVuaWNhc3QgUFcgYXMgYSBzdWJzZXQg
b2YgdGhlIFJGQzQ0NDcgZGVmaW5lZA0KbWV0aG9kb2xvZ2llcy48L2ZvbnQ+PGZvbnQgc2l6ZT0x
IGZhY2U9IkFyaWFsIj48YnI+DQo8YnI+DQpXaGF0J3MgbW9yZSwgaXQgaXMgYWxzbyBkaWZmaWN1
bHQgdG8gY29uZmlndXJlIHRoZSBQV2lkLiBJZiBQRXggdXNlcyBQV2lkXzENCmZvciBDRXgxLCBh
bmQgUFdpZF8yIGZvciBDRXgyLCBhY2NvcmRpbmcgdG8gc2VjdGlvbiA3LjEsIHRoZSBQRXkgbmVl
ZHMNCnRvIGNvbmZpZ3VyZSBib3RoIFBXaWRfMSBhbmQgUFdpZF8yLCB3aGljaCBpcyBhY3R1YWxs
eSBub3QgbmVjZXNzYXJ5LiBEbw0KSSBtaXNzIHNvbWV0aGluZyBpbXBvcnRhbnQgaGVyZSB0byB1
bmRlcnN0YW5kIHRoZSBjb25jZXB0IG9mIHVuaWRpcmVjdGlvbmFsDQptcDJwIHBzZXVkb3dpcmU/
IFRoZXJlIG1heSBiZSBhIG5ldyB0eXBlIG9mIEZFQyB0aGF0IGlzIHJlcXVpcmVkLCBzaW1pbGFy
DQp3aXRoIHVuaWRpcmVjdGlvbmFsIFAyTVAgUFcuPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJU
aW1lcyBOZXcgUm9tYW4iPg0KPC9mb250Pjxmb250IHNpemU9MSBjb2xvcj0jMWY0OTdkIGZhY2U9
IlRyZWJ1Y2hldCBNUyI+PGI+PGk+PGJyPg0KW0hpbWFuc2h1Jmd0O10gUFdpZCBpcyBwZXIgSVBM
UyBpbnN0YW5jZSBhbmQgbm90IHBlciBDRS4gSSBkbyBub3Qgc2VlIGFueQ0KdGV4dCBpbiA3LjEg
d2hpY2ggdGFsa3MgYWJvdXQgY29uZmlndXJpbmcgZGlmZmVyZW5jZSBQV2lkIGZvciBlYWNoIENF
LjwvaT48L2I+PC9mb250Pjxmb250IHNpemU9MT4NCjwvZm9udD48Zm9udCBzaXplPTEgY29sb3I9
IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQgTVMiPjxiPjxpPjxicj4NCkZvciBhIGdpdmVuIElQTFMg
aW5zdGFuY2UgYSBQRSBoYXMgZm9sbG93aW5nIHRvIHNpZ25hbCCoQzwvaT48L2I+PC9mb250Pjxm
b250IHNpemU9MT4NCjwvZm9udD48Zm9udCBzaXplPTEgY29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVi
dWNoZXQgTVMiPjxiPjxpPjxicj4NCmEpICZuYnNwOyAmbmJzcDtQVyBpZDwvaT48L2I+PC9mb250
Pjxmb250IHNpemU9MT4gPC9mb250Pjxmb250IHNpemU9MSBjb2xvcj0jMWY0OTdkIGZhY2U9IlRy
ZWJ1Y2hldCBNUyI+PGI+PGk+PGJyPg0KYikgJm5ic3A7ICZuYnNwO09uZSBNUDJQIKGubXVsdGlj
YXN0oa8gJm5ic3A7RXRoZXJuZXQgUFc8L2k+PC9iPjwvZm9udD48Zm9udCBzaXplPTE+DQo8L2Zv
bnQ+PGZvbnQgc2l6ZT0xIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT48
YnI+DQpjKSAmbmJzcDsgJm5ic3A7TWFueSAoaS5lLiBvbmUgcGVyIGxvY2FsIENFKSBNUDJQIKGu
dW5pY2FzdKGvIElQIFBXIGFsb25nDQp3aXRoIENFoa9zIE1BQyBhZGRyZXNzPC9pPjwvYj48L2Zv
bnQ+PGZvbnQgc2l6ZT0xPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGNvbG9yPSMxZjQ5N2QgZmFjZT0i
VGltZXMgTmV3IFJvbWFuIj48Yj48aT48YnI+DQpbSGltYW5zaHUmZ3Q7XSA8L2k+PC9iPjwvZm9u
dD48Zm9udCBzaXplPTEgY29sb3I9IzFmNDk3ZCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPlNlY3Rp
b24NCjcuMSBkZXNjcmliZXMgZGV0YWlscyBmb3Igc2VuZCBhbmQgcmVjZWl2ZSBwcm9jZXNzaW5n
IG9mIGxhYmVsIG1hcHBpbmcNCm1lc3NhZ2U8L2ZvbnQ+PGZvbnQgc2l6ZT0xPiA8L2ZvbnQ+PGZv
bnQgc2l6ZT0xIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPjxiPjxicj4NCltMaXpob25nXSBEbyB5
b3UgbWVhbiBQRSB3aWxsIGFkdmVydGlzZSBhbGwgbGFiZWxzIGZvciBDRXMgd2l0aCBzYW1lIFBX
aWQ/DQpUaGVuIHRoYXQgbWVhbnMgUEUgd2lsbCBhZHZlcnRpc2UgZGlmZmVyZW50IGxhYmVscyBm
b3Igc2FtZSBGRUMoc2FtZSBQV2lkKSwNCndoaWNoIHdpbGwgbm90IG9wZXJhdGUgY29ycmVjdGx5
IHVuZGVyIGN1cnJlbnQgZnJhbWV3b3JrLiBUaGUgcGVlciBQRSByZWNlaXZpbmcNCnNldmVyYWwg
bGFiZWwgbWFwcGluZyBtZXNzYWdlcyB3aXRoIHNhbWUgRkVDIGJ1dCBkaWZmZXJlbnQgbGFiZWxz
IHdpbGwNCnVwZGF0ZSB0aGUgYWxyZWFkeSByZWNlaXZlZCBsYWJlbCwgYW5kIG9ubHkgcmV0YWlu
IHRoZSBuZXdlc3Qgb25lLiBUaGUNCndheSB0byBzb2x2ZSB0aGlzIGlzIHRvIGRlZmluZSBhIG5l
dyB0eXBlIG9mIEZFQyB0byBzcGVjaWZ5IGRpZmZlcmVudCBvcGVyYXRpb24NCmNvbXBhcmluZyB3
aXRoIG5vcm1hbCBGRUMgKGUuZywgdHlwZSAxMjggYW5kIDEyOSkuPC9iPjwvZm9udD48Zm9udCBz
aXplPTE+DQo8YnI+DQo8YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGNvbG9yPSMwMDgwMDA+PGJy
Pg0KJmx0O2hpbWFuc2h1Jmd0OyBOb3QgdHJ1ZS4gVGhlIGRyYWZ0IGNsZWFybHkgc3RhdGVzIHRo
YXQgKENFoa9zKSBNQUMgYWRkcmVzcw0KbXVzdCBiZSBhZHZlcnRpc2VkIGluIHRoZSBMTSBtZXNz
YWdlLiBUaGUgTUFDIGFkZHJlc3MgaXMgYXVnbWVudGVkIGFuZA0KaXMgdHJlYXRlZCBhczxicj4N
CnBhcnQgb2YgUFctRkVDLiBNYXkgYmUgYSBzZW50ZW5jZSBuZWVkcyB0byBiZSBhZGRlZCB0byBh
dm9pZCB0aGUgY29uZnVzaW9uLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgY29sb3I9Ymx1ZT48
aT5bTGl6aG9uZ108L2k+PC9mb250Pjxmb250IHNpemU9MSBjb2xvcj1ibHVlIGZhY2U9IkFyaWFs
Ij48aT4NCk5vdyBJIGdldCB5b3VyIG1lYW5pbmcuIFRoZW4gdGhlIG1ldGhvZCBkZXNjcmliZWQg
aW4gZHJhZnQgaXMgaW1wbGVtZW50YWJsZSwNCmJ1dCB0aGUgRkVDIGRlZmluaXRpb24gaXMgbm90
IGdvb2QgaWYgTUFDIGFkZHJlc3MgaXMgYXVnbWVudGVkIHRvIFBXLUZFQy4NCkkgY2FuIHN1bW1h
cmlzZSBsaWtlIHRoYXQgd2hlbiBQRSBhZHZlcnRpc2Ugb25lIEZFQyAoZS5nLCB0eXBlIDEyOCBv
ciAxMjkpDQp3aXRoIE1BQyBhZGRyZXNzIGFuZCBJUCBQVyB0eXBlLCB0aGVuIFBFIHNob3VsZCB0
cmVhdCBpdCBhcyBhbiB1bmlkaXJlY3Rpb25hbA0KUFcgYW5kIGFsbG9jYXRlIGEgbGFiZWwgZm9y
IGNvbWJpbmF0aW9uIG9mIEZFQyBhbmQgTUFDIGFkZHJlc3MuIFRoZSBjb25jZXB0DQppcyBhIGJp
dCBkaWZmZXJlbnQgd2l0aCB0aGUgdHJhZGl0aW9uYWwgb25lIChSRkM1MDM2KSB3aGVyZSBQRSB3
aWxsIG9ubHkNCmFsbG9jYXRlIGxhYmVsIGZvciBGRUMgd2l0aG91dCBjb25zaWRlcmluZyBhbnkg
b3RoZXIgdmFsdWUuIEEgY2xhcmlmaWVkDQpzZW50YW5jZSBtYXkgbm90IHN1ZmZpY2llbnQgaGVy
ZS4uLjwvaT48L2ZvbnQ+PGZvbnQgc2l6ZT0xIGZhY2U9IkFyaWFsIj48aT4uLjwvaT48L2ZvbnQ+
PGZvbnQgc2l6ZT0xIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPjxpPi5hDQpuZXcgdHlwZSBvZiBG
RUMgd291bGQgYmUgYmVzdCBmcm9tIG15IHVuZGVyc3RhbmRpbmcuPC9pPjwvZm9udD48Zm9udCBz
aXplPTEgZmFjZT0iQXJpYWwiPjxicj4NCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgZmFjZT0i
QXJpYWwiPjxicj4NCjMuIFNlY3Rpb24gNy4yLCB3aHkgbm90IHVzaW5nIExEUCBjYXBhYmlsaXR5
IHRvIGFkdmVydGlzaW5nIElQdjYgc3RhY2sNCmNhcGFiaWxpdHk/PC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGNvbG9yPSMxZjQ5
N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT48YnI+DQpbSGltYW5zaHUmZ3Q7XSBCZWNhdXNl
IHRoaXMgaXMgc3BlY2lmaWMgdG8gUFcgYW5kIElQTFMgaW5zdGFuY2U8L2k+PC9iPjwvZm9udD48
Zm9udCBzaXplPTE+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwi
PjxiPjxicj4NCltMaXpob25nXSBhY3R1YWxseSwgY3VycmVudCBQMk1QIFBXIGNhcGFiaWxpdHkg
bmVnb3RpYXRpb24gdXNlcyBMRFAgY2FwYWJpbGl0eS4NCkkgaG9wZSB3ZSBjYW4gYWxpZ24gdGhp
cywgYmVjYXVzZSBib3RoIGFyZSByZWxhdGVkIHdpdGggUFcgY2FwYWJpbGl0eS48L2I+PC9mb250
Pjxmb250IHNpemU9MT4NCjxicj4NCjwvZm9udD48Zm9udCBzaXplPTEgY29sb3I9IzAwODAwMD48
YnI+DQombHQ7aGltYW5zaHUmZ3Q7IFdlIChhdXRob3JzKSB3aWxsIGxvb2sgaW50byB0aGlzLjwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTEgY29sb3I9Ymx1ZT48aT5bTGl6aG9uZ108L2k+PC9mb250
Pjxmb250IHNpemU9MSBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj48aT4NClRoYXQncyBnb29kLjwv
aT48L2ZvbnQ+PGZvbnQgc2l6ZT0xIGZhY2U9IkFyaWFsIj48YnI+DQo8L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0xIGZhY2U9IkFyaWFsIj48YnI+DQo0LiBXaWxsIElQTFMgY29uc2lkZXIgYW55IHNw
b2tlIGNvbm5lY3Rpdml0eSB0byBpbmNyZWFzZSB0aGUgc2NhbGFiaWxpdHksDQpzYW1lIGFzIFZQ
TFM/PC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiA8L2ZvbnQ+PGZv
bnQgc2l6ZT0xIGNvbG9yPSMxZjQ5N2QgZmFjZT0iVHJlYnVjaGV0IE1TIj48Yj48aT48YnI+DQpb
SGltYW5zaHUmZ3Q7XSBJIGFtIG5vdCBzdXJlIEkgZnVsbHkgdW5kZXJzdGFuZC4gSVBMUyBhc3N1
bWVzIChyZWNvbW1lbmRzKQ0KdGhhdCBDRXMgYXJlIElQIHJvdXRlcnMgdGhhdCBhY3QgYXMgZWRn
ZSBib3guPC9pPjwvYj48L2ZvbnQ+PGZvbnQgc2l6ZT0xPg0KPC9mb250Pjxmb250IHNpemU9MSBj
b2xvcj0jMWY0OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+PGJyPg0KTWVhbmluZyBtb3N0
IG9mIHRoZSBjdXN0b21lcqGvcyBJUCBob3N0cyBhbmQgJm5ic3A7b3RoZXIgcm91dGVycyBhcmUg
YmVoaW5kDQp0aGlzIENFIHJvdXRlciBpbiBjdXN0b21lciBuZXR3b3JrIGFuZCBQRSBkb2VzPC9p
PjwvYj48L2ZvbnQ+PGZvbnQgc2l6ZT0xPg0KPC9mb250Pjxmb250IHNpemU9MSBjb2xvcj0jMWY0
OTdkIGZhY2U9IlRyZWJ1Y2hldCBNUyI+PGI+PGk+PGJyPg0Kbm90IHNlZSB0aGVtLiBUaGlzIGJ5
IGl0c2VsZiBwcm92aWRlcyBnb29kIGhpZXJhcmNoeSAmYW1wOyBzY2FsYWJpbGl0eS4NCjwvaT48
L2I+PC9mb250Pjxmb250IHNpemU9MSBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj48Yj48YnI+DQpb
TGl6aG9uZ10gU29ycnkgZm9yIHRoZSB1bmNsZWFyIHN0YXRlbWVudC4gVGhlIHNjYWxhYmlsaXR5
IEkgcmVmZXIgaXMgUFcNCnNjYWxhYmxpdHkgdG8gY29uc3RydWN0IGxhcmdlIElQTFMgbmV0d29y
aywgd2hpY2ggaXMgaW5jbHVkZWQgaW4gUkZDNDc2Mg0Kc2VjdGlvbiAxMC4xLjEuPC9iPjwvZm9u
dD48Zm9udCBzaXplPTEgY29sb3I9IzFmNDk3ZCBmYWNlPSJUcmVidWNoZXQgTVMiPjxiPjxpPg0K
PC9pPjwvYj48L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGJyPg0K
PC9mb250Pjxmb250IHNpemU9MSBjb2xvcj0jMDA4MDAwPjxicj4NCiZsdDtoaW1hbnNodSZndDsg
TXkgZmVlbGluZyBpcyB0aGF0IGN1cnJlbnQgZHJhZnQgaXMgYWRlcXVhdGUgZm9yIHRoZSBzY2Fs
YWJpbGl0eQ0KdGhhdCBpcyBlbnZpc2lvbmVkIGZvciBpdHMgYXBwbGljYWJpbGl0eSBpbiB0aGUg
ZXhpc3RpbmcgbmV0d29ya3MuPGJyPg0KSG93ZXZlciwgaWYgZmllbGQgZXhwZXJpZW5jZSBzdWdn
ZXN0IHRoYXQgc2NhbGFiaWxpdHkgaXMgYW4gaXNzdWUsIHdnIGNhbg0KdW5kZXJ0YWtlIGEgc2Vw
YXJhdGUgd29yayBpdGVtIHRvIGV4dGVuZCB0aGUgYXJjaGl0ZWN0dXJlIHRvIGFkZHJlc3M8YnI+
DQpzY2FsYWJpbGl0eS4gJm5ic3A7IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgY29sb3I9Ymx1
ZT48aT5bTGl6aG9uZ108L2k+PC9mb250Pjxmb250IHNpemU9MSBjb2xvcj1ibHVlIGZhY2U9IkFy
aWFsIj48aT4NClRoYXQncyBPSy48L2k+PC9mb250Pjxmb250IHNpemU9MSBmYWNlPSJBcmlhbCI+
PGJyPg0KPGJyPg0KSG9wZSB0byBzZWUgeW91ciByZXBseSwgdGhhbmsgeW91LjwvZm9udD48Zm9u
dCBzaXplPTIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4NCjwvZm9udD48Zm9udCBzaXplPTEgZmFj
ZT0iQXJpYWwiPjxicj4NCjxicj4NCkJlc3QgUmVnYXJkczwvZm9udD48Zm9udCBzaXplPTIgZmFj
ZT0iVGltZXMgTmV3IFJvbWFuIj4gPC9mb250Pjxmb250IHNpemU9MSBmYWNlPSJBcmlhbCI+PGJy
Pg0KTGl6aG9uZyBKaW48L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+
IDxicj4NCjwvZm9udD48Zm9udCBzaXplPTEgZmFjZT0iQ291cmllciBOZXciPjxicj4NCjxicj4N
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCjxicj4NCkRhdGU6IE1vbiwgNSBB
cHIgMjAxMCAxOTo1ODowMSAtMDYwMDxicj4NCkZyb206IFNoYW5lIEFtYW50ZSAmbHQ7PC9mb250
PjxhIGhyZWY9c2hhbmVAY2FzdGxlcG9pbnQubmV0Pjxmb250IHNpemU9MSBjb2xvcj1ibHVlIGZh
Y2U9IkNvdXJpZXIgTmV3Ij48dT5zaGFuZUBjYXN0bGVwb2ludC5uZXQ8L3U+PC9mb250PjwvYT48
Zm9udCBzaXplPTEgZmFjZT0iQ291cmllciBOZXciPiZndDs8YnI+DQpTdWJqZWN0OiBXRyBMYXN0
IENhbGw6IGRyYWZ0LWlldGYtbDJ2cG4taXBscy0wOTxicj4NClRvOiA8L2ZvbnQ+PGEgaHJlZj1s
MnZwbkBpZXRmLm9yZz48Zm9udCBzaXplPTEgY29sb3I9Ymx1ZSBmYWNlPSJDb3VyaWVyIE5ldyI+
PHU+bDJ2cG5AaWV0Zi5vcmc8L3U+PC9mb250PjwvYT48Zm9udCBzaXplPTEgZmFjZT0iQ291cmll
ciBOZXciPjxicj4NCk1lc3NhZ2UtSUQ6ICZsdDs8L2ZvbnQ+PGEgaHJlZj0iN0I2QzUwNDAtQzEw
My00NjI2LTgzRjgtNjE4MzMxRjY4QkNFQGNhc3RsZXBvaW50Lm5ldCI+PGZvbnQgc2l6ZT0xIGNv
bG9yPWJsdWUgZmFjZT0iQ291cmllciBOZXciPjx1PjdCNkM1MDQwLUMxMDMtNDYyNi04M0Y4LTYx
ODMzMUY2OEJDRUBjYXN0bGVwb2ludC5uZXQ8L3U+PC9mb250PjwvYT48Zm9udCBzaXplPTEgZmFj
ZT0iQ291cmllciBOZXciPiZndDs8YnI+DQpDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJz
ZXQ9dXMtYXNjaWk8YnI+DQo8YnI+DQpIaSBFdmVyeW9uZSw8YnI+DQo8YnI+DQpUaGlzIGlzIHRv
IGJlZ2luIGEgKGZpbmFsKSBXRyBMYXN0IENhbGwgb246PC9mb250Pjxmb250IHNpemU9MSBjb2xv
cj1ibHVlIGZhY2U9IkNvdXJpZXIgTmV3Ij48dT48YnI+DQo8L3U+PC9mb250PjxhIGhyZWY9Imh0
dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbDJ2cG4taXBscy0wOSI+PGZvbnQg
c2l6ZT0xIGNvbG9yPWJsdWUgZmFjZT0iQ291cmllciBOZXciPjx1Pmh0dHA6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWlldGYtbDJ2cG4taXBscy0wOTwvdT48L2ZvbnQ+PC9hPjxmb250IHNp
emU9MSBmYWNlPSJDb3VyaWVyIE5ldyI+PGJyPg0KPGJyPg0KSWYgeW91IGhhdmUgc3Vic3RhbnRp
YWwgdGVjaG5pY2FsIGNvbW1lbnRzIG9yIGNvbmNlcm5zLCBwbGVhc2Ugc2hhcmUgdGhlbQ0Kd2l0
aCB0aGUgbGlzdC4gJm5ic3A7SWYgeW91IGhhdmUgZWRpdG9yaWFsIGNvbW1lbnRzLCBwbGVhc2Ug
c2hhcmUgdGhlbQ0KZGlyZWN0bHkgd2l0aCB0aGUgYXV0aG9ycyBhbmQgY28tY2hhaXJzLjxicj4N
Cjxicj4NClNvIGZhciwgd2UgaGF2ZSB0aGUgZm9sbG93aW5nIGZvbGtzIHNpZ25lZCB1cCBmb3Ig
YSB0aG9yb3VnaCByZXZpZXcgYW5kDQpjb21tZW50czo8YnI+DQotIEFuZHkgTWFsaXM8YnI+DQot
IE5pY2sgRGVsUmVnbm88YnI+DQotIFByYW5qYWwgRHV0dGE8YnI+DQpIb3dldmVyLCB3ZSBjb3Vs
ZCB1c2UgbW9yZSBwZW9wbGUgdG8gY29uZHVjdCBhIHJldmlldy4gJm5ic3A7SWYgeW91IGhhdmUN
CnRoZSB0aW1lIGFuZC9vciBpbmNsaW5hdGlvbiwgcGxlYXNlIGxldCB0aGUgY2hhaXJzIGtub3cg
aWYgeW91J2xsIGJlIGNvbmR1Y3RpbmcNCmEgcmV2aWV3Ljxicj4NCjxicj4NClRoZSBMYXN0IENh
bGwgb24gdGhpcyBkcmFmdCB3aWxsIGFsc28gZW5kIG9uIEFwcmlsIDIzLjxicj4NCjxicj4NClRo
YW5rcyw8YnI+DQo8YnI+DQpHaWxlcyAmYW1wOyBTaGFuZTwvZm9udD48Zm9udCBzaXplPTE+IDwv
Zm9udD48Zm9udCBzaXplPTEgZmFjZT0iQ291cmllciBOZXciPjxicj4NCjxicj4NCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9mb250Pjxm
b250IHNpemU9MT4NCjwvZm9udD48Zm9udCBzaXplPTEgZmFjZT0iQ291cmllciBOZXciPjxicj4N
ClpURSBJbmZvcm1hdGlvbiBTZWN1cml0eSBOb3RpY2U6IFRoZSBpbmZvcm1hdGlvbiBjb250YWlu
ZWQgaW4gdGhpcyBtYWlsDQppcyBzb2xlbHkgcHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2Fu
aXphdGlvbi4gVGhpcyBtYWlsIGNvbW11bmljYXRpb24NCmlzIGNvbmZpZGVudGlhbC4gUmVjaXBp
ZW50cyBuYW1lZCBhYm92ZSBhcmUgb2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kNCmFuZCBh
cmUgbm90IHBlcm1pdHRlZCB0byBkaXNjbG9zZSB0aGUgY29udGVudHMgb2YgdGhpcyBjb21tdW5p
Y2F0aW9uIHRvDQpvdGhlcnMuPC9mb250Pjxmb250IHNpemU9MT4gPC9mb250Pjxmb250IHNpemU9
MSBmYWNlPSJDb3VyaWVyIE5ldyI+PGJyPg0KVGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5z
bWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlhbCBhbmQgaW50ZW5kZWQNCnNvbGVseSBmb3Ig
dGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hvbSB0aGV5IGFyZSBhZGRy
ZXNzZWQuDQpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yIHBsZWFzZSBu
b3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YNCnRoZSBtZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2Vk
IGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2YgdGhlIGluZGl2aWR1YWwNCnNlbmRlci48L2Zv
bnQ+PGZvbnQgc2l6ZT0xPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0xIGZhY2U9IkNvdXJpZXIgTmV3Ij48
YnI+DQpUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBhbmQgU3BhbSBi
eSBaVEUgQW50aS1TcGFtIHN5c3RlbS48L2ZvbnQ+PGZvbnQgc2l6ZT0xPg0KPGJyPg0KPGJyPg0K
PGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS08YnI+DQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkgTm90aWNlOiBUaGUgaW5mb3JtYXRp
b24gY29udGFpbmVkIGluIHRoaXMgbWFpbA0KaXMgc29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5k
ZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uDQppcyBjb25maWRlbnRp
YWwuIFJlY2lwaWVudHMgbmFtZWQgYWJvdmUgYXJlIG9ibGlnYXRlZCB0byBtYWludGFpbiBzZWNy
ZWN5DQphbmQgYXJlIG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2UgdGhlIGNvbnRlbnRzIG9mIHRo
aXMgY29tbXVuaWNhdGlvbiB0bw0Kb3RoZXJzLjxicj4NClRoaXMgZW1haWwgYW5kIGFueSBmaWxl
cyB0cmFuc21pdHRlZCB3aXRoIGl0IGFyZSBjb25maWRlbnRpYWwgYW5kIGludGVuZGVkDQpzb2xl
bHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdob20gdGhleSBh
cmUgYWRkcmVzc2VkLg0KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciBw
bGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mDQp0aGUgbWVzc2FnZS4gQW55IHZpZXdzIGV4
cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3NlIG9mIHRoZSBpbmRpdmlkdWFsDQpzZW5k
ZXIuPGJyPg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNw
YW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uPGJyPg0KPC9mb250Pg0KPGJyPg0KPGJyPjxwcmU+
DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24mbmJzcDtTZWN1cml0eSZuYnNwO05vdGljZTombmJzcDtU
aGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNw
O21haWwmbmJzcDtpcyZuYnNwO3NvbGVseSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2YmbmJzcDt0aGUm
bmJzcDtzZW5kZXIncyZuYnNwO29yZ2FuaXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7bWFpbCZuYnNw
O2NvbW11bmljYXRpb24mbmJzcDtpcyZuYnNwO2NvbmZpZGVudGlhbC4mbmJzcDtSZWNpcGllbnRz
Jm5ic3A7bmFtZWQmbmJzcDthYm92ZSZuYnNwO2FyZSZuYnNwO29ibGlnYXRlZCZuYnNwO3RvJm5i
c3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7bm90Jm5ic3A7
cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtkaXNjbG9zZSZuYnNwO3RoZSZuYnNwO2NvbnRlbnRzJm5i
c3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7b3RoZXJzLg0K
VGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJzcDt0cmFuc21p
dHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZuYnNwO2FyZSZuYnNwO2NvbmZpZGVudGlhbCZuYnNwO2Fu
ZCZuYnNwO2ludGVuZGVkJm5ic3A7c29sZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7dXNlJm5i
c3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRpdHkmbmJzcDt0
byZuYnNwO3dob20mbmJzcDt0aGV5Jm5ic3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZuYnNwO0lmJm5i
c3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3JlY2VpdmVkJm5ic3A7dGhpcyZuYnNwO2VtYWlsJm5ic3A7
aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFzZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZuYnNwO29yaWdp
bmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZuYnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5ic3A7dmlld3Mm
bmJzcDtleHByZXNzZWQmbmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttZXNzYWdlJm5ic3A7YXJlJm5i
c3A7dGhvc2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtzZW5kZXIuDQpU
aGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hhcyZuYnNwO2JlZW4mbmJzcDtzY2FubmVkJm5ic3A7Zm9y
Jm5ic3A7dmlydXNlcyZuYnNwO2FuZCZuYnNwO1NwYW0mbmJzcDtieSZuYnNwO1pURSZuYnNwO0Fu
dGktU3BhbSZuYnNwO3N5c3RlbS4NCjwvcHJlPg==
--=_alternative 00072FDF48257712_=--


From hshah@force10networks.com  Mon Apr 26 18:39:35 2010
Return-Path: <hshah@force10networks.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 33FF528C111 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 18:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.898
X-Spam-Level: 
X-Spam-Status: No, score=-4.898 tagged_above=-999 required=5 tests=[AWL=1.100,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, 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 FEiihbCUmDfW for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 18:39:29 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id 7E58F3A6765 for <l2vpn@ietf.org>; Mon, 26 Apr 2010 18:39:29 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Mon, 26 Apr 2010 18:39:17 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn>
Date: Mon, 26 Apr 2010 18:39:14 -0700
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: Acrlp6MLTzDIWJ66Ruu+61+tVdztLAAAs4pU
Message-ID: <C7FBB882.383B%hshah@force10networks.com>
In-Reply-To: <OF623D5ADF.B723124B-ON48257712.0004D2F2-48257712.00072FE2@zte.com.cn>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7FBB882383Bhshahforce10networkscom_"
MIME-Version: 1.0
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "flefauch@cisco.com" <flefauch@cisco.com>, "lmartini@cisco.com" <lmartini@cisco.com>, "giles.heron@gmail.com" <giles.heron@gmail.com>, "shane@castlepoint.net" <shane@castlepoint.net>, "erosen@cisco.com" <erosen@cisco.com>, Krishnamoorthy Arvind <karvind@enterasys.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: Tue, 27 Apr 2010 01:39:35 -0000

--_000_C7FBB882383Bhshahforce10networkscom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks Lizhong for your further comments. Cut & Paste below that is releven=
t..

What's more, it is also difficult to configure the PWid. If PEx uses PWid_1=
 for CEx1, and PWid_2 for CEx2, according to section 7.1, the PEy needs to =
configure both PWid_1 and PWid_2, which is actually not necessary. Do I mis=
s something important here to understand the concept of unidirectional mp2p=
 pseudowire? There may be a new type of FEC that is required, similar with =
unidirectional P2MP PW.
[Himanshu>] PWid is per IPLS instance and not per CE. I do not see any text=
 in 7.1 which talks about configuring difference PWid for each CE.
For a given IPLS instance a PE has following to signal -
a)    PW id
b)    One MP2P 'multicast'  Ethernet PW
c)    Many (i.e. one per local CE) MP2P 'unicast' IP PW along with CE's MAC=
 address
[Himanshu>] Section 7.1 describes details for send and receive processing o=
f label mapping message
[Lizhong] Do you mean PE will advertise all labels for CEs with same PWid? =
Then that means PE will advertise different labels for same FEC(same PWid),=
 which will not operate correctly under current framework. The peer PE rece=
iving several label mapping messages with same FEC but different labels wil=
l update the already received label, and only retain the newest one. The wa=
y to solve this is to define a new type of FEC to specify different operati=
on comparing with normal FEC (e.g, type 128 and 129).


<himanshu> Not true. The draft clearly states that (CE's) MAC address must =
be advertised in the LM message. The MAC address is augmented and is treate=
d as
part of PW-FEC. May be a sentence needs to be added to avoid the confusion.
[Lizhong] Now I get your meaning. Then the method described in draft is imp=
lementable, but the FEC definition is not good if MAC address is augmented =
to PW-FEC. I can summarise like that when PE advertise one FEC (e.g, type 1=
28 or 129) with MAC address and IP PW type, then PE should treat it as an u=
nidirectional PW and allocate a label for combination of FEC and MAC addres=
s. The concept is a bit different with the traditional one (RFC5036) where =
PE will only allocate label for FEC without considering any other value. A =
clarified sentance may not sufficient here......a new type of FEC would be =
best from my understanding.

[himanshu] - I don't think new FEC is necessary. I will let other authors a=
nd/or WG members to express their opinion.

Regards,
himanshu



--_000_C7FBB882383Bhshahforce10networkscom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: WG Last Call: draft-ietf-l2vpn-ipls-09</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:9pt'>Thanks Lizhong for yo=
ur further comments. Cut &amp; Paste below that is relevent..<BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Arial">What's mor=
e, it is also difficult to configure the PWid. If PEx uses PWid_1 for CEx1,=
 and PWid_2 for CEx2, according to section 7.1, the PEy needs to configure =
both PWid_1 and PWid_2, which is actually not necessary. Do I miss somethin=
g important here to understand the concept of unidirectional mp2p pseudowir=
e? There may be a new type of FEC that is required, similar with unidirecti=
onal P2MP PW.</FONT><FONT FACE=3D"Times New Roman"> <BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:9pt'><FONT COLOR=3D"#1E4=
87C"><FONT FACE=3D"Trebuchet MS"><B><I>[Himanshu&gt;] PWid is per IPLS inst=
ance and not per CE. I do not see any text in 7.1 which talks about configu=
ring difference PWid for each CE.</I></B></FONT></FONT><FONT FACE=3D"Ayutha=
ya"> <BR>
</FONT><FONT COLOR=3D"#1E487C"><FONT FACE=3D"Trebuchet MS"><B><I>For a give=
n IPLS instance a PE has following to signal &#8211;</I></B></FONT></FONT><=
FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1E487C"><FONT FACE=3D"Trebuchet MS"><B><I>a) &nbsp;&=
nbsp;&nbsp;PW id</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1E487C"><FONT FACE=3D"Trebuchet MS"><B><I>b) &nbsp;&=
nbsp;&nbsp;One MP2P &#8216;multicast&#8217; &nbsp;Ethernet PW</I></B></FONT=
></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#1E487C"><FONT FACE=3D"Trebuchet MS"><B><I>c) &nbsp;&=
nbsp;&nbsp;Many (i.e. one per local CE) MP2P &#8216;unicast&#8217; IP PW al=
ong with CE&#8217;s MAC address</I></B></FONT></FONT><FONT FACE=3D"Ayuthaya=
"> <BR>
</FONT><FONT COLOR=3D"#1E487C"><FONT FACE=3D"Times New Roman"><B><I>[Himans=
hu&gt;] </I></B>Section 7.1 describes details for send and receive processi=
ng of label mapping message</FONT></FONT><FONT FACE=3D"Ayuthaya"> <BR>
</FONT><FONT COLOR=3D"#0000FF"><FONT FACE=3D"Arial"><B>[Lizhong] Do you mea=
n PE will advertise all labels for CEs with same PWid? Then that means PE w=
ill advertise different labels for same FEC(same PWid), which will not oper=
ate correctly under current framework. The peer PE receiving several label =
mapping messages with same FEC but different labels will update the already=
 received label, and only retain the newest one. The way to solve this is t=
o define a new type of FEC to specify different operation comparing with no=
rmal FEC (e.g, type 128 and 129).</B></FONT></FONT><FONT FACE=3D"Ayuthaya">=
 <BR>
<BR>
<FONT COLOR=3D"#007F00"><BR>
&lt;himanshu&gt; Not true. The draft clearly states that (CE&#8217;s) MAC a=
ddress must be advertised in the LM message. The MAC address is augmented a=
nd is treated as<BR>
part of PW-FEC. May be a sentence needs to be added to avoid the confusion.=
</FONT> <BR>
<FONT COLOR=3D"#0000FF"><I>[Lizhong]</I></FONT></FONT><FONT COLOR=3D"#0000F=
F"><I><FONT FACE=3D"Arial"> Now I get your meaning. Then the method describ=
ed in draft is implementable, but the FEC definition is not good if MAC add=
ress is augmented to PW-FEC. I can summarise like that when PE advertise on=
e FEC (e.g, type 128 or 129) with MAC address and IP PW type, then PE shoul=
d treat it as an unidirectional PW and allocate a label for combination of =
FEC and MAC address. The concept is a bit different with the traditional on=
e (RFC5036) where PE will only allocate label for FEC without considering a=
ny other value. A clarified sentance may not sufficient here...</FONT></I><=
/FONT><I><FONT FACE=3D"Arial">..<FONT COLOR=3D"#0000FF">.a new type of FEC =
would be best from my understanding.<BR>
</FONT></FONT></I><FONT FACE=3D"Ayuthaya"><BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:9pt'><FONT FACE=3D"Ayut=
haya">[himanshu] - I don&#8217;t think new FEC is necessary. I will let oth=
er authors and/or WG members to express their opinion.<BR>
<BR>
Regards,<BR>
himanshu<BR>
<BR>
<BR>
</FONT></SPAN>
</BODY>
</HTML>


--_000_C7FBB882383Bhshahforce10networkscom_--

From hshah@force10networks.com  Mon Apr 26 19:10:40 2010
Return-Path: <hshah@force10networks.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 AD4EF28C1BE for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 19:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.544
X-Spam-Level: 
X-Spam-Status: No, score=-4.544 tagged_above=-999 required=5 tests=[AWL=0.195,  BAYES_20=-0.74, 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 cfy4x3zxLOUD for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 19:10:38 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id AC6593A67A2 for <l2vpn@ietf.org>; Mon, 26 Apr 2010 19:10:38 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Mon, 26 Apr 2010 19:10:26 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Mon, 26 Apr 2010 19:10:25 -0700
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNCB0egAN5+5b0=
Message-ID: <C7FBBFD1.3846%hshah@force10networks.com>
In-Reply-To: <C584046466ED224CA92C1BC3313B963E09DFEF6B09@INBANSXCHMBSA3.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7FBBFD13846hshahforce10networkscom_"
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, 27 Apr 2010 02:10:41 -0000

--_000_C7FBBFD13846hshahforce10networkscom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Pranjal,
Thanks for your comments.

Response in line..

Regards,
himanshu

On 4/22/10 12:08 PM, "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lu=
cent.com> wrote:

Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.

Section 7.2 IPV6 Capability advertisement.
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....
<Comment>

There is a need to consider the following case on IPV6 Capability negotiati=
on.

Let's take some sequence of events in IP L2 PW setup between A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs
   to do re-mapping. A sends label withdraw W1 first and
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It
   responds with unsolicited "release" R1 to A with status
   code S1 =3D "IP Address Type Mismatch" since B supports
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw
   W1 that A is waiting for. So it advertises L2 to B - the
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -
   unsolicited release.
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t
A but would be fine at B. Both ends are out of sync due to race conditions.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d
withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) whe=
n
it changes from IPV4 to IPV6 (but not vice versa). When B processes label
withdraw with status Code S2, no release should be sent as response and B
should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-1=
3
as well.

</Comment>


[himanshu] I understand your scenario. It seems that if label TLV is used f=
or
withdraw/release, label itself could be used to co-ordinate the release msg=
.
Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid
the race condition. I would like Mathew Bocci to comment on this too. Could
you send him an internal mail to draw his attention.



Section 7.3 Signaling Advertisement Processing

A PE should process a received [PWE3-CONTROL] advertisement with PW- type o=
f IP Layer2 transport for IPLS as follows,

        - Verify the IPLS VPN membership by matching the VPN-Id
          signaled in the AGI field or the PW-ID field with all the
          VPN-Ids configured in the PE. Discard and release the PW
          label if VPN-Id is not found.
        - Program the Forwarding Information Base (FIB) such that when
          a unicast IP packet is received from an AC with its
          destination MAC address matching the advertised MAC address,
          the packet is forwarded out over the tunnel to the
          advertising PE with the advertised PW-label as the inner
          label.

<Comment>

In section 6.1 we have described that there would be one PW (either P2MP or
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that w=
e
are signaling P2P PW per CE with FEC128 to receive unicast traffic and ther=
e
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS mem=
bership with FEC128 Pwid. If we need to advertise multiple CEs from same si=
te over same LDP signaling session, each with different labels then PWid
(VPN-ID) is not unique differentiator at receiver. It needs to be explained
in detail on how the PW setup would take place per CE using FEC128. For FEC=
129 different AC-ID can be used for each CE but with common AGI (=3D VPN-ID=
) to associate them to same IPLS instance at receivers.

</Comment>


[himanshu] This is a similar comment as LiZhong from ZTE. Hope you have fol=
lowed that discussions.
In a nutshell, PE must augment MAC address to PW-FEC and treat it as a uniq=
ue entity and apply
label operations (mapping/withdraw/FIB programming, etc) accordingly. Same =
comment applies to FEC129,
because note that multiple CEs can exist on a single AC.



Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane


--_000_C7FBBFD13846hshahforce10networkscom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: WG Last Call: draft-ietf-l2vpn-ipls-09</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:9pt'>Hi Pranjal,<BR>
Thanks for your comments.<BR>
<BR>
Response in line..<BR>
<BR>
Regards,<BR>
himanshu<BR>
<BR>
On 4/22/10 12:08 PM, &quot;Dutta, Pranjal K (Pranjal)&quot; &lt;<a href=3D"=
pranjal.dutta@alcatel-lucent.com">pranjal.dutta@alcatel-lucent.com</a>&gt; =
wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:=
9pt'>Hello Authors and WG,<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;Here are some of my review comments on this version=
 of the I-D.<BR>
&nbsp;&nbsp;<BR>
Section 7.2 IPV6 Capability advertisement.<BR>
&nbsp;&nbsp;&nbsp;....<BR>
&nbsp;&nbsp;&nbsp;A PE that supports IPv6 on an IP PW MUST signal the stack=
 capability<BR>
&nbsp;&nbsp;&nbsp;sub-TLV in the initial label mapping message for the PW. =
The PE<BR>
&nbsp;&nbsp;&nbsp;nodes compare the value advertised by the remote PE with =
the local<BR>
&nbsp;&nbsp;&nbsp;configuration and only use a capability which is advertis=
ed by both.<BR>
&nbsp;&nbsp;&nbsp;If a PE that supports IPv6 does not receive a 'stack capa=
bility'<BR>
&nbsp;&nbsp;&nbsp;sub-TLV from the far-end PE in the initial label mapping =
message, or<BR>
&nbsp;&nbsp;&nbsp;one is received but it is set to a reserved value, the PE=
 MUST send<BR>
&nbsp;&nbsp;&nbsp;an unsolicited release for the PW label with the LDP stat=
us code<BR>
&nbsp;&nbsp;&nbsp;meaning ''IP Address type mismatch'' (Status Code 0x00000=
04A).<BR>
&nbsp;&nbsp;&nbsp;....<BR>
&lt;Comment&gt;<BR>
<BR>
There is a need to consider the following case on IPV6 Capability negotiati=
on.<BR>
<BR>
Let's take some sequence of events in IP L2 PW setup between A and B.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A---------------------B<BR>
<BR>
A is configured with IPV4 only initially.<BR>
B supports both IPV6 + IPv4.<BR>
<BR>
1. A sends initial label mapping L1 for IPV4 PW setup to B.<BR>
&nbsp;&nbsp;&nbsp;L1 is waiting in B to get processed.<BR>
2. Now we configured ipv6 capability in A. So A needs<BR>
&nbsp;&nbsp;&nbsp;to do re-mapping. A sends label withdraw W1 first and<BR>
&nbsp;&nbsp;&nbsp;then awaits for label release from B to re-advertise<BR>
&nbsp;&nbsp;&nbsp;with IPV4 + IPV6 capability. So label withdraw W1 is<BR>
&nbsp;&nbsp;&nbsp;in queue after the initial label Map L1 at B.<BR>
3. Now B processes the initial label map L1 from A. It<BR>
&nbsp;&nbsp;&nbsp;responds with unsolicited &quot;release&quot; R1 to A wit=
h status<BR>
&nbsp;&nbsp;&nbsp;code S1 =3D &quot;IP Address Type Mismatch&quot; since B =
supports<BR>
&nbsp;&nbsp;&nbsp;IPV4 + IPV6.<BR>
4. Now A processes R1 and thinks it's the Release to withdraw<BR>
&nbsp;&nbsp;&nbsp;W1 that A is waiting for. So it advertises L2 to B - the<=
BR>
&nbsp;&nbsp;&nbsp;new Label mapping with IPV4 + IPV6.<BR>
5. B processes W1 now and responds back with regular Release R2.<BR>
6. A thinks that its label map L2 is being released by R2 -<BR>
&nbsp;&nbsp;&nbsp;unsolicited release. <BR>
7. B processes L2 and is happy with it.<BR>
<BR>
At the end of this re-negotiation, the PW would never be operationally up a=
t<BR>
A but would be fine at B. Both ends are out of sync due to race conditions.=
<BR>
<BR>
So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d<BR>
withdraw W1 with a new status code S2 =3D &quot;Wrong IP Address Type&quot;=
 (e.g) when<BR>
it changes from IPV4 to IPV6 (but not vice versa). When B processes label<B=
R>
withdraw with status Code S2, no release should be sent as response and B<B=
R>
should continue to wait for next control message from A.<BR>
<BR>
We do similar procedures with cBit re-negotiation. Please refer to section<=
BR>
6.2 in RFC 4447 on usage of &quot;Wrong C-bit&quot;.<BR>
<BR>
Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-1=
3<BR>
as well.<BR>
<BR>
&lt;/Comment&gt;<BR>
<BR>
<BR>
[himanshu] I understand your scenario. It seems that if label TLV is used f=
or<BR>
withdraw/release, label itself could be used to co-ordinate the release msg=
.<BR>
Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid=
<BR>
the race condition. I would like Mathew Bocci to comment on this too. Could=
<BR>
you send him an internal mail to draw his attention. <BR>
<BR>
<BR>
<BR>
Section 7.3 Signaling Advertisement Processing<BR>
<BR>
A PE should process a received [PWE3-CONTROL] advertisement with PW- type o=
f IP Layer2 transport for IPLS as follows,<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Verify the IPLS VPN membe=
rship by matching the VPN-Id<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;signaled in the=
 AGI field or the PW-ID field with all the<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;VPN-Ids configu=
red in the PE. Discard and release the PW<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;label if VPN-Id=
 is not found.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Program the Forwarding In=
formation Base (FIB) such that when<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a unicast IP pa=
cket is received from an AC with its<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;destination MAC=
 address matching the advertised MAC address,<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the packet is f=
orwarded out over the tunnel to the<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;advertising PE =
with the advertised PW-label as the inner<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;label.<BR>
&nbsp;&nbsp;<BR>
&lt;Comment&gt;<BR>
<BR>
In section 6.1 we have described that there would be one PW (either P2MP or=
<BR>
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that w=
e<BR>
are signaling P2P PW per CE with FEC128 to receive unicast traffic and ther=
e<BR>
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS mem=
bership with FEC128 Pwid. If we need to advertise multiple CEs from same si=
te over same LDP signaling session, each with different labels then PWid<BR=
>
(VPN-ID) is not unique differentiator at receiver. It needs to be explained=
<BR>
in detail on how the PW setup would take place per CE using FEC128. For FEC=
129 different AC-ID can be used for each CE but with common AGI (=3D VPN-ID=
) to associate them to same IPLS instance at receivers.<BR>
<BR>
&lt;/Comment&gt;<BR>
<BR>
<BR>
[himanshu] This is a similar comment as LiZhong from ZTE. Hope you have fol=
lowed that discussions.<BR>
In a nutshell, PE must augment MAC address to PW-FEC and treat it as a uniq=
ue entity and apply<BR>
label operations (mapping/withdraw/FIB programming, etc) accordingly. Same =
comment applies to FEC129,<BR>
because note that multiple CEs can exist on a single AC.<BR>
&nbsp;<BR>
<BR>
&nbsp;<BR>
Thanks,<BR>
Pranjal<BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"l2vpn-bounces@ietf.org">l2vpn-bounces@ietf.org</a> [<a hre=
f=3D"mailto:l2vpn-bounces@ietf.org">mailto:l2vpn-bounces@ietf.org</a>] On B=
ehalf Of Shane Amante<BR>
Sent: Monday, April 05, 2010 6:58 PM<BR>
To: <a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><BR>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<BR>
<BR>
Hi Everyone,<BR>
<BR>
This is to begin a (final) WG Last Call on:<BR>
<a href=3D"http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09">http://tool=
s.ietf.org/html/draft-ietf-l2vpn-ipls-09</a><BR>
<BR>
If you have substantial technical comments or concerns, please share them w=
ith the list. &nbsp;If you have editorial comments, please share them direc=
tly with the authors and co-chairs.<BR>
<BR>
So far, we have the following folks signed up for a thorough review and com=
ments:<BR>
- Andy Malis<BR>
- Nick DelRegno<BR>
- Pranjal Dutta<BR>
However, we could use more people to conduct a review. &nbsp;If you have th=
e time and/or inclination, please let the chairs know if you'll be conducti=
ng a review.<BR>
<BR>
The Last Call on this draft will also end on April 23.<BR>
<BR>
Thanks,<BR>
<BR>
Giles &amp; Shane<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C7FBBFD13846hshahforce10networkscom_--

From hshah@force10networks.com  Mon Apr 26 19:21:31 2010
Return-Path: <hshah@force10networks.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 72B4728C1D2 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 19:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level: 
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_50=0.001, 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 mgWkaT5qlm+8 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 19:21:28 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id 5A5E228C1DA for <l2vpn@ietf.org>; Mon, 26 Apr 2010 19:21:05 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Mon, 26 Apr 2010 19:20:53 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: "PAULING, JOEL (JOEL)" <joel.pauling@alcatel-lucent.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Mon, 26 Apr 2010 19:20:50 -0700
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLKV0PSguv1yOSDSMtyd3zpMAzQABQgJQArEKIyAAEAiqIAFekhBU
Message-ID: <C7FBC242.3849%hshah@force10networks.com>
In-Reply-To: <2B79F1682D699B45839C711B092EA89EA3EC2FD6BA@SGSINSXCHMBSA2.sg.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7FBC2423849hshahforce10networkscom_"
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, 27 Apr 2010 02:21:32 -0000

--_000_C7FBC2423849hshahforce10networkscom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

OK. I suppose if you believe a lack of fallback configuration switch could =
be impediment
for a rollout, we should add it in.

Thanks,
himanshu


On 4/19/10 11:16 PM, "PAULING, JOEL (JOEL)" <joel.pauling@alcatel-lucent.co=
m> wrote:

Thanks,

I understand your position but I can see ipls being a significant component=
 in a V6 centric infrastructure as an alternative way to deliver v4 sans DS=
-lite etc. Because of this very likely scenario and also the push to MPLS-T=
P in the core (san's any IP layer involvement) I think this may be importan=
t to remove a v4 fallback as a default.

-JoelW

-----Original Message-----
From: Himanshu Shah [mailto:hshah@force10networks.com]
Sent: Tuesday, 20 April 2010 7:44 a.m.
To: PAULING, JOEL (JOEL); l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Joel -
Thanks for your comment.

While you make a good a point, here is what my thinking behind it.

IPLS was designed originally for IPv4 and existed for a long time before su=
pport of IPv6 added. If there is any implementation out there, they have IP=
v4 support for it and would like to see a newer implementation be compatibl=
e with existing.

Secondly, it is always desirable that an RFC provide 'a base version' that =
is at minimum be compatible and interoperable with other implementations.

Nonetheless, you make a good point and would like to hear from other member=
s of the WG that entertain a possibility of IPv6 only IPLS (a possibility, =
with a fallback tunable option).

Regards,
himanshu


-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of P=
AULING JOEL
Sent: Monday, April 05, 2010 10:40 PM
To: l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Looks good.

One comment:

Re fallback protocol (proposed to be IPv4) should be a tuneable option. Whi=
le the V6 compatibility flag currently signals v6 stack compatibility on th=
e tunnel end point, I would prefer from a future proofing perspective if th=
e fallback protocol was definable.

Especially in MPLS PE-PE scenarios, it is preferable to run either IPV4 + M=
PLS OR IPV6 + MPLS, rather than both through a MS core network (reducing ad=
min overhead by having to maintain two stacks). Having fallback protocol be=
 a tuneable option will cater to this scenario better than current proposed=
 draft.


Kind regards


Joel W Pauling

Network Capability Engineer
Alcatel-Lucent New Zealand
+64 4 803 7639
+64 21 171 8049
joel.pauling@alcatel-lucent.com

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Tuesday, 6 April 2010 1:58 p.m.
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane


--_000_C7FBC2423849hshahforce10networkscom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: WG Last Call: draft-ietf-l2vpn-ipls-09</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:9pt'>OK. I suppose if you =
believe a lack of fallback configuration switch could be impediment<BR>
for a rollout, we should add it in.<BR>
<BR>
Thanks,<BR>
himanshu <BR>
<BR>
<BR>
On 4/19/10 11:16 PM, &quot;PAULING, JOEL (JOEL)&quot; &lt;<a href=3D"joel.p=
auling@alcatel-lucent.com">joel.pauling@alcatel-lucent.com</a>&gt; wrote:<B=
R>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Ayuthaya"><SPAN STYLE=3D'font-size:=
9pt'>Thanks,<BR>
<BR>
I understand your position but I can see ipls being a significant component=
 in a V6 centric infrastructure as an alternative way to deliver v4 sans DS=
-lite etc. Because of this very likely scenario and also the push to MPLS-T=
P in the core (san's any IP layer involvement) I think this may be importan=
t to remove a v4 fallback as a default.<BR>
<BR>
-JoelW<BR>
<BR>
-----Original Message-----<BR>
From: Himanshu Shah [<a href=3D"mailto:hshah@force10networks.com">mailto:hs=
hah@force10networks.com</a>]<BR>
Sent: Tuesday, 20 April 2010 7:44 a.m.<BR>
To: PAULING, JOEL (JOEL); <a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><BR>
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09<BR>
<BR>
Hi Joel -<BR>
Thanks for your comment.<BR>
<BR>
While you make a good a point, here is what my thinking behind it.<BR>
<BR>
IPLS was designed originally for IPv4 and existed for a long time before su=
pport of IPv6 added. If there is any implementation out there, they have IP=
v4 support for it and would like to see a newer implementation be compatibl=
e with existing.<BR>
<BR>
Secondly, it is always desirable that an RFC provide 'a base version' that =
is at minimum be compatible and interoperable with other implementations.<B=
R>
<BR>
Nonetheless, you make a good point and would like to hear from other member=
s of the WG that entertain a possibility of IPv6 only IPLS (a possibility, =
with a fallback tunable option).<BR>
<BR>
Regards,<BR>
himanshu<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"l2vpn-bounces@ietf.org">l2vpn-bounces@ietf.org</a> [<a hre=
f=3D"mailto:l2vpn-bounces@ietf.org">mailto:l2vpn-bounces@ietf.org</a>] On B=
ehalf Of PAULING JOEL<BR>
Sent: Monday, April 05, 2010 10:40 PM<BR>
To: <a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><BR>
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09<BR>
<BR>
Looks good.<BR>
<BR>
One comment:<BR>
<BR>
Re fallback protocol (proposed to be IPv4) should be a tuneable option. Whi=
le the V6 compatibility flag currently signals v6 stack compatibility on th=
e tunnel end point, I would prefer from a future proofing perspective if th=
e fallback protocol was definable.<BR>
<BR>
Especially in MPLS PE-PE scenarios, it is preferable to run either IPV4 + M=
PLS OR IPV6 + MPLS, rather than both through a MS core network (reducing ad=
min overhead by having to maintain two stacks). Having fallback protocol be=
 a tuneable option will cater to this scenario better than current proposed=
 draft.<BR>
<BR>
<BR>
Kind regards<BR>
<BR>
<BR>
Joel W Pauling<BR>
<BR>
Network Capability Engineer<BR>
Alcatel-Lucent New Zealand<BR>
+64 4 803 7639<BR>
+64 21 171 8049<BR>
<a href=3D"joel.pauling@alcatel-lucent.com">joel.pauling@alcatel-lucent.com=
</a><BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"l2vpn-bounces@ietf.org">l2vpn-bounces@ietf.org</a> [<a hre=
f=3D"mailto:l2vpn-bounces@ietf.org">mailto:l2vpn-bounces@ietf.org</a>] On B=
ehalf Of Shane Amante<BR>
Sent: Tuesday, 6 April 2010 1:58 p.m.<BR>
To: <a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><BR>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<BR>
<BR>
Hi Everyone,<BR>
<BR>
This is to begin a (final) WG Last Call on:<BR>
<a href=3D"http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09">http://tool=
s.ietf.org/html/draft-ietf-l2vpn-ipls-09</a><BR>
<BR>
If you have substantial technical comments or concerns, please share them w=
ith the list. &nbsp;If you have editorial comments, please share them direc=
tly with the authors and co-chairs.<BR>
<BR>
So far, we have the following folks signed up for a thorough review and com=
ments:<BR>
- Andy Malis<BR>
- Nick DelRegno<BR>
- Pranjal Dutta<BR>
However, we could use more people to conduct a review. &nbsp;If you have th=
e time and/or inclination, please let the chairs know if you'll be conducti=
ng a review.<BR>
<BR>
The Last Call on this draft will also end on April 23.<BR>
<BR>
Thanks,<BR>
<BR>
Giles &amp; Shane<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C7FBC2423849hshahforce10networkscom_--

From raymond.key@ieee.org  Mon Apr 26 20:11:21 2010
Return-Path: <raymond.key@ieee.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 4E46328C117 for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 20:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.916
X-Spam-Level: 
X-Spam-Status: No, score=-99.916 tagged_above=-999 required=5 tests=[AWL=1.176, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327,  MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQD6OofoLFTw for <l2vpn@core3.amsl.com>; Mon, 26 Apr 2010 20:11:19 -0700 (PDT)
Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by core3.amsl.com (Postfix) with ESMTP id 70EBC3A6C1B for <l2vpn@ietf.org>; Mon, 26 Apr 2010 20:11:02 -0700 (PDT)
Received: from localhost.localdomain (webmail06.syd.optusnet.com.au [211.29.133.86]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o3R3AfRo007835; Tue, 27 Apr 2010 13:10:42 +1000
Message-Id: <201004270310.o3R3AfRo007835@mail02.syd.optusnet.com.au>
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
X-Mailer: MIME-tools 5.420 (Entity 5.420)
Received: from bcavo.tcif.telstra.com.au ([203.35.135.133]) by webmail06.syd.optusnet.com.au with http (user=rkey_ieee@optusnet.com.au); Tue, 27 Apr 2010 13:10:36 +1000
From: Raymond Key <raymond.key@ieee.org>
To: "UTTARO, JAMES (ATTLABS)" <ju1738@att.com>
Date: Tue, 27 Apr 2010 13:10:36 +1000
Subject: RE: Comments on draft-key-l2vpn-vpls-etree-02
Cc: l2vpn@ietf.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raymond.key@ieee.org
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, 27 Apr 2010 03:11:21 -0000

Hi Jim,

Thanks for your questions.

I have attempted to address these in section 4.3 in the draft - 
Additional Action in Data Forwarding 
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-4.3)

a) If Leafs are on the same PE how will the CW function? Will we need to rely 
on some other mechanism to prevent Leaf<>Leaf traffic on the same PE ?

[RK] Leaf AC -> Leaf AC Same PE : Rule 6 in Table 1

[RK] When both ingress AC and egress AC are on the same PE, PW is not 
involved and hence CW is not applicable.

b) Leaf->Root traffic on the same PE? We don't want the Root to simply forward 
the traffic directly to another Leaf either on the PE or via a PW to a remote PE.. 
How is this accomplished?

[RK] Leaf AC -> Root AC Same PE : Rule 1 in Table 1

[RK] Root AC -> Leaf AC Same PE : Rule 5 in Table 1

[RK] Root AC -> Leaf AC Remote PE
          Ingress PE (Root AC -> PW) : Rule 2 and Rule 3 in Table 1
          Egress PE (PW -> Leaf AC) : Rule 7 and Rule 8 in Table 1

Have a read on the section 4.3 and see if it works.

Thanks,
Raymond


> UTTARO, JAMES (ATTLABS) <ju1738@att.com> wrote:
> 
> I guess  am still a bit confused as to how this would work when there
> are leafs and roots on the same PE..
> 
> a) If Leafs are on the same PE how will the CW function? Will we need to
> rely on some other mechanism to prevent Leaf<>Leaf traffic on the same
> PE ?
> 
> b) Leaf->Root traffic on the same PE? We don't want the Root to simply
> forward the traffic directly to another Leaf either on the PE or via a
> PW to a remote PE.. How is this accomplished?
> 
> Comments In-Line..
> 
> Jim Uttaro
> 
> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
> Of Raymond Key
> Sent: Friday, April 23, 2010 9:39 PM
> To: Delregno, Christopher N (Nick DelRegno)
> Cc: l2vpn@ietf.org
> Subject: Comments on draft-key-l2vpn-vpls-etree-02
> 
> Hi Nick,
> 
> Thanks for your comment.
> 
> Quote from your email, "However, if we are relying on CW to indicate
> leaf/root and the targeted PE doesn't support CW, then the ETREE model
> breaks as I can no longer determine leaf/root and drop/forward traffic
> accordingly."
> 
> There may be some confusion here. When the targeted PE doesn't support 
> CW, it also implies the targeted PE doesn't support the extension 
> specified in this draft (see section 4.2, "A PE MUST be capable of 
> sending and receiving the Control Word on Ethernet PW") and hence the 
> targeted PE has only Root ACs. This is a backward compatibility 
> scenario and does not result in any problem.
> 
> [Jim U>] From an SP perspective this approach represents a major
> operational/provisioning challenge.. We would now need to track the set
> of PEs that are candidates for Roots ( No CW Capable ), Roots and Leafs,
> Leafs only. We cannot easily go back and change our homing rules. This
> would also impact the provisonable footprint.
> 
> Backward compatibility issues are discussed in section 5 in the draft. 
> (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5)
> Some paragraphs are extracted below.
> 
> (5.3. Additional Action in Data Forwarding)
> 
> For backward compatibility reason, a PE not supporting the extension
> specified in this document can participate in an E-Tree construct,
> but only Root ACs can be connected to such PE.
> 
> Lack of Control Word L-bit per-payload signaling between a PE
> supporting the extension specified in this document and a PE not
> supporting such extension does not result in any problem.
> 
> (5.3.1 Ingress PE Support the Extension but Egress PE Not)
> 
> If Control Word is not used on the Ethernet PW, there will be no CW
> L-bit. The egress PE will forward the frame as per current standard.
> This is correct as only Root ACs exist on a PE not supporting the
> extension specified in this document.  A Root AC can receive from any
> other ACs.
> 
> By the way I recently posted a draft "Requirements for MEF E-Tree 
> Support in VPLS" 
> (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-reqt-00)
> trying to start a "solution-neutral" discussion on whether there is a 
> valid requirement to enhance VPLS or not. Any comments on that draft?
> 
> Thanks,
> Raymond 
> 
> 
> > Delregno, Christopher N (Nick DelRegno) <nick.delregno@verizon.com>
> wrote:
> > 
> > Raymond:
> > 
> > From a purely T-LDP perspective, I agree.  However, if we are relying
> on
> > CW to indicate leaf/root and the targeted PE doesn't support CW, then
> > the ETREE model breaks as I can no longer determine leaf/root and
> > drop/forward traffic accordingly.  As such, the implementation
> behavior
> > when using CW to indicate Leaf/Root MUST NOT allow the CW preference
> > mismatch to result in an active PW.
> > 
> > Thanks,
> > Nick
> > 
> > -----Original Message-----
> > From: Raymond Key [mailto:raymond.key@ieee.org] 
> > Sent: Wednesday, April 21, 2010 4:55 PM
> > To: Delregno, Christopher N (Nick DelRegno)
> > Cc: l2vpn@ietf.org
> > Subject: Re: Updated minutes from IETF 77
> > 
> > Hi Nic,
> > 
> > I go through the recently published IETF77 L2VPN minutes and would
> like
> > to follow up on one of your comments.
> > 
> > Extract from minutes under
> > 10) Extension to VPLS for E-Tree
> > "Nic: This requires a control word, so a box has to support a control
> > word. 
> > PW mustn't come up if a CW is not supported."
> > 
> > There may be some confusion here. When one PE does not support control
> > word, PW can still come up.
> > 
> > Refer to Section 5.2. Control Word (under Backward Compatibility) For
> > backward compatibility reason, use of Control Word on Ethernet PW is
> not
> > mandatory. If the PE on the other end prefers not to use Control Word
> or
> > does not support Control Word (which implies such PE does not support
> > the extension specified in this document), then Control Word will not
> be
> > used on the Ethernet PW.
> > Refer to Appendix A for different Control Word scenarios.
> > (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5.2)
> > 
> > Regards,
> > Raymond Key
> > 
> > 
> > > Giles Heron <giles.heron@gmail.com> wrote:
> > > 
> > > Ok - so it'd help if I actually put some content in my email.
> > > 
> > > As Simon Delord helpfully pointed out the other day I missed the 
> > > second half of the meeting out when I posted these.
> > > 
> > > I've now updated the online minutes:
> > > 
> > > http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
> > > 
> > > Giles

From hshah@force10networks.com  Tue Apr 27 11:17:51 2010
Return-Path: <hshah@force10networks.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 67B3B28C1C4 for <l2vpn@core3.amsl.com>; Tue, 27 Apr 2010 11:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.177
X-Spam-Level: 
X-Spam-Status: No, score=-4.177 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_50=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 KuIlK4s4Cb9F for <l2vpn@core3.amsl.com>; Tue, 27 Apr 2010 11:17:50 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id 88EDD28C1BD for <l2vpn@ietf.org>; Tue, 27 Apr 2010 11:17:38 -0700 (PDT)
Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Tue, 27 Apr 2010 11:17:26 -0700
From: Himanshu Shah <hshah@force10networks.com>
To: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Tue, 27 Apr 2010 11:17:28 -0700
Subject: RE: WG Last Call:  draft-ietf-l2vpn-arp-mediation-13
Thread-Topic: WG Last Call:  draft-ietf-l2vpn-arp-mediation-13
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNBG3HAAADNZ5AA/6rxIA==
Message-ID: <34F81DE93A7AA840A6A3B1187BAD5FC80379DE5769@EXCH-CLUSTER-10.force10networks.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net> <C584046466ED224CA92C1BC3313B963E09DFEF6B04@INBANSXCHMBSA3.in.alcatel-lucent.com>
In-Reply-To: <C584046466ED224CA92C1BC3313B963E09DFEF6B04@INBANSXCHMBSA3.in.alcatel-lucent.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-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, 27 Apr 2010 18:17:51 -0000

Hi Pranjal -=20
Thanks for the review and the comments.
Comments in line..

/himanshu

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of D=
utta, Pranjal K (Pranjal)
Sent: Thursday, April 22, 2010 11:59 AM
To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-arp-mediation-13

Sorry this was for arp-mediation draft. So please read it for other one
and NOT for ipls draft.=20

Shane : I have changed your subject line :-) in this thread.

-----Original Message-----
From: Dutta, Pranjal K (Pranjal)=20
Sent: Thursday, April 22, 2010 8:55 AM
To: 'Shane Amante'; l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.=20

In Section 6.1 When to Signal an IPv4 address of a CE
     ....
     Similarly, if the PE detects that an IP address of a CE is no
     longer valid (by methods described above), the PE must re-
     advertise the PW FEC with null IP address to denote the
     withdrawal of IP address of the CE. The receiving PE then waits
     for notification of the remote IP address. During this period,
     propagation of unicast IPv4 traffic is suspended, but multicast
     IPv4 traffic can continue to flow between the AC and the
     pseudowire.
     ....
     <Comment>=20
     I think we need to expand a bit on "PE must re-advertise the=20
     PW FEC with null IP address". Section 6.2 also specifies LDP
     Notification message to reflect any change in CE address without=20
     re-mapping/re-advertising if label has been advertised already.
     Otherwise it's a bit ambiguous on whether to use label withdraw=20
     on moving from 'non-zero' CE address to 'zero' CE address or    =20
     reflect the change with CE address change Notification Message.
    </Comment>

[Himanshu>]  Section 5 discusses the how CE discovery and PW=20
establishment procedures are decoupled. They need to be,=20
especially for multicast traffic to flow, which in turn aids in CE
discovery. Hence the 'label withdraw' and 'address withdraw' are
kept separate. The label withdraw would apply only when the=20
service is no longer configured or unfavorable to both parties.
The 'address withdraw' cases are described the draft.



Section 7. IPV6 Capability Advertisement
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....

<Comment>

There is a need to consider the following case on IPV6=20
Capability negotiation.

Let's take some sequence of events in IP L2 PW setup between=20
A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs=20
   to do re-mapping. A sends label withdraw W1 first and=20
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is=20
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It=20
   responds with unsolicited "release" R1 to A with status=20
   code S1 =3D "IP Address Type Mismatch" since B supports=20
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw=20
   W1 that A is waiting for. So it advertises L2 to B - the=20
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -=20
   unsolicited release. =20
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t A but would be fine at B. Both ends are out of sync due to race condition=
s.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) w=
hen it changes from IPV4 to IPV6 (but not vice versa). When B processes lab=
el withdraw with status Code S2, no release should be sent as response and =
B should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section =
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7.2 in draft-ietf-l2vpn-ipls-09 as we=
ll.
</Comment>

[Himanshu>]  Cut & Paste below from the response on ipls comment (for those=
 who may not have read IPLS mails)

[himanshu] "I understand your scenario. It seems that if label TLV is used =
for
withdraw/release, label itself could be used to co-ordinate the release msg=
.
Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid
the race condition. I would like Mathew Bocci to comment on this too. Could
you send him an internal mail to draw his attention."


Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

From pranjal.dutta@alcatel-lucent.com  Tue Apr 27 19:49:04 2010
Return-Path: <pranjal.dutta@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 0EBF53A68DB for <l2vpn@core3.amsl.com>; Tue, 27 Apr 2010 19:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.123
X-Spam-Level: 
X-Spam-Status: No, score=-0.123 tagged_above=-999 required=5 tests=[AWL=-1.609, BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9GYZ7PfHjCZ for <l2vpn@core3.amsl.com>; Tue, 27 Apr 2010 19:48:52 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 7FD113A6782 for <l2vpn@ietf.org>; Tue, 27 Apr 2010 19:48:51 -0700 (PDT)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o3S2mTic019800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Apr 2010 21:48:31 -0500 (CDT)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3S2mPFH016128 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 28 Apr 2010 08:18:27 +0530
Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 28 Apr 2010 08:18:25 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
To: Himanshu Shah <hshah@force10networks.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Wed, 28 Apr 2010 08:18:21 +0530
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNCB0egAN5+5b0AMnY/IA==
Message-ID: <C584046466ED224CA92C1BC3313B963E09E06F293E@INBANSXCHMBSA3.in.alcatel-lucent.com>
References: <C584046466ED224CA92C1BC3313B963E09DFEF6B09@INBANSXCHMBSA3.in.alcatel-lucent.com> <C7FBBFD1.3846%hshah@force10networks.com>
In-Reply-To: <C7FBBFD1.3846%hshah@force10networks.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_C584046466ED224CA92C1BC3313B963E09E06F293EINBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
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, 28 Apr 2010 02:49:04 -0000

--_000_C584046466ED224CA92C1BC3313B963E09E06F293EINBANSXCHMBSA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Himanshu,
                           Please refer my responses inline in blue.

Thanks,
Pranjal
________________________________
From: Himanshu Shah [mailto:hshah@force10networks.com]
Sent: Monday, April 26, 2010 7:10 PM
To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Pranjal,
Thanks for your comments.

Response in line..

Regards,
himanshu

On 4/22/10 12:08 PM, "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lu=
cent.com> wrote:
Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.

Section 7.2 IPV6 Capability advertisement.
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....
<Comment>

There is a need to consider the following case on IPV6 Capability negotiati=
on.

Let's take some sequence of events in IP L2 PW setup between A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs
   to do re-mapping. A sends label withdraw W1 first and
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It
   responds with unsolicited "release" R1 to A with status
   code S1 =3D "IP Address Type Mismatch" since B supports
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw
   W1 that A is waiting for. So it advertises L2 to B - the
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -
   unsolicited release.
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t
A but would be fine at B. Both ends are out of sync due to race conditions.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d
withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) whe=
n
it changes from IPV4 to IPV6 (but not vice versa). When B processes label
withdraw with status Code S2, no release should be sent as response and B
should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-1=
3
as well.

</Comment>


[himanshu] I understand your scenario. It seems that if label TLV is used f=
or
withdraw/release, label itself could be used to co-ordinate the release msg=
.
Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid
the race condition. I would like Mathew Bocci to comment on this too. Could
you send him an internal mail to draw his attention.

[Pranjal] No really. We can't use label TLV as reliable method for withdraw=
/
releases. If we refer to section 3.5.10 and 3.5.11 in RFC 5036, label TLV i=
s
OPTIONAL in LDP label withdraw/release messages. Sure, I would bring this
into Mathew's attention.

Section 7.3 Signaling Advertisement Processing

A PE should process a received [PWE3-CONTROL] advertisement with PW- type o=
f IP Layer2 transport for IPLS as follows,

        - Verify the IPLS VPN membership by matching the VPN-Id
          signaled in the AGI field or the PW-ID field with all the
          VPN-Ids configured in the PE. Discard and release the PW
          label if VPN-Id is not found.
        - Program the Forwarding Information Base (FIB) such that when
          a unicast IP packet is received from an AC with its
          destination MAC address matching the advertised MAC address,
          the packet is forwarded out over the tunnel to the
          advertising PE with the advertised PW-label as the inner
          label.

<Comment>

In section 6.1 we have described that there would be one PW (either P2MP or
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that w=
e
are signaling P2P PW per CE with FEC128 to receive unicast traffic and ther=
e
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS mem=
bership with FEC128 Pwid. If we need to advertise multiple CEs from same si=
te over same LDP signaling session, each with different labels then PWid
(VPN-ID) is not unique differentiator at receiver. It needs to be explained
in detail on how the PW setup would take place per CE using FEC128. For FEC=
129 different AC-ID can be used for each CE but with common AGI (=3D VPN-ID=
) to associate them to same IPLS instance at receivers.

</Comment>


[himanshu] This is a similar comment as LiZhong from ZTE. Hope you have fol=
lowed that discussions.
In a nutshell, PE must augment MAC address to PW-FEC and treat it as a uniq=
ue entity and apply
label operations (mapping/withdraw/FIB programming, etc) accordingly. Same =
comment applies to FEC129,
because note that multiple CEs can exist on a single AC.

[Pranjal] Yes, I am following your exchanges with Lizhong. But still I was =
not
          able to make it work from an implementation perspective. If we wo=
uld
          want to augment the PW-FEC "as is" with MAC address and apply lab=
el
          operations then we need to define a new FEC type (e.g FEC128/129 =
+ MAC).
          Here, IPLS VPN-ID is NOT the FEC, but the unidirectional PW used =
in IPLS
          is. Having a new FEC type makes existing PW/L2VPN much cleaner. E=
xisting
          implementations would consider one label from a peer against a PW=
 (which
          is a FEC as per RFC 4447).

          In IPLS, the intent is to have the ability to associate VPN membe=
rship
          (thru common FEC 128/FEC129) but also have unidirectional PWs per=
 CE MAC
          address. As an example, we do the same with FEC129 based LDP VPLS=
 with BGP
          Autodiscovery. The AGI (which is part of FEC129 but doesn't defin=
e a
          specific PW) matches the VPLS ID  (VPN membership) even though FE=
C(AGI +
          SAII + TAII) s of each PWs are different. In similar note IPLS is=
 a service
          that needs to build undirectional PW (FEC) infrastructure using a=
 common
          denominator as VPN-ID.





Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

--_000_C584046466ED224CA92C1BC3313B963E09E06F293EINBANSXCHMBSA_
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: WG Last Call: draft-ietf-l2vpn-ipls-09</title>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Device Font 12cpi";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Ayuthaya;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi Himanshu,<o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Please refer my responses inline in </span></font><b><font size=3D2 color=
=3Dblue
face=3D"Device Font 12cpi"><span style=3D'font-size:10.0pt;font-family:"Dev=
ice Font 12cpi";
color:blue;font-weight:bold'>blue</span></font></b><font size=3D2 color=3Dn=
avy
face=3D"Device Font 12cpi"><span style=3D'font-size:10.0pt;font-family:"Dev=
ice Font 12cpi";
color:navy'>.</span></font><font size=3D2 color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span><=
/font></p>

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

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Pranjal<o:p></o:p></span></font></p>

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Himanshu=
 Shah
[mailto:hshah@force10networks.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, April 26, 2010=
 7:10
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Dutta, Pranjal K (Pranja=
l);
Shane Amante; l2vpn@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: WG Last Call:
draft-ietf-l2vpn-ipls-09</span></font><o:p></o:p></p>

</div>

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D1 face=3DA=
yuthaya><span
style=3D'font-size:9.0pt;font-family:Ayuthaya'>Hi Pranjal,<br>
Thanks for your comments.<br>
<br>
Response in line..<br>
<br>
Regards,<br>
himanshu<br>
<br>
On 4/22/10 12:08 PM, &quot;Dutta, Pranjal K (Pranjal)&quot; &lt;<a
href=3D"pranjal.dutta@alcatel-lucent.com">pranjal.dutta@alcatel-lucent.com<=
/a>&gt;
wrote:</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D1 face=3DA=
yuthaya><span
style=3D'font-size:9.0pt;font-family:Ayuthaya'>Hello Authors and WG,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;Here are some of my review comments on this version=
 of
the I-D.<br>
&nbsp;&nbsp;<br>
Section 7.2 IPV6 Capability advertisement.<br>
&nbsp;&nbsp;&nbsp;....<br>
&nbsp;&nbsp;&nbsp;A PE that supports IPv6 on an IP PW MUST signal the stack
capability<br>
&nbsp;&nbsp;&nbsp;sub-TLV in the initial label mapping message for the PW. =
The
PE<br>
&nbsp;&nbsp;&nbsp;nodes compare the value advertised by the remote PE with =
the
local<br>
&nbsp;&nbsp;&nbsp;configuration and only use a capability which is advertis=
ed
by both.<br>
&nbsp;&nbsp;&nbsp;If a PE that supports IPv6 does not receive a 'stack
capability'<br>
&nbsp;&nbsp;&nbsp;sub-TLV from the far-end PE in the initial label mapping
message, or<br>
&nbsp;&nbsp;&nbsp;one is received but it is set to a reserved value, the PE
MUST send<br>
&nbsp;&nbsp;&nbsp;an unsolicited release for the PW label with the LDP stat=
us
code<br>
&nbsp;&nbsp;&nbsp;meaning ''IP Address type mismatch'' (Status Code
0x0000004A).<br>
&nbsp;&nbsp;&nbsp;....<br>
&lt;Comment&gt;<br>
<br>
There is a need to consider the following case on IPV6 Capability negotiati=
on.<br>
<br>
Let's take some sequence of events in IP L2 PW setup between A and B.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A---------------------B<br>
<br>
A is configured with IPV4 only initially.<br>
B supports both IPV6 + IPv4.<br>
<br>
1. A sends initial label mapping L1 for IPV4 PW setup to B.<br>
&nbsp;&nbsp;&nbsp;L1 is waiting in B to get processed.<br>
2. Now we configured ipv6 capability in A. So A needs<br>
&nbsp;&nbsp;&nbsp;to do re-mapping. A sends label withdraw W1 first and<br>
&nbsp;&nbsp;&nbsp;then awaits for label release from B to re-advertise<br>
&nbsp;&nbsp;&nbsp;with IPV4 + IPV6 capability. So label withdraw W1 is<br>
&nbsp;&nbsp;&nbsp;in queue after the initial label Map L1 at B.<br>
3. Now B processes the initial label map L1 from A. It<br>
&nbsp;&nbsp;&nbsp;responds with unsolicited &quot;release&quot; R1 to A wit=
h
status<br>
&nbsp;&nbsp;&nbsp;code S1 =3D &quot;IP Address Type Mismatch&quot; since B
supports<br>
&nbsp;&nbsp;&nbsp;IPV4 + IPV6.<br>
4. Now A processes R1 and thinks it's the Release to withdraw<br>
&nbsp;&nbsp;&nbsp;W1 that A is waiting for. So it advertises L2 to B - the<=
br>
&nbsp;&nbsp;&nbsp;new Label mapping with IPV4 + IPV6.<br>
5. B processes W1 now and responds back with regular Release R2.<br>
6. A thinks that its label map L2 is being released by R2 -<br>
&nbsp;&nbsp;&nbsp;unsolicited release. <br>
7. B processes L2 and is happy with it.<br>
<br>
At the end of this re-negotiation, the PW would never be operationally up a=
t<br>
A but would be fine at B. Both ends are out of sync due to race conditions.=
<br>
<br>
So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d<br>
withdraw W1 with a new status code S2 =3D &quot;Wrong IP Address Type&quot;=
 (e.g)
when<br>
it changes from IPV4 to IPV6 (but not vice versa). When B processes label<b=
r>
withdraw with status Code S2, no release should be sent as response and B<b=
r>
should continue to wait for next control message from A.<br>
<br>
We do similar procedures with cBit re-negotiation. Please refer to section<=
br>
6.2 in RFC 4447 on usage of &quot;Wrong C-bit&quot;.<br>
<br>
Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-1=
3<br>
as well.<br>
<br>
&lt;/Comment&gt;<br>
<br>
<br>
[himanshu] I understand your scenario. It seems that if label TLV is used f=
or<br>
withdraw/release, label itself could be used to co-ordinate the release msg=
.<br>
Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid=
<br>
the race condition. I would like Mathew Bocci to comment on this too. Could=
<br>
you send him an internal mail to draw his attention. <br>
<br>
</span></font><b><font size=3D2 color=3Dblue face=3DAyuthaya><span style=3D=
'font-size:
10.0pt;font-family:Ayuthaya;color:blue;font-weight:bold'>[Pranjal]</span></=
font></b><font
size=3D2 color=3Dnavy face=3DAyuthaya><span style=3D'font-size:10.0pt;font-=
family:Ayuthaya;
color:navy'> </span></font><b><font size=3D2 color=3Dblue face=3DAyuthaya><=
span
style=3D'font-size:10.0pt;font-family:Ayuthaya;color:blue;font-weight:bold'=
>No really.
We can&#8217;t use</span></font></b><b><font size=3D1 color=3Dblue face=3DA=
yuthaya><span
style=3D'font-size:9.0pt;font-family:Ayuthaya;color:blue;font-weight:bold'>=
 </span></font></b><b><font
size=3D2 color=3Dblue face=3DAyuthaya><span style=3D'font-size:10.0pt;font-=
family:Ayuthaya;
color:blue;font-weight:bold'>label TLV as reliable method for withdraw/<br>
releases. If we refer to section 3.5.10 and 3.5.11 in RFC 5036, label TLV i=
s <br>
OPTIONAL in LDP label withdraw/release messages. Sure, I would bring this<b=
r>
into Mathew&#8217;s attention.</span></font></b><font size=3D1 color=3Dblue
face=3DAyuthaya><span style=3D'font-size:9.0pt;font-family:Ayuthaya;color:b=
lue'><br>
</span></font><font size=3D1 face=3DAyuthaya><span style=3D'font-size:9.0pt=
;
font-family:Ayuthaya'><br>
Section 7.3 Signaling Advertisement Processing<br>
<br>
A PE should process a received [PWE3-CONTROL] advertisement with PW- type o=
f IP
Layer2 transport for IPLS as follows,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Verify the IPLS VPN
membership by matching the VPN-Id<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;signaled in the=
 AGI
field or the PW-ID field with all the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;VPN-Ids configu=
red
in the PE. Discard and release the PW<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;label if VPN-Id=
 is
not found.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Program the Forwarding
Information Base (FIB) such that when<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a unicast IP pa=
cket
is received from an AC with its<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;destination MAC
address matching the advertised MAC address,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the packet is
forwarded out over the tunnel to the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;advertising PE =
with
the advertised PW-label as the inner<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;label.<br>
&nbsp;&nbsp;<br>
&lt;Comment&gt;<br>
<br>
In section 6.1 we have described that there would be one PW (either P2MP or=
<br>
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that w=
e<br>
are signaling P2P PW per CE with FEC128 to receive unicast traffic and ther=
e<br>
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS
membership with FEC128 Pwid. If we need to advertise multiple CEs from same
site over same LDP signaling session, each with different labels then PWid<=
br>
(VPN-ID) is not unique differentiator at receiver. It needs to be explained=
<br>
in detail on how the PW setup would take place per CE using FEC128. For FEC=
129
different AC-ID can be used for each CE but with common AGI (=3D VPN-ID) to=
 associate
them to same IPLS instance at receivers.<br>
<br>
&lt;/Comment&gt;<br>
<br>
<br>
[himanshu] This is a similar comment as LiZhong from ZTE. Hope you have
followed that discussions.<br>
In a nutshell, PE must augment MAC address to PW-FEC and treat it as a uniq=
ue
entity and apply<br>
label operations (mapping/withdraw/FIB programming, etc) accordingly. Same
comment applies to FEC129,<br>
because note that multiple CEs can exist on a single AC.<br>
<br>
<font color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></sp=
an></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 color=
=3Dblue
face=3D"Device Font 12cpi"><span style=3D'font-size:10.0pt;font-family:"Dev=
ice Font 12cpi";
color:blue;font-weight:bold'>[Pranjal] Yes, I am following your exchanges w=
ith
Lizhong. But still I was not <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; able to make it work
from an implementation perspective. If we would <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; want to augment the
PW-FEC &#8220;as is&#8221; with MAC address and apply label <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operations then we n=
eed
to define a new FEC type (e.g FEC128/129 + MAC). <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Here, IPLS VPN-ID is=
 NOT
the FEC, but the unidirectional PW used in IPLS <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is. Having a new FEC
type makes existing PW/L2VPN much cleaner. Existing <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementations woul=
d
consider one label from a peer against a PW (which <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is a FEC as per RFC =
4447).
<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 color=
=3Dblue
face=3D"Device Font 12cpi"><span style=3D'font-size:10.0pt;font-family:"Dev=
ice Font 12cpi";
color:blue;font-weight:bold'><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In IPLS, the intent =
is
to have the ability to associate VPN membership <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (thru common FEC
128/FEC129) but also have unidirectional PWs per CE MAC <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; address. As an examp=
le, we
do the same with FEC129 based LDP VPLS with BGP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;Autodiscovery. The A=
GI (which
is part of FEC129 but doesn&#8217;t define a <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specific PW) matches=
 the
VPLS ID&nbsp; (VPN membership) even though FEC(AGI + <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SAII + TAII) s of ea=
ch PWs
are different. In similar note IPLS is a service <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that needs to build
undirectional PW (FEC) infrastructure using a common <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; denominator as VPN-I=
D.<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 color=
=3Dblue
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:blue;
font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 color=
=3Dblue
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:blue;
font-weight:bold'>&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></b></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D1 face=3DA=
yuthaya><span
style=3D'font-size:9.0pt;font-family:Ayuthaya'><br>
<br>
&nbsp;<br>
Thanks,<br>
Pranjal<br>
<br>
-----Original Message-----<br>
From: <a href=3D"l2vpn-bounces@ietf.org">l2vpn-bounces@ietf.org</a> [<a
href=3D"mailto:l2vpn-bounces@ietf.org">mailto:l2vpn-bounces@ietf.org</a>] O=
n
Behalf Of Shane Amante<br>
Sent: Monday, April 05, 2010 6:58 PM<br>
To: <a href=3D"l2vpn@ietf.org">l2vpn@ietf.org</a><br>
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<br>
<br>
Hi Everyone,<br>
<br>
This is to begin a (final) WG Last Call on:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09">http://tool=
s.ietf.org/html/draft-ietf-l2vpn-ipls-09</a><br>
<br>
If you have substantial technical comments or concerns, please share them w=
ith
the list. &nbsp;If you have editorial comments, please share them directly =
with
the authors and co-chairs.<br>
<br>
So far, we have the following folks signed up for a thorough review and
comments:<br>
- Andy <st1:country-region w:st=3D"on"><st1:place w:st=3D"on">Malis</st1:pl=
ace></st1:country-region><br>
- Nick DelRegno<br>
- Pranjal Dutta<br>
However, we could use more people to conduct a review. &nbsp;If you have th=
e
time and/or inclination, please let the chairs know if you'll be conducting=
 a
review.<br>
<br>
The Last Call on this draft will also end on April 23.<br>
<br>
Thanks,<br>
<br>
Giles &amp; Shane</span></font><b><font size=3D2 color=3Dblue face=3DAyutha=
ya><span
style=3D'font-size:10.0pt;font-family:Ayuthaya;color:blue;font-weight:bold'=
><o:p></o:p></span></font></b></p>

</div>

</body>

</html>

--_000_C584046466ED224CA92C1BC3313B963E09E06F293EINBANSXCHMBSA_--

From pranjal.dutta@alcatel-lucent.com  Tue Apr 27 20:04:37 2010
Return-Path: <pranjal.dutta@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 E5CB83A6A0F for <l2vpn@core3.amsl.com>; Tue, 27 Apr 2010 20:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.835,  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 zIv4f8V-ISrH for <l2vpn@core3.amsl.com>; Tue, 27 Apr 2010 20:04:28 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 796BB3A685B for <l2vpn@ietf.org>; Tue, 27 Apr 2010 20:04:27 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o3S33xYA013716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Apr 2010 22:04:01 -0500 (CDT)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o3S33wYk004170 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 28 Apr 2010 08:33:58 +0530
Received: from INBANSXCHMBSA3.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Wed, 28 Apr 2010 08:33:58 +0530
From: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>
To: Himanshu Shah <hshah@force10networks.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Wed, 28 Apr 2010 08:33:55 +0530
Subject: RE: WG Last Call:  draft-ietf-l2vpn-arp-mediation-13
Thread-Topic: WG Last Call:  draft-ietf-l2vpn-arp-mediation-13
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNBG3HAAADNZ5AA/6rxIAASmO9w
Message-ID: <C584046466ED224CA92C1BC3313B963E09E06F2940@INBANSXCHMBSA3.in.alcatel-lucent.com>
References: <7B6C5040-C103-4626-83F8-618331F68BCE@castlepoint.net> <C584046466ED224CA92C1BC3313B963E09DFEF6B04@INBANSXCHMBSA3.in.alcatel-lucent.com> <34F81DE93A7AA840A6A3B1187BAD5FC80379DE5769@EXCH-CLUSTER-10.force10networks.com>
In-Reply-To: <34F81DE93A7AA840A6A3B1187BAD5FC80379DE5769@EXCH-CLUSTER-10.force10networks.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_C584046466ED224CA92C1BC3313B963E09E06F2940INBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.31
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, 28 Apr 2010 03:04:38 -0000

--_000_C584046466ED224CA92C1BC3313B963E09E06F2940INBANSXCHMBSA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Himanshu,

            Thanks for the clarification. Please refer inline

In blue.



Thanks,

Pranjal



-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of H=
imanshu Shah
Sent: Tuesday, April 27, 2010 11:17 AM
To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-arp-mediation-13



Hi Pranjal -

Thanks for the review and the comments.

Comments in line..



/himanshu



-----Original Message-----

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of D=
utta, Pranjal K (Pranjal)

Sent: Thursday, April 22, 2010 11:59 AM

To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org

Subject: RE: WG Last Call: draft-ietf-l2vpn-arp-mediation-13



Sorry this was for arp-mediation draft. So please read it for other one

and NOT for ipls draft.



Shane : I have changed your subject line :-) in this thread.



-----Original Message-----

From: Dutta, Pranjal K (Pranjal)

Sent: Thursday, April 22, 2010 8:55 AM

To: 'Shane Amante'; l2vpn@ietf.org

Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09



Hello Authors and WG,



    Here are some of my review comments on this version of the I-D.



In Section 6.1 When to Signal an IPv4 address of a CE

     ....

     Similarly, if the PE detects that an IP address of a CE is no

     longer valid (by methods described above), the PE must re-

     advertise the PW FEC with null IP address to denote the

     withdrawal of IP address of the CE. The receiving PE then waits

     for notification of the remote IP address. During this period,

     propagation of unicast IPv4 traffic is suspended, but multicast

     IPv4 traffic can continue to flow between the AC and the

     pseudowire.

     ....

     <Comment>

     I think we need to expand a bit on "PE must re-advertise the

     PW FEC with null IP address". Section 6.2 also specifies LDP

     Notification message to reflect any change in CE address without

     re-mapping/re-advertising if label has been advertised already.

     Otherwise it's a bit ambiguous on whether to use label withdraw

     on moving from 'non-zero' CE address to 'zero' CE address or

     reflect the change with CE address change Notification Message.

    </Comment>



[Himanshu>]  Section 5 discusses the how CE discovery and PW

establishment procedures are decoupled. They need to be,

especially for multicast traffic to flow, which in turn aids in CE

discovery. Hence the 'label withdraw' and 'address withdraw' are

kept separate. The label withdraw would apply only when the

service is no longer configured or unfavorable to both parties.

The 'address withdraw' cases are described the draft.



[Pranjal] Yes, that's correctly explained in section 6.2. I was looking

          from an implementation angle and section 5 leaves some ambiguity.
          This was a minor editorial comment.




Section 7. IPV6 Capability Advertisement

   ....

   A PE that supports IPv6 on an IP PW MUST signal the stack capability

   sub-TLV in the initial label mapping message for the PW. The PE

   nodes compare the value advertised by the remote PE with the local

   configuration and only use a capability which is advertised by both.

   If a PE that supports IPv6 does not receive a 'stack capability'

   sub-TLV from the far-end PE in the initial label mapping message, or

   one is received but it is set to a reserved value, the PE MUST send

   an unsolicited release for the PW label with the LDP status code

   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).

   ....



<Comment>



There is a need to consider the following case on IPV6

Capability negotiation.



Let's take some sequence of events in IP L2 PW setup between

A and B.



     A---------------------B



A is configured with IPV4 only initially.

B supports both IPV6 + IPv4.



1. A sends initial label mapping L1 for IPV4 PW setup to B.

   L1 is waiting in B to get processed.

2. Now we configured ipv6 capability in A. So A needs

   to do re-mapping. A sends label withdraw W1 first and

   then awaits for label release from B to re-advertise

   with IPV4 + IPV6 capability. So label withdraw W1 is

   in queue after the initial label Map L1 at B.

3. Now B processes the initial label map L1 from A. It

   responds with unsolicited "release" R1 to A with status

   code S1 =3D "IP Address Type Mismatch" since B supports

   IPV4 + IPV6.

4. Now A processes R1 and thinks it's the Release to withdraw

   W1 that A is waiting for. So it advertises L2 to B - the

   new Label mapping with IPV4 + IPV6.

5. B processes W1 now and responds back with regular Release R2.

6. A thinks that its label map L2 is being released by R2 -

   unsolicited release.

7. B processes L2 and is happy with it.



At the end of this re-negotiation, the PW would never be operationally up a=
t A but would be fine at B. Both ends are out of sync due to race condition=
s.



So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) w=
hen it changes from IPV4 to IPV6 (but not vice versa). When B processes lab=
el withdraw with status Code S2, no release should be sent as response and =
B should continue to wait for next control message from A.



We do similar procedures with cBit re-negotiation. Please refer to section =
6.2 in RFC 4447 on usage of "Wrong C-bit".



Note that the same applies to Section 7.2 in draft-ietf-l2vpn-ipls-09 as we=
ll.

</Comment>



[Himanshu>]  Cut & Paste below from the response on ipls comment (for those=
 who may not have read IPLS mails)



[himanshu] "I understand your scenario. It seems that if label TLV is used =
for

withdraw/release, label itself could be used to co-ordinate the release msg=
.

Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid

the race condition. I would like Mathew Bocci to comment on this too. Could

you send him an internal mail to draw his attention."



[Pranjal] Please refer to response in IPLS thread.



Thanks,

Pranjal



-----Original Message-----

From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante

Sent: Monday, April 05, 2010 6:58 PM

To: l2vpn@ietf.org

Subject: WG Last Call: draft-ietf-l2vpn-ipls-09



Hi Everyone,



This is to begin a (final) WG Last Call on:

http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09



If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.



So far, we have the following folks signed up for a thorough review and com=
ments:

- Andy Malis

- Nick DelRegno

- Pranjal Dutta

However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.



The Last Call on this draft will also end on April 23.



Thanks,



Giles & Shane

--_000_C584046466ED224CA92C1BC3313B963E09E06F2940INBANSXCHMBSA_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:st1=3D"urn:schemas-microsoft-com:off=
ice:smarttags" 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 11 (filtered medium)">
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 31.3pt 1.0in 31.25pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Hi Himanshu,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thanks
for the clarification. Please refer inline<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>In <b><font color=3Dblue><span style=3D'color:blue;font-weight:bold=
'>blue.</span></font></b><o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Pranjal&nbsp;&nbsp; <o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>-----Original Message-----<br>
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of H=
imanshu
Shah<br>
Sent: Tuesday, April 27, 2010 11:17 AM<br>
To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org<br>
Subject: RE: WG Last Call: draft-ietf-l2vpn-arp-mediation-13</span></font><=
/p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Hi Pranjal - <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Thanks for the review and the comments.<o:p></o:p></span></font></p=
>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Comments in line..<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>/himanshu<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>-----Original Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Beh=
alf
Of Dutta, Pranjal K (Pranjal)<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Sent: Thursday, April 22, 2010 11:59 AM<o:p></o:p></span></font></p=
>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org<o:p></=
o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Subject: RE: WG Last Call: draft-ietf-l2vpn-arp-mediation-13<o:p></=
o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Sorry this was for arp-mediation draft. So please read it for other=
 one<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>and NOT for ipls draft. <o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Shane : I have changed your subject line :-) in this thread.<o:p></=
o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>-----Original Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>From: Dutta, Pranjal K (Pranjal) <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Sent: Thursday, April 22, 2010 8:55 AM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>To: 'Shane Amante'; l2vpn@ietf.org<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09<o:p></o:p></spa=
n></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Hello Authors and WG,<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp; Here are some of my review comments on this vers=
ion
of the I-D. <o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>In Section 6.1 When to Signal an IPv4 address of a CE<o:p></o:p></s=
pan></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; ....<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; Similarly, if the PE detects that an IP
address of a CE is no<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; longer valid (by methods described above),=
 the
PE must re-<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; advertise the PW FEC with null IP address =
to
denote the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; withdrawal of IP address of the CE. The
receiving PE then waits<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; for notification of the remote IP address.
During this period,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; propagation of unicast IPv4 traffic is
suspended, but multicast<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; IPv4 traffic can continue to flow between =
the
AC and the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; pseudowire.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; ....<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; &lt;Comment&gt; <o:p></o:p></span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; I think we need to expand a bit on &quot;P=
E
must re-advertise the <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; PW FEC with null IP address&quot;. Section=
 6.2
also specifies LDP<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; Notification message to reflect any change=
 in
CE address without <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; re-mapping/re-advertising if label has bee=
n
advertised already.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; Otherwise it's a bit ambiguous on whether =
to use
label withdraw <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; on moving from 'non-zero' CE address to 'z=
ero'
CE address or&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; reflect the change with CE address change
Notification Message.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp; &lt;/Comment&gt;<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>[Himanshu&gt;]&nbsp; Section 5 discusses the how CE discovery and P=
W <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>establishment procedures are decoupled. They need to be, <o:p></o:p=
></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>especially for multicast traffic to flow, which in turn aids in CE<=
o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>discovery. Hence the 'label withdraw' and 'address withdraw' are<o:=
p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>kept separate. The label withdraw would apply only when the <o:p></=
o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>service is no longer configured or unfavorable to both parties.<o:p=
></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>The 'address withdraw' cases are described the draft.<o:p></o:p></s=
pan></font></p>

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

<p class=3DMsoPlainText><b><font size=3D2 color=3Dblue face=3D"Courier New"=
><span
style=3D'font-size:10.0pt;color:blue;font-weight:bold'>[Pranjal] Yes, that&=
#8217;s
correctly explained in section 6.2. I was looking<o:p></o:p></span></font><=
/b></p>

<p class=3DMsoPlainText><b><font size=3D2 color=3Dblack face=3D"Courier New=
"><span
style=3D'font-size:10.0pt;color:black;font-weight:bold'>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><font color=3Dblue><span style=3D'color:blue'>from an impleme=
ntation
angle and section 5 leaves some ambiguity.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;This was a minor edi=
torial
comment.<br>
&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></b></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Section 7. IPV6 Capability Advertisement<o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; ....<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; A PE that supports IPv6 on an IP PW MUST signal the st=
ack
capability<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; sub-TLV in the initial label mapping message for the P=
W.
The PE<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; nodes compare the value advertised by the remote PE wi=
th
the local<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; configuration and only use a capability which is
advertised by both.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; If a PE that supports IPv6 does not receive a 'stack
capability'<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; sub-TLV from the far-end PE in the initial label mappi=
ng
message, or<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; one is received but it is set to a reserved value, the=
 PE
MUST send<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; an unsolicited release for the PW label with the LDP
status code<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; meaning ''IP Address type mismatch'' (Status Code
0x0000004A).<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; ....<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&lt;Comment&gt;<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>There is a need to consider the following case on IPV6 <o:p></o:p><=
/span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Capability negotiation.<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Let's take some sequence of events in IP L2 PW setup between <o:p><=
/o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>A and B.<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; A---------------------B<o:p></o:p></span><=
/font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>A is configured with IPV4 only initially.<o:p></o:p></span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>B supports both IPV6 + IPv4.<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>1. A sends initial label mapping L1 for IPV4 PW setup to B.<o:p></o=
:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; L1 is waiting in B to get processed.<o:p></o:p></span>=
</font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>2. Now we configured ipv6 capability in A. So A needs <o:p></o:p></=
span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; to do re-mapping. A sends label withdraw W1 first and =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; then awaits for label release from B to re-advertise<o=
:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; with IPV4 + IPV6 capability. So label withdraw W1 is <=
o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; in queue after the initial label Map L1 at B.<o:p></o:=
p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>3. Now B processes the initial label map L1 from A. It <o:p></o:p><=
/span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; responds with unsolicited &quot;release&quot; R1 to A =
with
status <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; code S1 =3D &quot;IP Address Type Mismatch&quot; since=
 B
supports <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; IPV4 + IPV6.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>4. Now A processes R1 and thinks it's the Release to withdraw <o:p>=
</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; W1 that A is waiting for. So it advertises L2 to B - t=
he <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; new Label mapping with IPV4 + IPV6.<o:p></o:p></span><=
/font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>5. B processes W1 now and responds back with regular Release R2.<o:=
p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>6. A thinks that its label map L2 is being released by R2 - <o:p></=
o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&nbsp;&nbsp; unsolicited release.&nbsp; <o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>7. B processes L2 and is happy with it.<o:p></o:p></span></font></p=
>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>At the end of this re-negotiation, the PW would never be operationa=
lly
up at A but would be fine at B. Both ends are out of sync due to race
conditions.<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>So we can't overlap releases R1 and R2 from B. The solution is for =
A to
send withdraw W1 with a new status code S2 =3D &quot;Wrong IP Address Type&=
quot;
(e.g) when it changes from IPV4 to IPV6 (but not vice versa). When B proces=
ses
label withdraw with status Code S2, no release should be sent as response a=
nd B
should continue to wait for next control message from A.<o:p></o:p></span><=
/font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>We do similar procedures with cBit re-negotiation. Please refer to
section 6.2 in RFC 4447 on usage of &quot;Wrong C-bit&quot;.<o:p></o:p></sp=
an></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Note that the same applies to Section 7.2 in draft-ietf-l2vpn-ipls-=
09
as well.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>&lt;/Comment&gt;<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>[Himanshu&gt;]&nbsp; Cut &amp; Paste below from the response on ipl=
s
comment (for those who may not have read IPLS mails)<o:p></o:p></span></fon=
t></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>[himanshu] &quot;I understand your scenario. It seems that if label=
 TLV
is used for<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>withdraw/release, label itself could be used to co-ordinate the rel=
ease
msg.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Anyway, the method you note as describe in 6.2 of 4447 can be used =
to
avoid<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>the race condition. I would like Mathew Bocci to comment on this to=
o.
Could<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>you send him an internal mail to draw his attention.&quot;<o:p></o:=
p></span></font></p>

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

<p class=3DMsoPlainText><b><font size=3D2 color=3Dblue face=3D"Courier New"=
><span
style=3D'font-size:10.0pt;color:blue;font-weight:bold'>[Pranjal] Please ref=
er to
response in IPLS thread.<o:p></o:p></span></font></b></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier New"><=
span
style=3D'font-size:10.0pt;color:black'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Pranjal<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>-----Original Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Beh=
alf
Of Shane Amante<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Sent: Monday, April 05, 2010 6:58 PM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>To: l2vpn@ietf.org<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Subject: WG Last Call: draft-ietf-l2vpn-ipls-09<o:p></o:p></span></=
font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Hi Everyone,<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>This is to begin a (final) WG Last Call on:<o:p></o:p></span></font=
></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09<o:p></o:p></spa=
n></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>If you have substantial technical comments or concerns, please shar=
e
them with the list.&nbsp; If you have editorial comments, please share them
directly with the authors and co-chairs.<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>So far, we have the following folks signed up for a thorough review=
 and
comments:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>- Andy <st1:country-region w:st=3D"on"><st1:place w:st=3D"on">Malis=
</st1:place></st1:country-region><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>- Nick DelRegno<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>- Pranjal Dutta<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>However, we could use more people to conduct a review.&nbsp; If you
have the time and/or inclination, please let the chairs know if you'll be
conducting a review.<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>The Last Call on this draft will also end on April 23.<o:p></o:p></=
span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Thanks,<o:p></o:p></span></font></p>

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

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span style=3D'=
font-size:
10.0pt'>Giles &amp; Shane<o:p></o:p></span></font></p>

</div>

</body>

</html>

--_000_C584046466ED224CA92C1BC3313B963E09E06F2940INBANSXCHMBSA_--

From ju1738@att.com  Wed Apr 28 06:24:20 2010
Return-Path: <ju1738@att.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 6726C3A6991 for <l2vpn@core3.amsl.com>; Wed, 28 Apr 2010 06:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.734
X-Spam-Level: 
X-Spam-Status: No, score=-104.734 tagged_above=-999 required=5 tests=[AWL=-1.735, BAYES_50=0.001, J_BACKHAIR_44=1, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UA+CzfIn4LT6 for <l2vpn@core3.amsl.com>; Wed, 28 Apr 2010 06:24:17 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id E84B33A698D for <l2vpn@ietf.org>; Wed, 28 Apr 2010 06:18:17 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ju1738@att.com
X-Msg-Ref: server-6.tower-121.messagelabs.com!1272460683!32755529!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 24860 invoked from network); 28 Apr 2010 13:18:04 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-6.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Apr 2010 13:18:04 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3SDHlep018699; Wed, 28 Apr 2010 09:17:47 -0400
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com [144.155.43.107]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3SDHhuW018626; Wed, 28 Apr 2010 09:17:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Comments on draft-key-l2vpn-vpls-etree-02
Date: Wed, 28 Apr 2010 09:17:59 -0400
Message-ID: <1477DEAE19DD884CB004730D0FD77FD7041A8835@misout7msgusr7e.ugd.att.com>
In-Reply-To: <201004270310.o3R3AfRo007835@mail02.syd.optusnet.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-key-l2vpn-vpls-etree-02
Thread-Index: Acrlt0KfZ7YzCIXtTOuswhqPjzLNSwBG8oWw
References: <201004270310.o3R3AfRo007835@mail02.syd.optusnet.com.au>
From: "UTTARO, JAMES (ATTLABS)" <ju1738@att.com>
To: <raymond.key@ieee.org>
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, 28 Apr 2010 13:24:20 -0000

Raymond,

Comments In-Line..

Jim Uttaro

-----Original Message-----
From: Raymond Key [mailto:raymond.key@ieee.org]=20
Sent: Monday, April 26, 2010 11:11 PM
To: UTTARO, JAMES (ATTLABS)
Cc: Delregno, Christopher N (Nick DelRegno); l2vpn@ietf.org
Subject: RE: Comments on draft-key-l2vpn-vpls-etree-02

Hi Jim,

Thanks for your questions.

I have attempted to address these in section 4.3 in the draft -=20
Additional Action in Data Forwarding=20
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-4.3)

a) If Leafs are on the same PE how will the CW function? Will we need to
rely=20
on some other mechanism to prevent Leaf<>Leaf traffic on the same PE ?

[RK] Leaf AC -> Leaf AC Same PE : Rule 6 in Table 1
[Jim U>] This rule does not specify how the decision is made to drop. So
we have to have two mechanisms one if traffic came over a PW from a
remote PE ( CW ) and another if the traffic came from a leaf that is on
the same PE as the Leaf that originated the traffic ( ? ). The solution
is not complete if we need two mechanisms.. As a SP we want
specifications that are the same.

[RK] When both ingress AC and egress AC are on the same PE, PW is not=20
involved and hence CW is not applicable.
[Jim U>] But that forces a different solution.. If not a PW then a PW
semantic for intra-PE traffic between two ACs..=20

b) Leaf->Root traffic on the same PE? We don't want the Root to simply
forward=20
the traffic directly to another Leaf either on the PE or via a PW to a
remote PE..=20
How is this accomplished?

[RK] Leaf AC -> Root AC Same PE : Rule 1 in Table 1

[RK] Root AC -> Leaf AC Same PE : Rule 5 in Table 1

[RK] Root AC -> Leaf AC Remote PE
          Ingress PE (Root AC -> PW) : Rule 2 and Rule 3 in Table 1
          Egress PE (PW -> Leaf AC) : Rule 7 and Rule 8 in Table 1

[Jim U>] I guess I do not understand the table.. Referring to the
figure.. Assume ingress traffic from Leaf AC arrives on PE. The intra PE
traffic is forwarded to the Root AC ( VSI 1-R ). There is no PW semantic
for this traffic so it appears as if it is native ethernet traffic with
the same semantic as an AC.  At this point the traffic in that context
is sent out to all interfaces both PWs and other ACs possibly homed into
( VSI 1-R ). This would cause Leaf<->Leaf traffic as Leaf PE1 ( VSI 1-L
) would receive the traffic from the PE ( VSI 1-R ) that is not really
the customer's root traffic..

Leaf AC ( VSI 1-L )-------
                         |
                         |
Root AC ( VSI 1-R )-----PE-------------PE1--------Leaf ( VSI 1-L )

Have a read on the section 4.3 and see if it works.

Thanks,
Raymond


> UTTARO, JAMES (ATTLABS) <ju1738@att.com> wrote:
>=20
> I guess  am still a bit confused as to how this would work when there
> are leafs and roots on the same PE..
>=20
> a) If Leafs are on the same PE how will the CW function? Will we need
to
> rely on some other mechanism to prevent Leaf<>Leaf traffic on the same
> PE ?
>=20
> b) Leaf->Root traffic on the same PE? We don't want the Root to simply
> forward the traffic directly to another Leaf either on the PE or via a
> PW to a remote PE.. How is this accomplished?
>=20
> Comments In-Line..
>=20
> Jim Uttaro
>=20
> -----Original Message-----
> From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf
> Of Raymond Key
> Sent: Friday, April 23, 2010 9:39 PM
> To: Delregno, Christopher N (Nick DelRegno)
> Cc: l2vpn@ietf.org
> Subject: Comments on draft-key-l2vpn-vpls-etree-02
>=20
> Hi Nick,
>=20
> Thanks for your comment.
>=20
> Quote from your email, "However, if we are relying on CW to indicate
> leaf/root and the targeted PE doesn't support CW, then the ETREE model
> breaks as I can no longer determine leaf/root and drop/forward traffic
> accordingly."
>=20
> There may be some confusion here. When the targeted PE doesn't support

> CW, it also implies the targeted PE doesn't support the extension=20
> specified in this draft (see section 4.2, "A PE MUST be capable of=20
> sending and receiving the Control Word on Ethernet PW") and hence the=20
> targeted PE has only Root ACs. This is a backward compatibility=20
> scenario and does not result in any problem.
>=20
> [Jim U>] From an SP perspective this approach represents a major
> operational/provisioning challenge.. We would now need to track the
set
> of PEs that are candidates for Roots ( No CW Capable ), Roots and
Leafs,
> Leafs only. We cannot easily go back and change our homing rules. This
> would also impact the provisonable footprint.
>=20
> Backward compatibility issues are discussed in section 5 in the draft.

> (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5)
> Some paragraphs are extracted below.
>=20
> (5.3. Additional Action in Data Forwarding)
>=20
> For backward compatibility reason, a PE not supporting the extension
> specified in this document can participate in an E-Tree construct,
> but only Root ACs can be connected to such PE.
>=20
> Lack of Control Word L-bit per-payload signaling between a PE
> supporting the extension specified in this document and a PE not
> supporting such extension does not result in any problem.
>=20
> (5.3.1 Ingress PE Support the Extension but Egress PE Not)
>=20
> If Control Word is not used on the Ethernet PW, there will be no CW
> L-bit. The egress PE will forward the frame as per current standard.
> This is correct as only Root ACs exist on a PE not supporting the
> extension specified in this document.  A Root AC can receive from any
> other ACs.
>=20
> By the way I recently posted a draft "Requirements for MEF E-Tree=20
> Support in VPLS"=20
> (http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-reqt-00)
> trying to start a "solution-neutral" discussion on whether there is a=20
> valid requirement to enhance VPLS or not. Any comments on that draft?
>=20
> Thanks,
> Raymond=20
>=20
>=20
> > Delregno, Christopher N (Nick DelRegno) <nick.delregno@verizon.com>
> wrote:
> >=20
> > Raymond:
> >=20
> > From a purely T-LDP perspective, I agree.  However, if we are
relying
> on
> > CW to indicate leaf/root and the targeted PE doesn't support CW,
then
> > the ETREE model breaks as I can no longer determine leaf/root and
> > drop/forward traffic accordingly.  As such, the implementation
> behavior
> > when using CW to indicate Leaf/Root MUST NOT allow the CW preference
> > mismatch to result in an active PW.
> >=20
> > Thanks,
> > Nick
> >=20
> > -----Original Message-----
> > From: Raymond Key [mailto:raymond.key@ieee.org]=20
> > Sent: Wednesday, April 21, 2010 4:55 PM
> > To: Delregno, Christopher N (Nick DelRegno)
> > Cc: l2vpn@ietf.org
> > Subject: Re: Updated minutes from IETF 77
> >=20
> > Hi Nic,
> >=20
> > I go through the recently published IETF77 L2VPN minutes and would
> like
> > to follow up on one of your comments.
> >=20
> > Extract from minutes under
> > 10) Extension to VPLS for E-Tree
> > "Nic: This requires a control word, so a box has to support a
control
> > word.=20
> > PW mustn't come up if a CW is not supported."
> >=20
> > There may be some confusion here. When one PE does not support
control
> > word, PW can still come up.
> >=20
> > Refer to Section 5.2. Control Word (under Backward Compatibility)
For
> > backward compatibility reason, use of Control Word on Ethernet PW is
> not
> > mandatory. If the PE on the other end prefers not to use Control
Word
> or
> > does not support Control Word (which implies such PE does not
support
> > the extension specified in this document), then Control Word will
not
> be
> > used on the Ethernet PW.
> > Refer to Appendix A for different Control Word scenarios.
> >
(http://tools.ietf.org/html/draft-key-l2vpn-vpls-etree-02#section-5.2)
> >=20
> > Regards,
> > Raymond Key
> >=20
> >=20
> > > Giles Heron <giles.heron@gmail.com> wrote:
> > >=20
> > > Ok - so it'd help if I actually put some content in my email.
> > >=20
> > > As Simon Delord helpfully pointed out the other day I missed the=20
> > > second half of the meeting out when I posted these.
> > >=20
> > > I've now updated the online minutes:
> > >=20
> > > http://www.ietf.org/proceedings/10mar/minutes/l2vpn.txt
> > >=20
> > > Giles

From matthew.bocci@alcatel-lucent.com  Fri Apr 30 04:25:38 2010
Return-Path: <matthew.bocci@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 AC19628C23E for <l2vpn@core3.amsl.com>; Fri, 30 Apr 2010 04:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.755
X-Spam-Level: 
X-Spam-Status: No, score=-0.755 tagged_above=-999 required=5 tests=[AWL=-2.591, BAYES_50=0.001, HELO_EQ_FR=0.35, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9MgcOOJGuVC for <l2vpn@core3.amsl.com>; Fri, 30 Apr 2010 04:25:27 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id E35DE28C1F8 for <l2vpn@ietf.org>; Fri, 30 Apr 2010 04:24:25 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o3UBNKn6011049 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 30 Apr 2010 13:23:43 +0200
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.36]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Fri, 30 Apr 2010 13:23:24 +0200
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>, Himanshu Shah <hshah@force10networks.com>, Shane Amante <shane@castlepoint.net>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Date: Fri, 30 Apr 2010 13:23:22 +0200
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Topic: WG Last Call: draft-ietf-l2vpn-ipls-09
Thread-Index: AcrVLLO4sjnrt0WPSVqN9d+raMYzYQNCB0egAN5+5b0AMnY/IAB3ml6A
Message-ID: <030F37126795E34DB4796609C4FEAA4A127EA83834@FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com>
References: <C584046466ED224CA92C1BC3313B963E09DFEF6B09@INBANSXCHMBSA3.in.alcatel-lucent.com> <C7FBBFD1.3846%hshah@force10networks.com> <C584046466ED224CA92C1BC3313B963E09E06F293E@INBANSXCHMBSA3.in.alcatel-lucent.com>
In-Reply-To: <C584046466ED224CA92C1BC3313B963E09E06F293E@INBANSXCHMBSA3.in.alcatel-lucent.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_030F37126795E34DB4796609C4FEAA4A127EA83834FRMRSSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
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, 30 Apr 2010 11:25:38 -0000

--_000_030F37126795E34DB4796609C4FEAA4A127EA83834FRMRSSXCHMBSA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Himanshu, Pranjal,

I think it makes sense to use the same procedures that are described in Sec=
 6.2 of RFC4447. We would need to get a new LDP status code point for this.
I'll send some draft text for comment to the list in the next few days.

Thanks

Matthew

________________________________
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of D=
utta, Pranjal K (Pranjal)
Sent: 28 April 2010 03:48
To: Himanshu Shah; Shane Amante; l2vpn@ietf.org
Subject: RE: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Himanshu,
                           Please refer my responses inline in blue.

Thanks,
Pranjal
________________________________
From: Himanshu Shah [mailto:hshah@force10networks.com]
Sent: Monday, April 26, 2010 7:10 PM
To: Dutta, Pranjal K (Pranjal); Shane Amante; l2vpn@ietf.org
Subject: Re: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Pranjal,
Thanks for your comments.

Response in line..

Regards,
himanshu

On 4/22/10 12:08 PM, "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lu=
cent.com> wrote:
Hello Authors and WG,

    Here are some of my review comments on this version of the I-D.

Section 7.2 IPV6 Capability advertisement.
   ....
   A PE that supports IPv6 on an IP PW MUST signal the stack capability
   sub-TLV in the initial label mapping message for the PW. The PE
   nodes compare the value advertised by the remote PE with the local
   configuration and only use a capability which is advertised by both.
   If a PE that supports IPv6 does not receive a 'stack capability'
   sub-TLV from the far-end PE in the initial label mapping message, or
   one is received but it is set to a reserved value, the PE MUST send
   an unsolicited release for the PW label with the LDP status code
   meaning ''IP Address type mismatch'' (Status Code 0x0000004A).
   ....
<Comment>

There is a need to consider the following case on IPV6 Capability negotiati=
on.

Let's take some sequence of events in IP L2 PW setup between A and B.

     A---------------------B

A is configured with IPV4 only initially.
B supports both IPV6 + IPv4.

1. A sends initial label mapping L1 for IPV4 PW setup to B.
   L1 is waiting in B to get processed.
2. Now we configured ipv6 capability in A. So A needs
   to do re-mapping. A sends label withdraw W1 first and
   then awaits for label release from B to re-advertise
   with IPV4 + IPV6 capability. So label withdraw W1 is
   in queue after the initial label Map L1 at B.
3. Now B processes the initial label map L1 from A. It
   responds with unsolicited "release" R1 to A with status
   code S1 =3D "IP Address Type Mismatch" since B supports
   IPV4 + IPV6.
4. Now A processes R1 and thinks it's the Release to withdraw
   W1 that A is waiting for. So it advertises L2 to B - the
   new Label mapping with IPV4 + IPV6.
5. B processes W1 now and responds back with regular Release R2.
6. A thinks that its label map L2 is being released by R2 -
   unsolicited release.
7. B processes L2 and is happy with it.

At the end of this re-negotiation, the PW would never be operationally up a=
t
A but would be fine at B. Both ends are out of sync due to race conditions.

So we can't overlap releases R1 and R2 from B. The solution is for A to sen=
d
withdraw W1 with a new status code S2 =3D "Wrong IP Address Type" (e.g) whe=
n
it changes from IPV4 to IPV6 (but not vice versa). When B processes label
withdraw with status Code S2, no release should be sent as response and B
should continue to wait for next control message from A.

We do similar procedures with cBit re-negotiation. Please refer to section
6.2 in RFC 4447 on usage of "Wrong C-bit".

Note that the same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-1=
3
as well.

</Comment>


[himanshu] I understand your scenario. It seems that if label TLV is used f=
or
withdraw/release, label itself could be used to co-ordinate the release msg=
.
Anyway, the method you note as describe in 6.2 of 4447 can be used to avoid
the race condition. I would like Mathew Bocci to comment on this too. Could
you send him an internal mail to draw his attention.

[Pranjal] No really. We can't use label TLV as reliable method for withdraw=
/
releases. If we refer to section 3.5.10 and 3.5.11 in RFC 5036, label TLV i=
s
OPTIONAL in LDP label withdraw/release messages. Sure, I would bring this
into Mathew's attention.

Section 7.3 Signaling Advertisement Processing

A PE should process a received [PWE3-CONTROL] advertisement with PW- type o=
f IP Layer2 transport for IPLS as follows,

        - Verify the IPLS VPN membership by matching the VPN-Id
          signaled in the AGI field or the PW-ID field with all the
          VPN-Ids configured in the PE. Discard and release the PW
          label if VPN-Id is not found.
        - Program the Forwarding Information Base (FIB) such that when
          a unicast IP packet is received from an AC with its
          destination MAC address matching the advertised MAC address,
          the packet is forwarded out over the tunnel to the
          advertising PE with the advertised PW-label as the inner
          label.

<Comment>

In section 6.1 we have described that there would be one PW (either P2MP or
MP2MP) associated exclusively with one CE in an IPLS site. Let's say that w=
e
are signaling P2P PW per CE with FEC128 to receive unicast traffic and ther=
e
are multiple local CEs in a site. [PWE-CONTROL] method would match IPLS mem=
bership with FEC128 Pwid. If we need to advertise multiple CEs from same si=
te over same LDP signaling session, each with different labels then PWid
(VPN-ID) is not unique differentiator at receiver. It needs to be explained
in detail on how the PW setup would take place per CE using FEC128. For FEC=
129 different AC-ID can be used for each CE but with common AGI (=3D VPN-ID=
) to associate them to same IPLS instance at receivers.

</Comment>


[himanshu] This is a similar comment as LiZhong from ZTE. Hope you have fol=
lowed that discussions.
In a nutshell, PE must augment MAC address to PW-FEC and treat it as a uniq=
ue entity and apply
label operations (mapping/withdraw/FIB programming, etc) accordingly. Same =
comment applies to FEC129,
because note that multiple CEs can exist on a single AC.

[Pranjal] Yes, I am following your exchanges with Lizhong. But still I was =
not
          able to make it work from an implementation perspective. If we wo=
uld
          want to augment the PW-FEC "as is" with MAC address and apply lab=
el
          operations then we need to define a new FEC type (e.g FEC128/129 =
+ MAC).
          Here, IPLS VPN-ID is NOT the FEC, but the unidirectional PW used =
in IPLS
          is. Having a new FEC type makes existing PW/L2VPN much cleaner. E=
xisting
          implementations would consider one label from a peer against a PW=
 (which
          is a FEC as per RFC 4447).

          In IPLS, the intent is to have the ability to associate VPN membe=
rship
          (thru common FEC 128/FEC129) but also have unidirectional PWs per=
 CE MAC
          address. As an example, we do the same with FEC129 based LDP VPLS=
 with BGP
          Autodiscovery. The AGI (which is part of FEC129 but doesn't defin=
e a
          specific PW) matches the VPLS ID  (VPN membership) even though FE=
C(AGI +
          SAII + TAII) s of each PWs are different. In similar note IPLS is=
 a service
          that needs to build undirectional PW (FEC) infrastructure using a=
 common
          denominator as VPN-ID.





Thanks,
Pranjal

-----Original Message-----
From: l2vpn-bounces@ietf.org [mailto:l2vpn-bounces@ietf.org] On Behalf Of S=
hane Amante
Sent: Monday, April 05, 2010 6:58 PM
To: l2vpn@ietf.org
Subject: WG Last Call: draft-ietf-l2vpn-ipls-09

Hi Everyone,

This is to begin a (final) WG Last Call on:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09

If you have substantial technical comments or concerns, please share them w=
ith the list.  If you have editorial comments, please share them directly w=
ith the authors and co-chairs.

So far, we have the following folks signed up for a thorough review and com=
ments:
- Andy Malis
- Nick DelRegno
- Pranjal Dutta
However, we could use more people to conduct a review.  If you have the tim=
e and/or inclination, please let the chairs know if you'll be conducting a =
review.

The Last Call on this draft will also end on April 23.

Thanks,

Giles & Shane

--_000_030F37126795E34DB4796609C4FEAA4A127EA83834FRMRSSXCHMBSA_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Re: WG Last Call:=
 draft-ietf-l2vpn-ipls-09</TITLE>
<META content=3D"text/html; charset=3Dus-ascii" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18904"><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"country-region"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagTyp=
e><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagTyp=
e><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Device Font 12cpi;
}
@font-face {
	font-family: Ayuthaya;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt
}
LI.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
	MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	FONT-FAMILY: Arial; COLOR: navy; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US link=3Dblue vLink=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Himanshu, Pranjal,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>I think it makes sense to use the same procedures tha=
t are=20
described in Sec 6.2 of RFC4447. We would need to get a new LDP status code=
=20
point for this.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>I'll send some draft text for comment to the list in =
the next=20
few days.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Thanks</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D307541911-30042010><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Matthew</FONT></SPAN></DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> l2vpn-bounces@ietf.org=20
  [mailto:l2vpn-bounces@ietf.org] <B>On Behalf Of </B>Dutta, Pranjal K=20
  (Pranjal)<BR><B>Sent:</B> 28 April 2010 03:48<BR><B>To:</B> Himanshu Shah=
;=20
  Shane Amante; l2vpn@ietf.org<BR><B>Subject:</B> RE: WG Last Call:=20
  draft-ietf-l2vpn-ipls-09<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt">Hi=20
  Himanshu,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Please refer my responses inline in </SPAN></FONT><B><FONT color=3Dblue s=
ize=3D2=20
  face=3D"Device Font 12cpi"><SPAN=20
  style=3D"FONT-FAMILY: 'Device Font 12cpi'; COLOR: blue; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold">blue</SPAN></FONT></B><FONT=20
  color=3Dnavy size=3D2 face=3D"Device Font 12cpi"><SPAN=20
  style=3D"FONT-FAMILY: 'Device Font 12cpi'; COLOR: navy; FONT-SIZE: 10pt">=
.</SPAN></FONT><FONT=20
  color=3Dnavy size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"><o:p></o:p></S=
PAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt">Thanks,<o:p></=
o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt">Pranjal<o:p></=
o:p></SPAN></FONT></P>
  <DIV>
  <DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter><FONT =
size=3D3=20
  face=3D"Times New Roman"><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter SIZE=3D3 width=3D"100%">
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT size=3D2 face=3DTahoma><SPAN=20
  style=3D"FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; FONT-WEIGHT: bold">From:</=
SPAN></FONT></B><FONT=20
  size=3D2 face=3DTahoma><SPAN style=3D"FONT-FAMILY: Tahoma; FONT-SIZE: 10p=
t">=20
  Himanshu Shah [mailto:hshah@force10networks.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, April 26, 2010 7:10=
=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Dutta, Pranjal =
K=20
  (Pranjal); Shane Amante; l2vpn@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: WG Last Call:=20
  draft-ietf-l2vpn-ipls-09</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT size=3D3 face=3D"Times New Roman"><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><FONT size=3D1=20
  face=3DAyuthaya><SPAN style=3D"FONT-FAMILY: Ayuthaya; FONT-SIZE: 9pt">Hi=
=20
  Pranjal,<BR>Thanks for your comments.<BR><BR>Response in=20
  line..<BR><BR>Regards,<BR>himanshu<BR><BR>On 4/22/10 12:08 PM, "Dutta, Pr=
anjal=20
  K (Pranjal)" &lt;<A=20
  href=3D"pranjal.dutta@alcatel-lucent.com">pranjal.dutta@alcatel-lucent.co=
m</A>&gt;=20
  wrote:</SPAN></FONT><o:p></o:p></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><FONT size=3D1=20
  face=3DAyuthaya><SPAN style=3D"FONT-FAMILY: Ayuthaya; FONT-SIZE: 9pt">Hel=
lo=20
  Authors and WG,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;Here are some of my review=
=20
  comments on this version of the I-D.<BR>&nbsp;&nbsp;<BR>Section 7.2 IPV6=
=20
  Capability advertisement.<BR>&nbsp;&nbsp;&nbsp;....<BR>&nbsp;&nbsp;&nbsp;=
A PE=20
  that supports IPv6 on an IP PW MUST signal the stack=20
  capability<BR>&nbsp;&nbsp;&nbsp;sub-TLV in the initial label mapping mess=
age=20
  for the PW. The PE<BR>&nbsp;&nbsp;&nbsp;nodes compare the value advertise=
d by=20
  the remote PE with the local<BR>&nbsp;&nbsp;&nbsp;configuration and only =
use a=20
  capability which is advertised by both.<BR>&nbsp;&nbsp;&nbsp;If a PE that=
=20
  supports IPv6 does not receive a 'stack=20
  capability'<BR>&nbsp;&nbsp;&nbsp;sub-TLV from the far-end PE in the initi=
al=20
  label mapping message, or<BR>&nbsp;&nbsp;&nbsp;one is received but it is =
set=20
  to a reserved value, the PE MUST send<BR>&nbsp;&nbsp;&nbsp;an unsolicited=
=20
  release for the PW label with the LDP status code<BR>&nbsp;&nbsp;&nbsp;me=
aning=20
  ''IP Address type mismatch'' (Status Code=20
  0x0000004A).<BR>&nbsp;&nbsp;&nbsp;....<BR>&lt;Comment&gt;<BR><BR>There is=
 a=20
  need to consider the following case on IPV6 Capability=20
  negotiation.<BR><BR>Let's take some sequence of events in IP L2 PW setup=
=20
  between A and=20
  B.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A---------------------B<BR><BR>A =
is=20
  configured with IPV4 only initially.<BR>B supports both IPV6 + IPv4.<BR><=
BR>1.=20
  A sends initial label mapping L1 for IPV4 PW setup to=20
  B.<BR>&nbsp;&nbsp;&nbsp;L1 is waiting in B to get processed.<BR>2. Now we=
=20
  configured ipv6 capability in A. So A needs<BR>&nbsp;&nbsp;&nbsp;to do=20
  re-mapping. A sends label withdraw W1 first and<BR>&nbsp;&nbsp;&nbsp;then=
=20
  awaits for label release from B to re-advertise<BR>&nbsp;&nbsp;&nbsp;with=
 IPV4=20
  + IPV6 capability. So label withdraw W1 is<BR>&nbsp;&nbsp;&nbsp;in queue =
after=20
  the initial label Map L1 at B.<BR>3. Now B processes the initial label ma=
p L1=20
  from A. It<BR>&nbsp;&nbsp;&nbsp;responds with unsolicited "release" R1 to=
 A=20
  with status<BR>&nbsp;&nbsp;&nbsp;code S1 =3D "IP Address Type Mismatch" s=
ince B=20
  supports<BR>&nbsp;&nbsp;&nbsp;IPV4 + IPV6.<BR>4. Now A processes R1 and t=
hinks=20
  it's the Release to withdraw<BR>&nbsp;&nbsp;&nbsp;W1 that A is waiting fo=
r. So=20
  it advertises L2 to B - the<BR>&nbsp;&nbsp;&nbsp;new Label mapping with I=
PV4 +=20
  IPV6.<BR>5. B processes W1 now and responds back with regular Release=20
  R2.<BR>6. A thinks that its label map L2 is being released by R2=20
  -<BR>&nbsp;&nbsp;&nbsp;unsolicited release. <BR>7. B processes L2 and is =
happy=20
  with it.<BR><BR>At the end of this re-negotiation, the PW would never be=
=20
  operationally up at<BR>A but would be fine at B. Both ends are out of syn=
c due=20
  to race conditions.<BR><BR>So we can't overlap releases R1 and R2 from B.=
 The=20
  solution is for A to send<BR>withdraw W1 with a new status code S2 =3D "W=
rong IP=20
  Address Type" (e.g) when<BR>it changes from IPV4 to IPV6 (but not vice ve=
rsa).=20
  When B processes label<BR>withdraw with status Code S2, no release should=
 be=20
  sent as response and B<BR>should continue to wait for next control messag=
e=20
  from A.<BR><BR>We do similar procedures with cBit re-negotiation. Please =
refer=20
  to section<BR>6.2 in RFC 4447 on usage of "Wrong C-bit".<BR><BR>Note that=
 the=20
  same applies to Section 7 in draft-ietf-l2vpn-arp-mediation-13<BR>as=20
  well.<BR><BR>&lt;/Comment&gt;<BR><BR><BR>[himanshu] I understand your=20
  scenario. It seems that if label TLV is used for<BR>withdraw/release, lab=
el=20
  itself could be used to co-ordinate the release msg.<BR>Anyway, the metho=
d you=20
  note as describe in 6.2 of 4447 can be used to avoid<BR>the race conditio=
n. I=20
  would like Mathew Bocci to comment on this too. Could<BR>you send him an=
=20
  internal mail to draw his attention. <BR><BR></SPAN></FONT><B><FONT color=
=3Dblue=20
  size=3D2 face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: blue; FONT-SIZE: 10pt; FONT-WEIGHT=
: bold">[Pranjal]</SPAN></FONT></B><FONT=20
  color=3Dnavy size=3D2 face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: navy; FONT-SIZE: 10pt">=20
  </SPAN></FONT><B><FONT color=3Dblue size=3D2 face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: blue; FONT-SIZE: 10pt; FONT-WEIGHT=
: bold">No=20
  really. We can&#8217;t use</SPAN></FONT></B><B><FONT color=3Dblue size=3D=
1=20
  face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: blue; FONT-SIZE: 9pt; FONT-WEIGHT:=
 bold">=20
  </SPAN></FONT></B><B><FONT color=3Dblue size=3D2 face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: blue; FONT-SIZE: 10pt; FONT-WEIGHT=
: bold">label=20
  TLV as reliable method for withdraw/<BR>releases. If we refer to section=
=20
  3.5.10 and 3.5.11 in RFC 5036, label TLV is <BR>OPTIONAL in LDP label=20
  withdraw/release messages. Sure, I would bring this<BR>into Mathew&#8217;=
s=20
  attention.</SPAN></FONT></B><FONT color=3Dblue size=3D1 face=3DAyuthaya><=
SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: blue; FONT-SIZE: 9pt"><BR></SPAN><=
/FONT><FONT=20
  size=3D1 face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; FONT-SIZE: 9pt"><BR>Section 7.3 Signaling=
=20
  Advertisement Processing<BR><BR>A PE should process a received [PWE3-CONT=
ROL]=20
  advertisement with PW- type of IP Layer2 transport for IPLS as=20
  follows,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Verify =
the=20
  IPLS VPN membership by matching the=20
  VPN-Id<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sig=
naled=20
  in the AGI field or the PW-ID field with all=20
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;VPN-Id=
s=20
  configured in the PE. Discard and release the=20
  PW<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;label i=
f=20
  VPN-Id is not found.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-=
=20
  Program the Forwarding Information Base (FIB) such that=20
  when<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a uni=
cast=20
  IP packet is received from an AC with=20
  its<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;destin=
ation=20
  MAC address matching the advertised MAC=20
  address,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t=
he=20
  packet is forwarded out over the tunnel to=20
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;advert=
ising=20
  PE with the advertised PW-label as the=20
  inner<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;labe=
l.<BR>&nbsp;&nbsp;<BR>&lt;Comment&gt;<BR><BR>In=20
  section 6.1 we have described that there would be one PW (either P2MP=20
  or<BR>MP2MP) associated exclusively with one CE in an IPLS site. Let's sa=
y=20
  that we<BR>are signaling P2P PW per CE with FEC128 to receive unicast tra=
ffic=20
  and there<BR>are multiple local CEs in a site. [PWE-CONTROL] method would=
=20
  match IPLS membership with FEC128 Pwid. If we need to advertise multiple =
CEs=20
  from same site over same LDP signaling session, each with different label=
s=20
  then PWid<BR>(VPN-ID) is not unique differentiator at receiver. It needs =
to be=20
  explained<BR>in detail on how the PW setup would take place per CE using=
=20
  FEC128. For FEC129 different AC-ID can be used for each CE but with commo=
n AGI=20
  (=3D VPN-ID) to associate them to same IPLS instance at=20
  receivers.<BR><BR>&lt;/Comment&gt;<BR><BR><BR>[himanshu] This is a simila=
r=20
  comment as LiZhong from ZTE. Hope you have followed that discussions.<BR>=
In a=20
  nutshell, PE must augment MAC address to PW-FEC and treat it as a unique=
=20
  entity and apply<BR>label operations (mapping/withdraw/FIB programming, e=
tc)=20
  accordingly. Same comment applies to FEC129,<BR>because note that multipl=
e CEs=20
  can exist on a single AC.<BR><BR><FONT color=3Dnavy><SPAN=20
  style=3D"COLOR: navy"><o:p></o:p></SPAN></FONT></SPAN></FONT></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><FONT color=3Dblue =
size=3D2=20
  face=3D"Device Font 12cpi"><SPAN=20
  style=3D"FONT-FAMILY: 'Device Font 12cpi'; COLOR: blue; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold">[Pranjal]=20
  Yes, I am following your exchanges with Lizhong. But still I was not=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; able to make i=
t=20
  work from an implementation perspective. If we would=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; want to augmen=
t the=20
  PW-FEC &#8220;as is&#8221; with MAC address and apply label=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operations the=
n we=20
  need to define a new FEC type (e.g FEC128/129 + MAC).=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Here, IPLS VPN=
-ID=20
  is NOT the FEC, but the unidirectional PW used in IPLS=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is. Having a n=
ew=20
  FEC type makes existing PW/L2VPN much cleaner. Existing=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implementation=
s=20
  would consider one label from a peer against a PW (which=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is a FEC as pe=
r RFC=20
  4447). <o:p></o:p></SPAN></FONT></B></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><FONT color=3Dblue =
size=3D2=20
  face=3D"Device Font 12cpi"><SPAN=20
  style=3D"FONT-FAMILY: 'Device Font 12cpi'; COLOR: blue; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold"><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
  In IPLS, the intent is to have the ability to associate VPN membership=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (thru common F=
EC=20
  128/FEC129) but also have unidirectional PWs per CE MAC=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; address. As an=
=20
  example, we do the same with FEC129 based LDP VPLS with=20
  BGP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;Autodiscove=
ry.=20
  The AGI (which is part of FEC129 but doesn&#8217;t define a=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specific PW)=20
  matches the VPLS ID&nbsp; (VPN membership) even though FEC(AGI +=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SAII + TAII) s=
 of=20
  each PWs are different. In similar note IPLS is a service=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that needs to =
build=20
  undirectional PW (FEC) infrastructure using a common=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; denominator as=
=20
  VPN-ID.<o:p></o:p></SPAN></FONT></B></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><FONT color=3Dblue =
size=3D2=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: blue; FONT-SIZE: 10pt; FONT-WEIGHT: b=
old"><o:p>&nbsp;</o:p></SPAN></FONT></B></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><FONT color=3Dblue =
size=3D2=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: blue; FONT-SIZE: 10pt; FONT-WEIGHT: b=
old">&nbsp;&nbsp;&nbsp;=20
  <o:p></o:p></SPAN></FONT></B></P>
  <P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><FONT size=3D1=20
  face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; FONT-SIZE: 9pt"><BR><BR>&nbsp;<BR>Thanks,=
<BR>Pranjal<BR><BR>-----Original=20
  Message-----<BR>From: <A=20
  href=3D"l2vpn-bounces@ietf.org">l2vpn-bounces@ietf.org</A> [<A=20
  href=3D"mailto:l2vpn-bounces@ietf.org">mailto:l2vpn-bounces@ietf.org</A>]=
 On=20
  Behalf Of Shane Amante<BR>Sent: Monday, April 05, 2010 6:58 PM<BR>To: <A=
=20
  href=3D"l2vpn@ietf.org">l2vpn@ietf.org</A><BR>Subject: WG Last Call:=20
  draft-ietf-l2vpn-ipls-09<BR><BR>Hi Everyone,<BR><BR>This is to begin a (f=
inal)=20
  WG Last Call on:<BR><A=20
  href=3D"http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-09">http://tools=
.ietf.org/html/draft-ietf-l2vpn-ipls-09</A><BR><BR>If=20
  you have substantial technical comments or concerns, please share them wi=
th=20
  the list. &nbsp;If you have editorial comments, please share them directl=
y=20
  with the authors and co-chairs.<BR><BR>So far, we have the following folk=
s=20
  signed up for a thorough review and comments:<BR>- Andy <st1:country-regi=
on=20
  w:st=3D"on"><st1:place w:st=3D"on">Malis</st1:place></st1:country-region>=
<BR>-=20
  Nick DelRegno<BR>- Pranjal Dutta<BR>However, we could use more people to=
=20
  conduct a review. &nbsp;If you have the time and/or inclination, please l=
et=20
  the chairs know if you'll be conducting a review.<BR><BR>The Last Call on=
 this=20
  draft will also end on April 23.<BR><BR>Thanks,<BR><BR>Giles &amp;=20
  Shane</SPAN></FONT><B><FONT color=3Dblue size=3D2 face=3DAyuthaya><SPAN=20
  style=3D"FONT-FAMILY: Ayuthaya; COLOR: blue; FONT-SIZE: 10pt; FONT-WEIGHT=
: bold"><o:p></o:p></SPAN></FONT></B></P></DIV></BLOCKQUOTE></BODY></HTML>

--_000_030F37126795E34DB4796609C4FEAA4A127EA83834FRMRSSXCHMBSA_--
