The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] next hop change in CRLDP
+/v8APAAh-DOCTYPE HTML PUBLIC +ACI--//W3C//DTD HTML 4.0 Transitional//EN+ACIAPg- +ADw-HTML+AD4APA-HEAD+AD4- +ADw-META content+AD0AIg-text/html+ADs- charset+AD0-utf-7+ACI- http-equiv+AD0-Content-Type+AD4- +ADw-META content+AD0AIg-MSHTML 5.00.2614.3500+ACI- name+AD0-GENERATOR+AD4- +ADw-STYLE+AD4APA-/STYLE+AD4- +ADw-/HEAD+AD4- +ADw-BODY+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-hello venkat,+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- Yes,why not,there is no hard based rule for not storing ER-TLV's+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-Ref T.E MIB+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- One reason for not doing so would be that usually Loose hops+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- are not directly connected.+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-In other words the administrator does not know the stable topology+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-and gives it a shot by specifying the next hop to be loose,which means+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- the loose hop can be reached through any router.(Here if route pinning is+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- applied,then a better next hop is no use).+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- But,to do that,your MPLS management should very very efficient+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-In such cases,when you might have a lot of communication between+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-your signaling and forwarding management.+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAPA-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-Also,there arises a question,of controlling the child like Ingress of the Initiated LSP+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- to sustain the paths,since this is a downstream on demand mode+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAPA-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs-Also,whats the used of the better next hop ?.I dont see any good use of it,when one+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ACY-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- has a CR-LSP.+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- I guess it more of engineering and adding an extra rear view mirror to CR-LDP+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAPA-/FONT+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-Hope this helps,+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- Regards,+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- Abhay+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4AJg-nbsp+ADsAPA-/DIV+AD4- +ADw-DIV+AD4AJg-nbsp+ADsAPA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4------ Original Message ----- +ADw-/FONT+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-From: Venkat Dabbara +ACY-lt+ADsAPA-A href+AD0AIg-mailto:venkat.dabb+AEA-wipro.com+ACIAPg-venkat.dabb+AEA-wipro.com+ADw-/A+AD4AJg-gt+ADsAPA-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-To: +ACY-lt+ADsAPA-A href+AD0AIg-mailto:mpls+AEA-UU.NET+ACIAPg-mpls+AEA-UU.NET+ADw-/A+AD4AJg-gt+ADsAPA-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-Sent: Monday, November 19, 2001 5:01 PM+ADw-/FONT+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-Subject: next hop change in CRLDP +ADw-/FONT+AD4APA-/DIV+AD4APA-/DIV+AD4- +ADw-DIV+AD4APA-BR+AD4APA-/DIV+AD4APA-FONT face+AD0-Arial size+AD0-2+AD4-hai ,+ADw-BR+AD4APA-BR+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- This is regarding next hop change in CRLDP ( Better next hop avalability ) .+ADw-BR+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- I could find some discussion happening before on this but it wasn't satisfactory +ADw-BR+AD4APA-BR+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- Some one had asked +ADw-BR+AD4APA-BR+AD4AJg-gt+ADs-Suppose a CRLSP is setup with no-pin option and+ACY-nbsp+ADs- LSR-A is +ADw-BR+AD4AJg-gt+ADs- part of LSP as +ADw-BR+AD4AJg-gt+ADs- loose hop member. +ADw-BR+AD4AJg-gt+ADs- When LSR-A finds better nexthop, it is supposed to taer down +ADw-BR+AD4AJg-gt+ADs- LSP along old +ADw-BR+AD4AJg-gt+ADs- path+ACY-nbsp+ADs- and send label request to new nexthop. For this, LSR-A +ADw-BR+AD4AJg-gt+ADs- has to store +ADw-BR+AD4AJg-gt+ADs- all the TLVs it received in CRLSP initiation request so that +ADw-BR+AD4AJg-gt+ADs- it can initiate +ADw-BR+AD4AJg-gt+ADs- request along new nexthop. Does not it imply that CR-LDP is +ADw-BR+AD4AJg-gt+ADs- not scalable? +ADw-BR+AD4APA-BR+AD4-And some one had answered it saying +ADw-BR+AD4APA-BR+AD4AJg-gt+ADsAIg- This is not a scalability issue but a simple engineering issue, +ADw-BR+AD4AJg-gt+ADs- no-pinning with a CR-LDP loose hop is an unlikely scenario. +ADw-BR+AD4AJg-gt+ADs- No pinning is most appropriate with LDP. +ACIAPA-BR+AD4APA-BR+AD4-Ruling out such a scenario doesn't seem+ACY-nbsp+ADs- to solve the problem ..What if the scenario comes in ??+ADw-BR+AD4-Surely we can react as it is being done in LDP where u just tear down the path .+ADw-BR+AD4-Some thing of +ACI- make and break+ACIAJg-nbsp+ADs- policy should be done which would be of some meaning rather than going for+ADw-BR+AD4AJg-nbsp+ADsAIg-break and make +ACIAPA-BR+AD4-as done in LDP where u land up tearing down the CRLSP for every better next hop avalibility.+ADw-BR+AD4APA-BR+AD4-As pointed out by some one , will it be scalable to store the list of remaining hops present in ERTlv+ADw-BR+AD4-at every hop ??? If yes ,this would solve the purpose to some extent ...+ADw-BR+AD4APA-BR+AD4-Please correct me if i am wrong.+ADw-BR+AD4APA-BR+AD4-regards+ADw-BR+AD4-venkat+ADw-BR+AD4APA-BR+AD4APA-BR+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ADw-BR+AD4APA-BR+AD4AJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADsAJg-nbsp+ADs- +ADw-BR+AD4APA-BR+AD4APA-BR+AD4APA-BR+AD4APA-BR+AD4APA-/FONT+AD4APA-/BODY+AD4APA-/HTML+AD4-
|
|