Robert,
"smart configuration" is this case means nothing more then configuring
an offset to a common SRGB space on a per topology cases. This is as
operation friendly and easy to troubleshoot as configuring SRGB per
topology.
thanks,
Peter
On 8/20/15 10:03 , Robert Raszuk wrote:
Les,
I simply were trying to politely and gently point out (in the form of
the question) the problem with "smart configuration" auto picking SIDs
from global block.
To me there is fundamental difference in accidental or buggy collisions
vs design which will likely result in such on a regular basis in some
network deployment models.
To me it is like specifying say a global /16 IPv4 block in all routers
in the domain and having local "smart configuration" automatically
select /32 from that block for loopbacks or protocol router_ids.
Is this generally useful (well except maybe for home networking) ? Is
this operation friendly or easy for troubleshooting for large networks ?
Cheers,
R.
On Wed, Aug 19, 2015 at 8:05 PM, Les Ginsberg (ginsberg)
<ginsb...@cisco.com <mailto:ginsb...@cisco.com>> wrote:
Robert –____
__ __
There is another thread which is discussing how to deal with
conflict resolutions – I have attached one of the early emails on
the subject – please read the rest of that thread and – if you wish
– comment on that thread.____
Please do not introduce conflict resolution into this thread – that
isn’t appropriate – the problem is not specific to this discussion.____
__ __
Thanx.____
__ __
Les
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
