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 basi
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 s
Hi Peter,
On 8/19/15, 6:15 PM, "Peter Psenak" wrote:
>I'm not sure we want to advertise redundant data to allow more
>configuration flexibility. From both architecture and encoding
>perspective it's preferable to pick single approach. And it looks like
>to me one has been picked already by both
Hi Pushpasis,
On 8/20/15 11:20 , Pushpasis Sarkar wrote:
Hi Peter,
On 8/19/15, 6:15 PM, "Peter Psenak" wrote:
I'm not sure we want to advertise redundant data to allow more
configuration flexibility. From both architecture and encoding
perspective it's preferable to pick single approach. And
Hi Peter,
Sure. I will let the operators on the list to decide if this needed. No
more nagging from my side :)
Thanks
-Pushpasis
On 8/20/15, 4:43 PM, "Peter Psenak" wrote:
>Hi Pushpasis,
>
>On 8/20/15 11:20 , Pushpasis Sarkar wrote:
>> Hi Peter,
>>
>> On 8/19/15, 6:15 PM, "Peter Psenak" wrote
