Hi Vijay, > 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. Best Regards! -Haibin > -----Original Message----- > From: alto [mailto:[email protected]] On Behalf Of Vijay K. Gurbani > Sent: Tuesday, February 18, 2014 4:06 AM > To: alto > Subject: [alto] ALTO agenda for London IETF > > Folks: The agenda for the London IETF has been posted. Please see > http://www.ietf.org/proceedings/89/agenda/agenda-89-alto > > The bulk of the time is allocated to the rechartering discussion. > > Over the course of this week, Enrico and I will reach out to a subset of the > participants to prepare a short (3 minute*) per-topic presentation kicking off > the discussion on the work item under consideration. > > To keep the discussion focused, we will like exactly two slides per topic. > The > content of these two slides must contain examples (preferably JSON > representation) of the extensions being sought. > > * The exception is the extensions to ALTO server discovery mechanism. > Previous IETFs have demonstrated consensus for supporting this > extension; unless something material has changed by the time we get > to London, we will expect to spend the least amount of time on this > work item. > > The agenda is draft, of course, and not considered final until bashed at the > meeting. But regardless, it should give you a reasonable feel for where we > are headed. > > Thank you, > > - 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 _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
