The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Nov> msg00022



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

RSVP-TE ERO processing

  • From: "M. ELK" <elkou141061@hotmail.com>
  • Date: Tue, 12 Nov 2002 08:43:54 +0000
  • Resent-Date: Tue, 12 Nov 2002 05:32:40 -0500
  • To: mpls-ops@mplsrc.com
  • X-OriginalArrivalTime: 12 Nov 2002 08:43:54.0546 (UTC) FILETIME=[A1F6D120:01C28A27]
  • X-Originating-IP: [57.250.229.136]

 
The processing of the ERO is specified in rfc 3209 section 4.3.4 , what is not clear is the action taken by the node in case  the node is not able to find a "Next Hop"  .
 
Ex: 
 R1------a-R2-b-----a-R3 .
 
R1 originate Path msg with ERO : Strict_aR2 (intf "a" at R2) , Strict_aR3 (intf "a" at R3).
 
At R2: assume Intf "b" at R2 is down .
R2 process the ERO in the path msg as per section 4.3.4 ,
 reaching step 4 in this procedure ,R2 is not able to find a "Next Hop" to
 aR3 (as bR2 is down) . 
Step 4 do not include any reference to handle such case .
Presume in such case , R2 should send to R1 a PathError with error
"Bad strict node "  
 
Brgds
 
 

Tired of spam? Get advanced junk mail protection with MSN 8. ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml