[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Two-octet bandwidth values
- To: ccamp@ops.ietf.org
- Subject: Two-octet bandwidth values
- From: Kireeti Kompella <kireeti@juniper.net>
- Date: Sun, 25 Mar 2001 20:05:43 -0800 (PST)
- Delivery-date: Sun, 25 Mar 2001 20:07:34 -0800
- Envelope-to: ccamp-data@psg.com
Let's get the ball rolling. Please send questions and comments to the
list. Here are mine:
Questions to vendors:
1) Is floating point arithmetic a burdensome requirement? Is having
a new library of functions for the two-octet "floating point"
representation a burdensome requirement?
2) Is halving the size of the bandwidth TLVs a big win (keep in mind
that more bandwidth TLVs are being proposed)?
(a) for ISIS?
(b) for OSPF?
(c) if the answers for ISIS and OSPF differ, is it acceptable to
have different formats for the two protocols?
Questions to vendors & carriers:
1) Is 10 bits of dynamic range (0.1% accuracy) good enough?
2) Are you in favor of this draft, or against?
Kireeti.