From l2vpn-bounces@ietf.org Sun Dec 17 23:17:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gw9vP-0008CO-PB; Sun, 17 Dec 2006 23:16:27 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gw9vO-0008CE-1p for l2vpn@ietf.org; Sun, 17 Dec 2006 23:16:26 -0500 Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gw9vM-0004dJ-F5 for l2vpn@ietf.org; Sun, 17 Dec 2006 23:16:26 -0500 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JAG00H8TBTQ54@szxga03-in.huawei.com> for l2vpn@ietf.org; Mon, 18 Dec 2006 12:15:26 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JAG00IJRBTPUD@szxga03-in.huawei.com> for l2vpn@ietf.org; Mon, 18 Dec 2006 12:15:26 +0800 (CST) Received: from [127.0.0.1] ([10.111.98.160]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JAG00F5UBTJSY@szxml04-in.huawei.com> for l2vpn@ietf.org; Mon, 18 Dec 2006 12:15:25 +0800 (CST) Date: Mon, 18 Dec 2006 12:15:18 +0800 From: "Abhay D.S" To: l2vpn@ietf.org Message-id: <458615D6.1070807@acm.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_3PzYEWcct8WCW851bnOuwg)" User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: Query Regarding BGP-MPLS-VPLS Restart X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: abhayds@acm.org List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This is a multi-part message in MIME format. --Boundary_(ID_3PzYEWcct8WCW851bnOuwg) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT hi group, How does a Route Reflector with VPLS advertisement capability behave during a graceful re-start. What happens to VPLS allocations when RR undergoes re-start ?. Rgds, Abhay --Boundary_(ID_3PzYEWcct8WCW851bnOuwg) Content-type: text/x-vcard; charset=utf-8; name=abhayds.vcf Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=abhayds.vcf begin:vcard fn:Abhay Rao n:Rao;Abhay email;internet:abhayds@acm.org version:2.1 end:vcard --Boundary_(ID_3PzYEWcct8WCW851bnOuwg)-- From l2vpn-bounces@ietf.org Tue Dec 19 00:29:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwXWV-0003kF-4O; Tue, 19 Dec 2006 00:28:19 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwXWT-0003jp-3g for l2vpn@ietf.org; Tue, 19 Dec 2006 00:28:17 -0500 Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwXWR-0003nV-8c for l2vpn@ietf.org; Tue, 19 Dec 2006 00:28:17 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id kBJ5SD1Z052123; Mon, 18 Dec 2006 21:28:13 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id kBJ5SDB28030; Mon, 18 Dec 2006 21:28:13 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id kBJ5SBjK037503; Mon, 18 Dec 2006 21:28:13 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.12.8p1/8.12.3/Submit) with ESMTP id kBJ5S9n2037500; Mon, 18 Dec 2006 21:28:09 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Mon, 18 Dec 2006 21:28:09 -0800 (PST) From: Kireeti Kompella To: "Abhay D.S" In-Reply-To: <458615D6.1070807@acm.org> Message-ID: <20061218211624.C37477@kummer.juniper.net> References: <458615D6.1070807@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: l2vpn@ietf.org Subject: Re: Query Regarding BGP-MPLS-VPLS Restart X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org On Mon, 18 Dec 2006, Abhay D.S wrote: > hi group, > > How does a Route Reflector with VPLS advertisement capability > behave during a graceful re-start. > > What happens to VPLS allocations when RR undergoes re-start ?. To what VPLS allocations are you referring? > Rgds, > Abhay Kireeti. ------- From l2vpn-bounces@ietf.org Tue Dec 19 00:35:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwXd8-0006X7-LS; Tue, 19 Dec 2006 00:35:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwXd7-0006Ww-Jh for l2vpn@ietf.org; Tue, 19 Dec 2006 00:35:09 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwXd5-00054G-N8 for l2vpn@ietf.org; Tue, 19 Dec 2006 00:35:09 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JAI00BSZA547R@szxga01-in.huawei.com> for l2vpn@ietf.org; Tue, 19 Dec 2006 13:34:16 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JAI00B74A53S5@szxga01-in.huawei.com> for l2vpn@ietf.org; Tue, 19 Dec 2006 13:34:16 +0800 (CST) Received: from [127.0.0.1] ([10.111.98.160]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JAI002MJA4XIR@szxml04-in.huawei.com> for l2vpn@ietf.org; Tue, 19 Dec 2006 13:34:15 +0800 (CST) Date: Tue, 19 Dec 2006 13:34:08 +0800 From: "Abhay D.S" In-reply-to: <20061218211624.C37477@kummer.juniper.net> To: Kireeti Kompella Message-id: <458779D0.1030400@acm.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_pdlnx0WRCNlWemf5N2MeWw)" User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) References: <458615D6.1070807@acm.org> <20061218211624.C37477@kummer.juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: l2vpn@ietf.org Subject: Re: Query Regarding BGP-MPLS-VPLS Restart X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: abhayds@acm.org List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This is a multi-part message in MIME format. --Boundary_(ID_pdlnx0WRCNlWemf5N2MeWw) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT hi kireeti, In the mpls-bgp-restart-draft 4.3. Case 3 The following applies when the LSR does not set BGP next hop to self. In this case the LSR, when advertising its best route for a particular NLRI just uses the label that was received with that route. And if the route was received with no label, the LSR advertises the route with no label as well. Either way, the LSR does not allocate a label for that route. I think this condition the LSR is just an RR ?. Im not sure my assumption is correct . Thank you, Rgds, Abhay Kireeti Kompella wrote: > On Mon, 18 Dec 2006, Abhay D.S wrote: > >> hi group, >> >> How does a Route Reflector with VPLS advertisement capability >> behave during a graceful re-start. >> >> What happens to VPLS allocations when RR undergoes re-start ?. > > To what VPLS allocations are you referring? > >> Rgds, >> Abhay > > Kireeti. > ------- > > --Boundary_(ID_pdlnx0WRCNlWemf5N2MeWw) Content-type: text/x-vcard; charset=utf-8; name=abhayds.vcf Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=abhayds.vcf begin:vcard fn:Abhay Rao n:Rao;Abhay email;internet:abhayds@acm.org version:2.1 end:vcard --Boundary_(ID_pdlnx0WRCNlWemf5N2MeWw)-- From l2vpn-bounces@ietf.org Tue Dec 19 01:03:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwY4G-0001ro-F8; Tue, 19 Dec 2006 01:03:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwY4F-0001rf-I3 for l2vpn@ietf.org; Tue, 19 Dec 2006 01:03:11 -0500 Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwY4E-0000aA-6L for l2vpn@ietf.org; Tue, 19 Dec 2006 01:03:11 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id kBJ639X19198; Mon, 18 Dec 2006 22:03:09 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id kBJ634B32612; Mon, 18 Dec 2006 22:03:04 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id kBJ634jK037650; Mon, 18 Dec 2006 22:03:04 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.12.8p1/8.12.3/Submit) with ESMTP id kBJ634nU037647; Mon, 18 Dec 2006 22:03:04 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Mon, 18 Dec 2006 22:03:04 -0800 (PST) From: Kireeti Kompella To: "Abhay D.S" In-Reply-To: <458779D0.1030400@acm.org> Message-ID: <20061218215323.T37560@kummer.juniper.net> References: <458615D6.1070807@acm.org> <20061218211624.C37477@kummer.juniper.net> <458779D0.1030400@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: l2vpn@ietf.org Subject: Re: Query Regarding BGP-MPLS-VPLS Restart X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org On Tue, 19 Dec 2006, Abhay D.S wrote: > hi kireeti, > In the mpls-bgp-restart-draft > 4.3. Case 3 > > The following applies when the LSR does not set BGP next hop to self. > > In this case the LSR, when advertising its best route for a > particular NLRI just uses the label that was received with that > route. And if the route was received with no label, the LSR > advertises the route with no label as well. Either way, the LSR does > not allocate a label for that route. > > I think this condition the LSR is just an RR ?. Im not sure my assumption > is correct . An RR for VPLS would not set the BGP nexthop to self, so it would satisfy this condition. However, such an RR would not make any VPLS "allocations", if by that you mean labels. The RR (as per the quoted draft) must first re-acquire all the VPLS updates (including label blocks) from its neighbors. Once it does that successfully, the RR can then do path selection and advertise VPLS NLRIs to its neighbors *with the received label blocks*. The RR does not allocate new label blocks. HTH. > Thank you, > Rgds, > Abhay > > Kireeti Kompella wrote: >> On Mon, 18 Dec 2006, Abhay D.S wrote: >> >>> hi group, >>> >>> How does a Route Reflector with VPLS advertisement capability >>> behave during a graceful re-start. >>> >>> What happens to VPLS allocations when RR undergoes re-start ?. >> >> To what VPLS allocations are you referring? >> >>> Rgds, >>> Abhay >> >> Kireeti. >> ------- >> >> > Kireeti. ------- From l2vpn-bounces@ietf.org Tue Dec 19 01:09:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwYAD-0006AF-KT; Tue, 19 Dec 2006 01:09:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwYA8-00069D-Py for l2vpn@ietf.org; Tue, 19 Dec 2006 01:09:16 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwYA7-0001WM-5W for l2vpn@ietf.org; Tue, 19 Dec 2006 01:09:16 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JAI00BFYBM67R@szxga01-in.huawei.com> for l2vpn@ietf.org; Tue, 19 Dec 2006 14:06:07 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JAI00C8NBM6EM@szxga01-in.huawei.com> for l2vpn@ietf.org; Tue, 19 Dec 2006 14:06:06 +0800 (CST) Received: from [127.0.0.1] ([10.111.98.160]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JAI00CMEBM4SN@szxml03-in.huawei.com> for l2vpn@ietf.org; Tue, 19 Dec 2006 14:06:06 +0800 (CST) Date: Tue, 19 Dec 2006 14:06:04 +0800 From: "Abhay D.S" In-reply-to: <20061218215323.T37560@kummer.juniper.net> To: Kireeti Kompella Message-id: <4587814C.7080604@acm.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_IrJz6t/3Mg3ONCkUMJdynQ)" User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) References: <458615D6.1070807@acm.org> <20061218211624.C37477@kummer.juniper.net> <458779D0.1030400@acm.org> <20061218215323.T37560@kummer.juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: l2vpn@ietf.org Subject: Re: Query Regarding BGP-MPLS-VPLS Restart X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: abhayds@acm.org List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This is a multi-part message in MIME format. --Boundary_(ID_IrJz6t/3Mg3ONCkUMJdynQ) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT hi kireeti, Thanks, yes I agree RR does not allocate labels. Probably the draft could be modified to say that RR is the case. Rgds, Abhay Kireeti Kompella wrote: > On Tue, 19 Dec 2006, Abhay D.S wrote: > >> hi kireeti, >> In the mpls-bgp-restart-draft >> 4.3. Case 3 >> >> The following applies when the LSR does not set BGP next hop to self. >> >> In this case the LSR, when advertising its best route for a >> particular NLRI just uses the label that was received with that >> route. And if the route was received with no label, the LSR >> advertises the route with no label as well. Either way, the LSR does >> not allocate a label for that route. >> >> I think this condition the LSR is just an RR ?. Im not sure my >> assumption >> is correct . > > An RR for VPLS would not set the BGP nexthop to self, so it would > satisfy this condition. However, such an RR would not make any VPLS > "allocations", if by that you mean labels. The RR (as per the quoted > draft) must first re-acquire all the VPLS updates (including label > blocks) from its neighbors. Once it does that successfully, the RR > can then do path selection and advertise VPLS NLRIs to its neighbors > *with the received label blocks*. The RR does not allocate new label > blocks. > > HTH. > >> Thank you, >> Rgds, >> Abhay >> >> Kireeti Kompella wrote: >>> On Mon, 18 Dec 2006, Abhay D.S wrote: >>> >>>> hi group, >>>> >>>> How does a Route Reflector with VPLS advertisement capability >>>> behave during a graceful re-start. >>>> >>>> What happens to VPLS allocations when RR undergoes re-start ?. >>> >>> To what VPLS allocations are you referring? >>> >>>> Rgds, >>>> Abhay >>> >>> Kireeti. >>> ------- >>> >>> >> > > Kireeti. > ------- > > --Boundary_(ID_IrJz6t/3Mg3ONCkUMJdynQ) Content-type: text/x-vcard; charset=utf-8; name=abhayds.vcf Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=abhayds.vcf begin:vcard fn:Abhay Rao n:Rao;Abhay email;internet:abhayds@acm.org version:2.1 end:vcard --Boundary_(ID_IrJz6t/3Mg3ONCkUMJdynQ)-- From l2vpn-bounces@ietf.org Tue Dec 19 01:26:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwYQ0-0004Zy-HQ; Tue, 19 Dec 2006 01:25:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwYPz-0004Zp-2T for l2vpn@ietf.org; Tue, 19 Dec 2006 01:25:39 -0500 Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwYPx-00052t-Lk for l2vpn@ietf.org; Tue, 19 Dec 2006 01:25:39 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id kBJ6PbX19326; Mon, 18 Dec 2006 22:25:37 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id kBJ6PWB35710; Mon, 18 Dec 2006 22:25:32 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id kBJ6PWjK037782; Mon, 18 Dec 2006 22:25:32 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.12.8p1/8.12.3/Submit) with ESMTP id kBJ6PWk6037779; Mon, 18 Dec 2006 22:25:32 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Mon, 18 Dec 2006 22:25:31 -0800 (PST) From: Kireeti Kompella To: "Abhay D.S" In-Reply-To: <4587814C.7080604@acm.org> Message-ID: <20061218221317.J37729@kummer.juniper.net> References: <458615D6.1070807@acm.org> <20061218211624.C37477@kummer.juniper.net> <458779D0.1030400@acm.org> <20061218215323.T37560@kummer.juniper.net> <4587814C.7080604@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: l2vpn@ietf.org Subject: Re: Query Regarding BGP-MPLS-VPLS Restart X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org On Tue, 19 Dec 2006, Abhay D.S wrote: > hi kireeti, > Thanks, yes I agree RR does not allocate labels. > Probably the draft could be modified to say that RR is the case. Not really. There are many reasons why a BGP-speaking LSR may not set BGP nexthop to self. This draft is not for VPLS alone, but any NLRI with labels. On the other hand, the draft should apply to BGP VPLS. If you find it does not, please let the authors know (or me, and I'll forward it to the authors). Thanks! > Rgds, > Abhay > > Kireeti Kompella wrote: >> On Tue, 19 Dec 2006, Abhay D.S wrote: >> >>> hi kireeti, >>> In the mpls-bgp-restart-draft >>> 4.3. Case 3 >>> >>> The following applies when the LSR does not set BGP next hop to self. >>> >>> In this case the LSR, when advertising its best route for a >>> particular NLRI just uses the label that was received with that >>> route. And if the route was received with no label, the LSR >>> advertises the route with no label as well. Either way, the LSR does >>> not allocate a label for that route. >>> >>> I think this condition the LSR is just an RR ?. Im not sure my assumption >>> is correct . >> >> An RR for VPLS would not set the BGP nexthop to self, so it would satisfy >> this condition. However, such an RR would not make any VPLS "allocations", >> if by that you mean labels. The RR (as per the quoted draft) must first >> re-acquire all the VPLS updates (including label blocks) from its >> neighbors. Once it does that successfully, the RR can then do path >> selection and advertise VPLS NLRIs to its neighbors *with the received >> label blocks*. The RR does not allocate new label blocks. >> >> HTH. >> >>> Thank you, >>> Rgds, >>> Abhay >>> >>> Kireeti Kompella wrote: >>>> On Mon, 18 Dec 2006, Abhay D.S wrote: >>>> >>>>> hi group, >>>>> >>>>> How does a Route Reflector with VPLS advertisement capability >>>>> behave during a graceful re-start. >>>>> >>>>> What happens to VPLS allocations when RR undergoes re-start ?. >>>> >>>> To what VPLS allocations are you referring? >>>> >>>>> Rgds, >>>>> Abhay >>>> >>>> Kireeti. >>>> ------- >>>> >>>> >>> >> >> Kireeti. >> ------- >> >> > Kireeti. -------