Re: [spring] Managing "global" SIDs

[Alexander Vainshtein <[e-mail]>]

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: [phone]
Cell:      [phone]
Email:   [e-mail]

From: spring <[e-mail]> On Behalf Of Kireeti Kompella
Sent: Wednesday, July 24, 2019 6:36 PM
To: Robert Raszuk <[e-mail]>
Cc: SPRING WG List <[e-mail]>
Subject: Re: [spring] Managing "global" SIDs

Hi Robert,

On Wed, Jul 24, 2019 at 11:09 AM Robert Raszuk <[e-mail]<mailto:[e-mail]>> 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.
___________________________________________________________________________