The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Mar> msg00259



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

Between OSPF RSVP...

  • From: Steve Yao <syao@chiaro.com>
  • Date: Fri, 14 Mar 2003 11:51:09 -0600
  • Cc: mpls <mpls@UU.NET>



>Steve,
>
>In two messages prior you stated:
>
>> The RRO received at the HE only contains the IP addresses 
>that map to half
>> of the LSAs or LSPs that the LSP traversed. 
>
>You mentioned that only half the LSA/LSPDU were in the RRO, so the
>question "What cases were you thinking of?" that you just asked should
>be directed to you.

I asked the question since you mentioned earlier:

>It wasn't intended to cover all cases and does not depricate use of
>path-tear.  You still didn't answer my question.

But it is ok if you don't want to answer the question.

>
>Since you brought up the issue "where RRO may be too large" why don't
>you do the math and tell us 1) how big the RRO would have to be to be
>too large and 2) how likely you think that is of occurring.  RSVPd
>objects can be 64KB each.  The IPv4 address subobject is 8 bytes long,
>including type and length.  Add a label subobject (8 bytes) and fit it
>into a reasonable MTU and you're still at hundreds of hops.  I get
>200+ into a 4KB MTU and most networks seem to be going for 8K MTU so I
>get "not very likely" for question 2).
>
>Curtis
>

I agree that this is not very likely.

Steve
----------------------------------------- (on Chiaro SMTP Relay)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------