[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some minor comments on the loose-path-opt draft

Hi JP,

[snop...]
2. Other comments:

2.1. In section 4.3.1, page 7
"- If a better path can be found, the LSR MUST
             immediately send a Path Error to the head-end LSR
             (Error code 25 (Notify), sub-code=6 (better path
             exists))"

I wonder if you should also add "and go ahead with reopt by sending RSVP path messages for the new path". Otherwise there is no action described for this mid-point LSR what it will do after it found a better path and notify the HE LSR.

In this case, the TE LSP is contiguous, hence the mid-point's role is just to notify of the existence of a better path (or the requirement for local maintenance) in some downstream area/AS. Note that it cannot locally reoptimize since the LSP ID would not match. Moreover, the intention is to let the Head-end LSR decide on whether to reoptimize depending on the TE LSP attributes (pending back-off, ...).

Does that make sense ?

yes it does... your're right that the mid-point LSR can not reopt on its own since HE LSR controls the LSP ID but it will need to re-expand the ERO to the next loop hop. That's what I meant.


Cheers,
Raymond




Thanks for your useful comments: they will be incorporated in the next revision.

JP.


Regards,
Raymond