The MPLS WG Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
regrding GMPLS extension to ospf traffic engineering
-
From: "Prabakaran T Sampath" <prabakarts@future.futsoft.com>
-
Date: Sat, 24 Jan 2004 19:10:21 +0530
-
Cc: "'prabakarts'" <prabakarts@future.futsoft.com>
-
Importance: Normal
Hi,
Please find my in-lined comments
[PrabakarTS].
Thanks
and regards,
Prabakaran T.S.
Future
Software Limited,
480-481, Anna Salai,
Chennai - 600035, India.
Off Phone: +91-44-24330550
Hi,
i have few doubts about how to use bandwidth information while
calculating a constrined based path.
according to RFC 3630 (TE
Extensions to OSPF version 2) there are three kinds of bandwidth
2.5.6 Maximum Bandwidth. 2.5.7 Maximum Reservable
Bandwidth. 2.5.8 Unreserved Bandwidth.
if an application ask for a
constrined based path in which bandwidth constrain is X mbps.
now should i consider only those TE links which has Unreserved Bandwidth at particular priority greater than X Mbps. or i should also consider
the Maximum Bandwidth (True Link Capacity).
my doubt
is:-
whether the check should be like this
Unreserved Bandwidth [priority] >= X Mbps
or
(Unreserved Bandwidth [priorit] >= X Mbps) && (Maximum Bandwidth >= X
Mbps)
[PrabakarTS] In my understanding the
check for the constraint should be,
( (Unreserved
Bandwidth [priority] >= X Mbps) &&
(Maximum Reservable Bandwidth >= X Mbps))
according to draft Routing
Extensions in Support of generalised MPLS
(draft-ietf-ccamp-gmpls-routing-06.txt) there are two more bandwidth
Maximum LSP bandwidth. Minimum LSP bandwidth.
now say if
the application ask for a path in which bandwidth constrain is X Mbps.
now the check should be like this Minimum LSP bandwidth < X Mbps < Maximum LSP bandwidth
or
[PrabakarTS] The bellow one is more
reasonable. Minimum LSP bandwidth < X Mbps < minimum (Maximum LSP bandwidth,
Unreserved Bandwidth)
Regards
***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.
If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************
| |
|