Hi all, I think each vendor will uses its own NMS. So, it can’t be easy to manage global SID allocation with multi-vendor environment alongside multi-NMS. Therefore, PCE (standard) is better choice.
Regards, Vahid [email protected] > On Jul 24, 2019, at 10:32 PM, Jeff Tantsura <[email protected]> wrote: > > All of the tasks described belong in management plane, while I’m not > particularly fond of using DHCP, having single source of truth for > configurational state is better than configuring box by box (and excel to > manage it :)) > Most SP’s (and as Stephane alluded) already have a centralized management > entity that takes care of configuration management and soft resource (such as > IP’s, SID’s, RT/RDs, etc allocation. > > Cheers, > Jeff > On Jul 24, 2019, 12:38 PM -0400, Andrew G. Malis <[email protected]>, wrote: >> Sasha, >> >> Most "normal" DHCP servers require manual configuration of some sort if you >> want to guarantee persistence of the assigned IP address (i.e. "static" >> DHCP). So we're back to "manual" management, even if the results of the >> manual management are conveyed by a dynamic protocol. >> >> Cheers, >> Andy >> >> >> On Wed, Jul 24, 2019 at 11:53 AM Alexander Vainshtein >> <[email protected] <mailto:[email protected]>> >> wrote: >> Robert, Kireeti and all, >> >> I think that both loopbacks and their association with SIDs should be kept >> persistent. >> >> >> >> Whether such persistency is provided by the means of static configuration, >> or by the means that are external to some dynamic protocol is a different >> question. >> >> E.g., a “normal” DHCP client (like my office computer) may think that it >> obtains a dynamic IP address in the company network from the DHCP server >> every time I turn it on, but the DHCP server actually takes care to assign >> to it the same IP address every time. >> >> >> >> Does this help in any way? >> >> >> >> Regards, >> >> Sasha >> >> >> >> Office: +972-39266302 >> >> Cell: +972-549266302 >> >> Email: [email protected] >> <mailto:[email protected]> >> >> >> From: spring <[email protected] <mailto:[email protected]>> On >> Behalf Of Kireeti Kompella >> Sent: Wednesday, July 24, 2019 6:36 PM >> To: Robert Raszuk <[email protected] <mailto:[email protected]>> >> Cc: SPRING WG List <[email protected] <mailto:[email protected]>> >> Subject: Re: [spring] Managing "global" SIDs >> >> >> >> Hi Robert, >> >> >> >> On Wed, Jul 24, 2019 at 11:09 AM Robert Raszuk <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Kireeti, >> >> >> >> I would like to challenge a bit your fundamental assumption which is to >> state that while loopbacks are very important and locally significant and >> warrant manual/nms provisioning SIDs are not. >> >> >> >> Actually, what I said at the mike is that I believe that both loopbacks and >> global SIDs should be managed by DHCP. But that's a distraction; the point >> at hand is whether global SIDs should be managed "manually" (or by NMS or >> equivalent) (i.e., static), or by a protocol (say DHCP) (i.e., dynamic). >> You say the former .... thanks for the feedback. >> >> >> >> -- >> >> Kireeti >> >> >> ___________________________________________________________________________ >> >> This e-mail message is intended for the recipient only and contains >> information which is >> CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have >> received this >> transmission in error, please inform us by e-mail, phone or fax, and then >> delete the original >> and all copies thereof. >> ___________________________________________________________________________ >> _______________________________________________ >> spring mailing list >> [email protected] <mailto:[email protected]> >> https://www.ietf.org/mailman/listinfo/spring >> <https://www.ietf.org/mailman/listinfo/spring> >> _______________________________________________ >> spring mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/spring > _______________________________________________ > spring mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
