Subject: Re: [alto] One comment for the cost calendar

From: "RANDRIAMASY, SABINE (SABINE)" <[email-masked]>
Date: Wed, 12 Nov 2014 00:34:59 +0000

Hi Haibin,

Thanks for your feedback and question. Your example case is covered by the Calendar attributes presented in Toronto, see slides at http://tools.ietf.org/agenda/90/slides/slides-90-alto-5.pdf . Slide 10 gives the example of 7 daily calendars of 12 time intervals of 2 hours, computed every week on Sunday. Attribute "calendar-start-time" gives the time at which the daily pattern starts. 

In  this example, attribute "next-calendar-start-time" is set at Friday July 4th rather than Tuesday July 2nd. The reason in the example is that Friday July 4th has a different pattern because it either has a different pattern that the previous calendars, for reasons that may be as different as: maintenance period, week-end or vacation start day or celebration day. 

A new version of the draft will be presented at the ALTO session next Thursday, attribute names will be clarified, attributes with changing values such as dates are moved from the IRD to the ALTO responses, see http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-02.txt  

Additional illustration text related to your question was added in sections 
"4.4 ALTO Calendar information in ALTO responses"
and
"4.4.1 Example transaction for a routingcost Calendar to face intermittent connectivity" where one daily calendar is provided for a day that includes maintenance periods or is a celebration day.  

I hope this and the presentation to come will answer your questions.

Best regards,
Sabine

>>-----Message d'origine-----
>>De : Songhaibin (A) [mailto:[email-masked]]
>>Envoyé : vendredi 25 juillet 2014 19:45
>>À : RANDRIAMASY, SABINE (SABINE)
>>Cc : [email-masked]
>>Objet : One comment for the cost calendar
>>
>>One thought that came into my mind when Sabine presented the slides, I
>>think it may be useful to define the "exception" semantics in the cost
>>calendar. For example, you can define the cost for "every Monday" in
>>one year, but it happens that some holidays are also on Mondays, so you
>>can define some exceptions like "Dec 25", "May 1st", and some other
>>Mondays which may not apply the same cost value. Any thoughts?
>>
>>Regards!
>>-Haibin