The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Aug> msg00124



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

[Fwd: I-D ACTION:draft-pan-rsvp-te-restart-01.txt]

  • From: Yangguang Xu <xuyg@lucent.com>
  • Date: Wed, 15 Aug 2001 17:49:38 -0400
  • CC: mpls@UU.NET
  • Organization: Lucent Technologies, Inc.


See my reply below,

> >
> > The restart procedure you described virtually turns the RSVP from a soft state
> > protocol to a hard state protocol.
> >
> 
> How? Please explain.
> 

>From RFC 2205 "RSVP takes a "soft state" approach to managing the reservation
state in routers and hosts. RSVP soft state is created and periodically
refreshed by Path and Resv messages.  The state is deleted if no matching
refresh messages arrive before the expiration of a "cleanup timeout" interval."

The "state" here is data plane state. If you separate the control and transport
plane, you can't depend on the periodically refreshing of Path and Resv message
to maintain the data plane state any more. Indeed, you can't even associate the
health of control and data plane any more.

Thanks,

Yangguang