The MPLS WG Archive

[Adithya Bhat <adithya@sasken.com>]

Hi *,

In draft-ietf-mpls-rsvp-lsp-tunnel-08.txt Section 4.2.5 says

        "RSVP is designed to cope gracefully with non-RSVP routers anywhere
   between senders and receivers. However, obviously, non-RSVP routers
   cannot convey labels via RSVP. This means that if a router has a
   neighbor that is known to not be RSVP capable, the router MUST NOT
   advertise the LABEL_REQUEST object when sending messages that pass
   through the non-RSVP routers.  The router SHOULD send a PathErr back
   to the sender, with the error code "Routing problem" and the error
   value "MPLS being negotiated, but a non-RSVP capable router stands in
   the path."

1. Why should a PathErr be  sent back to the sender ? Will the current router not be a egress router, and hence should send a label binding back.

2.  If the above is not true does it mean that all the routers (from the sender  to the reciever ) should be  rsvp-te capable ( should support labels)  routers ?

3. What is the meaning of "MPLS being negotiated, but a non-RSVP capable router stands in
   the path."

 Please throw some light on this,

Thanks in advance
 

Adithya
 

begin:vcard 
n:Bhat;Adithya
tel;fax:5560045
tel;home:6782112
tel;work:5578300-8251
x-mozilla-html:FALSE
url:www.sasken.com
org:Sasken Communication Technologies Limited;R&D
version:2.1
email;internet:adithya@sasken.com
adr;quoted-printable:;;21, Brigade Square,  Cambridge Road, Ulsoor,=0D=0A;Bangalore;Karnataka;560008;India
fn:Adithya
end:vcard