+1
Please do not take my comments about link vs node capabilities, as support for
the solution, they are semantical.
Cheers,
Jeff
On Apr 6, 2020, 8:58 AM -0700, Tony Li , wrote:
>
>
> > This discussion is interesting, but please do not ignore the considerable
> > feedback from multiple folks
Very valid comment - When working on MSD - we had exactly same considerations,
since path computation could use different links over different line cards that
may have different capabilities, hence we decided to have per link granularity,
details in RFC 8491
Cheers,
Jeff
On Apr 4, 2020, 7:33
We would like to define the NMP based on the usecases. That is, a specific
> set of parameters exported by NMP can satisfy the purpose of a specific
> usecase. Thus the protocol can be deployed incrementally.
>
>
> Best Regards,
> Robin
>
>
>
> -Original Messag
Robin,
Pretty much same comment as Acee - I'm not clear as to why...
Protocol YANG models developed in the last years clearly provide much better
and more scalable approach to what has been proposed in the draft, since we are
talking is-is - look at notifications in
