The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2006-Nov> msg00103



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

RE: RSVP: reservation styles doubt

  • From: <Alaerte.Vidali@nokia.com>
  • Date: Mon, 27 Nov 2006 05:31:35 -0600
  • Resent-Date: Mon, 27 Nov 2006 08:54:01 -0500
  • X-Nokia-AV: Clean
  • X-OriginalArrivalTime: 27 Nov 2006 11:31:36.0946 (UTC) FILETIME=[99563520:01C71217]
  • X-Scanned-By: MIMEDefang 2.53 on 209.239.41.31
  • X-Security: MIME headers sanitized on host.secure4-hosting.netSee http://www.impsec.org/email-tools/sanitizer-intro.htmlfor details. $Revision: 1.138 $Date: 2003-01-26 11:25:54-08
  • X-SpamProbe: GOOD 0.0000000 99cf6d9f81c91e73d72297ca462ca2b5

Hi Shilpa,
 
Are you using RSVP for specific reason?
 
I have seen clients considerering RSVP used for MPLS Tunnels reserve the desired bandwidth on outgoing interfaces, while it is not really what occurs.
 
On the other hand, RSVP can be used for reserving bandwidth for other application when there is a source/destination speaking RSVP protocols or Cisco is configured to do so.
 
Best Regards,
Alaerte

From: ext Amit Kumar-G20042 [mailto:amitkumar@motorola.com]
Sent: Monday, November 27, 2006 9:08 AM
To: shilpa goel; mpls-ops@mplsrc.com
Subject: RE: [MPLS-OPS]: RSVP: reservation styles doubt

Hi Shilpa,
I am oversimplying the things for your understanding. Hope it helps you.
 
For your first doubt:
  Since here the reservation will be done "per source basis on the outgoing interface" along the data flow (from source to destination), for source S1 what maximum reservation is required to be done is max(3B for R2, B for R3) =3B, and for S2 it will be B.
   While sending the reseravtion request upstream again it is send per source basis max(4B for S1 on interface "c", 3B for S1 on interface "d") = 4B for S1 and similarly for other sources.
 
For your second doubt:
   In SE style, the reservation will be for the maximum bandwidth required to serve all reservation requests received on the interface, and the upstream requested bandwidth will be on interface "a" source reachable is S1, so the bandwidth requested is max(B for S1 on "c", 3B for S1 on "d") =3B and similarly on interface "b" where sources S2 and S3 are reachable, the bandwidth requested is max(3B for S2/S3 on "d", B for S2 on C) = 3B
 
Thanks and regards,
Amit kumar

From: shilpa goel [mailto:shilpa07@gmail.com]
Sent: Monday, November 27, 2006 11:42 AM
To: mpls-ops@mplsrc.com
Subject: [MPLS-OPS]: RSVP: reservation styles doubt

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