On 02/17/2014 07:37 PM, Songhaibin (A) wrote:
o (Standards Track) Protocol extensions to convey a richer set of
attributes to allow applications to determine not only "where" to
connect but also "when" to connect. Such additional information will
be related both to endpoints (e.g. conveying server load and cache
geolocation information for CDN use cases) and to
endpoint-to-endpoint costs (e.g. bandwidth calendaring to represent
time-averaged cost values in datacenter networks). (19')
This gives me a feeling that the protocol attributes extensions will
only consider the time based attributes. But I think overlay layer
path cost, i.e., you do not give only the source address and
destination address, but also give the intermediate node address to
retrieve the cost value for the overlay layer path, is also useful in
some scenarios such like CDN network, and can be easily achieved by
extending the protocol attributes.
Haibin: There is certainly nothing constraining the protocol attribute
extensions to temporal properties. However, it seems to me that your
particular use case may be better approached through cost computations
over a graph representation. But, as always is the case, the devil is
in the details.
Cheers,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / [email protected]
Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
