The MPLS-OPS Archive
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index][Thread Index][Author Index][Subject Index]
RSVP: reservation styles doubt
-
From: "shilpa goel" <shilpa07@gmail.com>
-
Date: Mon, 27 Nov 2006 11:41:59 +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=Oe3MxRYB/e2SMduqvHVNVl3KC9m2NY4zpCPh20LPlDwnwL9tF8MQRlmXblf98//B508u9CZNcgYQsRGO1HSS2RUYOdrcPCDr54Ng6RG83Ltx0gh8OxDOi9dhDlgfZCgO5FIFwYNPm8xA1npZ7mTOYQ9kVwwCwIoqJDF4nZ+XPpA=
-
Resent-Date: Mon, 27 Nov 2006 01:12:04 -0500
-
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 190f7394f72711cbc1abbc4cfcb3cae1
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:
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?
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
| |
|