Hi Adrian, Thanks for your comments.
The main idea of this draft is to solve the problem of potential unavailability of pre-configured routes and to provide better service, which is described in section 2. For the first question, I'm sorry for the mistake, and this will be rectified in the next version. For the second question, the flag defined in the draft is to let PCE know PCC need pre-configured route service. And PCC doesn't care how the route was derived. PCC can update the stored pre-configured route when it receives a PCRep message with the flag set. For PCE, when it receives a PCReq message with flag set, it can recognize a pre-configured route service is requested from PCC. So PCE can compute and send the updated pre-configured route to PCC when the corresponding condition meets. Best regards, Yuanlin Bao "Adrian Farrel" <[email protected]> 写于 2009-10-19 19:29:11: > While this is a reasonably well-written draft, I don't see that it adds > anything to what we already have in the core RFCs. > > In section 4.3 you have... > > There are two options > for PCE to send pre-configured route as follows: > PCRep is used to respond route computation result naturally. If it > is used to send pre-configured route, a new flag SHOULD be defined to > indicate the route carried is pre-configured route. > > Two questions: > 1. What is the other option? You only list one option. > 2. Why do you need a flag to indicate that a route is pre- > configured? Why does the PCC care how the route was > derived? > > You slighlty answer question 2, in section 5.1 where you say... > > When PCC requests pre-configured route > > ...but why would the PCC ask for a pre-configured route? It just wants a > route. If there is a policy to be applied by the PCE in selection of the > route, this should be indicated using the normal policy functions. If there > is an objective function/algorithm to be applied in selecting the route, > this should be indicated using the OF object. > > So I think that you don't need the pre-configured route flag. > > Cheers, > Adrian > >
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
