Subject: Loose ERO subobject

From: Rita Hui <[email-masked]>
Date: Mon, 13 Nov 2000 15:12:15 -0800 (PST)

Hi,

In RSVP-TE, when a LSR receives a PATH message with
the FIRST ERO subobject being a LOOSE one, which of
the following behaviour is correct?

1) It generates error "Bad Initial subobject" if the
node does not belong to the address described by the
subobject.
2)  It does not generate the "bad initial subobject"
error, but select a next hop for the address described
by the subobject.  If it does not have a path,
generate "Bad loose node", else, send it off.

The draft (version 7) does not say that it evaluates
the first ERO subobject only when the "L" bit of the
subobject is not set.  This is different than "CR-LDP"
draft which specifically states evaluation of first
ERO TLV is done ONLY when the "L" bit is not set. 

If RSVP-TE really evaluates the first ERO subobject no
matter it is loose or strict, when a LSR selects a
next hop for a loose ERO subobject, it must  ensure
that the Path message's first ERO subobject contains
the next hop's address before it sends downstream so
that the downstream node would accept it.

What is the rationale of this distinct behaviour in
Rsvp-Te as opposed to CR-LDP?

__________________________________________________
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/