The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2006-Nov> msg00133



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

[mpls] RSVP: reservation styles doubt

  • From: "shilpa goel" <shilpa07@gmail.com>
  • Date: Mon, 27 Nov 2006 11:23:10 +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=PWl3PFTpewJ+1fwfXUoDI7hSRXcV899idXBH/+o22CDwiVGx4rzMbvrvJ5KMMRkI89XFxXGzdqvNkuNJhjvmEDWJ6sa2pAr5Zpu2QTVTBpWDjNbvQzNJOXjcrdJ38jLu/qTVHB8wq9RTxCrSh0kAHTKI4TirDRORRr/AwzgpzDY=


Hi,

  Please help in clarifying 2 doubts wrt RFC 2205 (RSVP).

a) In the Fixed filter (FF) Reservation style example as explained in Section 1.4, Page 16, Figure 6, the problems in understanding are:

  1. In the Reserves at the interface "d" how come we have merged the different request for S1 (3B) by receiver R2 and the request S1 (B) by receiver R3 when we are using the FF style?

  2. While sending the reservation request upstream we have again merged the reservation for sender S1 on interface "a" for different receivers. This is not clear.

b) In the Shared Explicit (SE) style as I understand, the scope of the explicit senders in the reservation requests traveling upstream is changed i.e. the senders are merged giving the maximum of the reservation required in the upstream direction.

With respect to this, in the example explained in Figure 7, Page 17,  how reservation is done at the router for different explicit senders at the interface "d" is not clear. Also how the reservation requests traveling upstream have changed the scope of senders and modified flowspec is not clear.

thanks and regards,
Shilpa



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