Hi Xian,

I was just going through everyone's comments to update the draft and I had a
question about one of the points you raised...

> Q19:
> Is there a reason why the other sub-type of an active PCE is left out? IMHO,
an
> active PCE with the ability to issue new route recommendations would be also,
> maybe even more, like an NMS, as compared to the case mentioned. For an
> active PCE with LSP delegation, at least the LSP is initiated by the head-end
nodes
> and it has the root control when needed. :-)

I wondered what you meant by "sub-type of an active PCE".
Possibly you mean stateful vs stateless. Or maybe you are suggesting that there
are two types "recommend paths" and "provision paths".

In the first case, I don't think there is any distinction to be made. As the
current text notes, an Active PCE is likely to hold state for at least the LSPs
for which it can issue route recommendations.

In the second case you would be suggesting an option I personally don't consider
is allowable. That is, a PCE cannot, IMHO, provision paths. It can only issue
recommendations for rerouting of LSPs that have been delegated to it.

Thus you have drawn out an important distinction between an NMS and an Active
PCE. That is, the NMS can provision new LSP and has control over existing LSPs.
The Active PCE cannot provision new LSPs and can only suggest changes to
existing LSPs. I have added a little text about this to Section 19.

Cheers,
Adrian


_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce

Reply via email to