Hi guys, The CONEX work in my view can be of relevence here, instead of DSCP and ECN CONEX enables eforcement of trust in signals from the source.
CONEX also seem to equalize congestion volume between tenants (at the network or path level). Ofcourse fair drop rates do not mean bandwidth guarantees for sure. Thanks, Vishwas On Thu, Jul 19, 2012 at 3:40 PM, Selvam Ramanathan < [email protected]> wrote: > ** > Hi Lizhong & Truman, > > Yes i do agree this can be solved by rate limiting at ingress. Some how we > need to bring in > VNI in to the equation as well. > > So should the problem statement capture this as well ? > > Regards, > Selvam > ------------------------------ > *From:* Lizhong Jin [mailto:[email protected]] > *Sent:* Thursday, July 19, 2012 6:44 AM > > *To:* Selvam Ramanathan > *Cc:* [email protected] > *Subject:* Re: [nvo3] bandwidth requirements of the tenants in > draft-narten-nvo3-overlay-problem-statement-02.txt > > Hi Selvam, > One of the way to ensure bandwidth requirements is to build non-blocking > datacenter, and do rate-limiting at ingress and egress NVE. Otherwise, I > can not work out another way to ensure bandwidth in an IP network. > > Lizhong > > > >> ---------- Forwarded message ---------- >> From: Selvam Ramanathan <[email protected]> >> To: "[email protected]" <[email protected]> >> Cc: >> Date: Tue, 10 Jul 2012 19:40:05 -0400 >> Subject: [nvo3] bandwidth requirements of the tenants in >> draft-narten-nvo3-overlay-problem-statement-02.txt >> >> Hi , **** >> >> **** >> >> Should the overlay-problem-statement-02 also talk about the **** >> >> issues arising out of the bandwidth requirements of the tenants ? **** >> >> **** >> >> Regards, **** >> >> Selvam **** >> >> > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 > >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
