hi Wendy, Extension in 'https://datatracker.ietf.org/doc/draft-randriamasy-alto-cost-calendar/' works for this kind policy,And there are many other kind policies in ECA modes, ECA stands for Event Condition and Action. BRGuohai > Date: Tue, 14 Apr 2015 16:35:25 -0400 > From: [email protected] > To: [email protected] > Subject: Re: [alto] Ato extension for representing SDN policies > > Guohai, > > https://datatracker.ietf.org/doc/draft-randriamasy-alto-cost-calendar/ > presents an extension to add time-dependency to cost maps. Eg, the > extended cost map could say the cost from A->B is 20 from 9:00 to 12:00, > and 10 from 12:00 to 17:00, etc. > > Would that solve your problem? > > - Wendy Roome > > On 04/08/2015, 15:00, "[email protected]" <[email protected]> > wrote: > > >Message: 1 > >Date: Wed, 8 Apr 2015 13:18:44 +0000 > >From: ChenGuohai <[email protected]> > >To: ??? <[email protected]>, Richard Yang Y. <[email protected]> > >Cc: "[email protected]" <[email protected]> > >Subject: Re: [alto] Ato extension for representing SDN policies > >Message-ID: <[email protected]> > >Content-Type: text/plain; charset="gb2312" > > > >Hi Huaming,All > >Getting policy rules does benefit to traffic optimization. In addition to > >that it can reduce ALTO request and response. > >For example, a policy is that band between a pair of src(A)and dst is 20M > >between 11:00 to 14:00 and is 10M for other time. And band between other > >src(B,C,D ....) and this dst is 15M. The ALTO client can use this policy > >in selecting more optimal peers without sending ATLO cost map request to > >ALTO server now and then. > >ALTO client select src(A) as the peer between 11:00 to 14:00 and one of > >src(B,C,D....) at other time. > >Make sense? > > > >BR > >Guohai > > > > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
