Hello,I would greatly appreciate to invite you to a further reading of the thesis entitled "Implementation and Evaluation of a Network Element Control Protocol" [0] where different Dynamic Switch Control Protocols (ForCes, GSMP and OpenFlow) are compared (page 17-23). -Note: the source code is available at the web page titled "Work ETNA Package 4"[1]. Best Regards, [0]http://lib.tkk.fi/Dipl/2010/urn100214.pdf [1]http://etna.netlab.tkk.fi/ Guillaume FORTAINE Tel : +33(0)631 092 519 Mail : gfortaine at gfortaine.biz ---------------------------------------- > Date: Fri, 19 Nov 2010 10:14:34 -0500 > From: lberger at labn.net > To: Martin.Stiemerling at neclab.eu > CC: vnrg at irtf.org > Subject: Re: [vnrg] Meeting minutes IETF-79 > > Martin, > I have one comments/corrections. > > > Lou asked an OpenFlow question. Forces (RFC 5812?) framework (GSMP) > > uses Android model. Didi is not familiar with that. > > I don't believe I said anything about android (although Jamal may have.) > > How about: > > Lou Berger asked about how OpenFlow relates to the IETF FORCES WG > and [the Standards Track] GSMP [RFC3292]. Didi is not familiar with > that. > > Lou > > On 11/19/2010 8:56 AM, Martin Stiemerling wrote: > > Dear all, > > > > The meeting minutes are available here: > > http://www.ietf.org/proceedings/79/minutes/VNRG.txt > > > > Please check them and let me know if there are incorrect or miss some points discussed. > > > > Thanks > > > > Martin > > > > martin.stiemerling at neclab.eu > > > > NEC Laboratories Europe - Network Research Division > > NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 > > > > > > _______________________________________________ > > vnrg mailing list > > vnrg at irtf.org > > https://www.irtf.org/mailman/listinfo/vnrg > > > > > > > > > _______________________________________________ > vnrg mailing list > vnrg at irtf.org > https://www.irtf.org/mailman/listinfo/vnrg
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.