The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2006-Dec> msg00084



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

[mpls] basic query about RSVP

  • From: shilpa goel <shilpa07@gmail.com>
  • Date: Fri, 22 Dec 2006 15:51:42 +0530
  • DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;h=received:message-id:date:from:to:subject:mime-version:content-type;b=eejsFG9E3rqja08ztzse7X0UQLngTQk8d6XVyi0h3Z+v7z3ONTS4B4HbK6o7hqwW9P8NyPhrYRXNV8S4M4hr+MnR6/EpB8zsLYT6NG2015uI/M0FW8t9XPrXDESQiZnuQgkZhhBU2Bc2zUHLe6eE4MHdnq7V/B9bQ2hmfqXu1Jw=
  • X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlx=0adultscore=0 adjust=0 reason=mlx engine=3.1.0-0612050001definitions=main-0612220007

Hi,

  I have few basic doubts regarding the functioning of RSVP-TE:

In RSVP as I understand "Link Admission Control" is used within the PATH message and the bandwidth value is included in the sender's Tspec field. This bandwidth is moved to a waiting pool untill a RESV mesage is received. Otherwise, a path error  message will be sent upon reception of RESV.  With respect to this understanding, I have the following doubts:

1)What actual benefits do we achieve by "Receiver Initiated Reservation Style"? Why cannot we perform Admission Control and Policy control during the flow of Path messages only?

2)When the path message is moving downstream and the required bandwidth is available
then it is moved to the waiting pool, but what if the required bandwidth is not
available why the error message has to wait for the RESV message from the downstream?
In this way we are unnecessarily blocking the network with the control packets if we
know that required reservation could not be made in the first place?

thanks,
Shilpa
 
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls