The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Nov> msg00170



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

ERO processing

  • From: "Sandeep S" <san_101@hotmail.com>
  • Date: Fri, 16 Nov 2001 19:37:39 +0000
  • X-OriginalArrivalTime: 16 Nov 2001 19:37:40.0193 (UTC) FILETIME=[2725CD10:01C16ED6]
  • X-Originating-IP: [63.104.212.3]

As per my understanding whenever we get an ERO in PATH, the first node
we should look at and find it is not a local subnet on the box we should 
just discard it.

Is it necessary to it be a STRICT node rather than being a LOOSE. What are 
the possible negative parts using either one of them.

-Sandeep

======
4.3.4. Processing of the Explicit Route Object

4.3.4.1. Selection of the Next Hop

   1) The node receiving the RSVP message MUST first evaluate the first
   subobject.  If the node is not part of the abstract node described by
   the first subobject, it has received the message in error and SHOULD
   return a "Bad initial subobject" error.  If there is no first
   subobject, the message is also in error and the system SHOULD return a 
"Bad EXPLICIT_ROUTE object" error.

   6) Finally, the node replaces the first subobject with any subobject
   that denotes an abstract node containing the next hop.  This is
   necessary so that when the explicit route is received by the next
   hop, it will be accepted.




_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp