The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Jul> msg00039



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

rsvp refresh question

  • From: Yuan Gu <yuangu@ipinfusion.com>
  • Date: Thu, 11 Jul 2002 17:15:27 -0700
  • Organization: IP Infusion Inc
  • Resent-Date: Thu, 11 Jul 2002 21:20:22 -0400
  • To: mpls@UU.NET, mpls-ops@mplsrc.com

Hello:

In RFC2205, the refresh mechanism is defined not only to refresh the
state but also to UPDATE the state maintained by RSVP(Section 2.3, page
23). But in RFC3209 or any other document, there is no clearify about
this. Is this refresh UPDATE concept automaticly extended to RSVP-TE? If
so, beside update the QoS parameters, we also can use refresh msg to
update other parameters such as ERO, Session_Attribute and Label? Then
we don't need "make before break" any more? What's the pros and cons to
use refresh msg to modify the existing LSP? At last, can anybody
clearify how cisco and Juniper handle this issue? Do they compare every
bit of received refresh msg with exiting states?

Thanks alot!

Yuan

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml